Frequently (60% of the time) my Win7 install BluScreens on startup. It gets to the "Starting Windows" screen, displays the logo, then goes into the classic "Dumping physical memory...".I am running Windows 7 RC1 (Build 7100) 64 Bit Englishon a Toshiba L305D with 4 GB of RAM, a Dual-Core AMDTurion X2 Ultra 64, and an NVIDIA graphics card. Just reply if you need futher information.My question is, is there anything I can do to remedy this, apart from taking apart the computer. Thanks for your time!Cheers!C Day

Hi C Day,What I would suggest is, download WinDbg, and Windows 7 Symbols, and debug the .dmp file that is generated through the blue screen. This should help you pinpoint the issue - whether it's a memory issue or a system file corruption etc.For more information about WinDbg, please see this link.Jabez Gan [MVP] - http://www.msblog.org Contributing Author for: (Sybex) MCTS: Windows Server 2008 Applications Infrastructure Configuration Study Guide: Exam 70-643

Thank you very much. I will certainly do that!

I have the exact same model, Toshiba L305D-S5934 and I have been having the same problem except I would have to say that my BSOD at startup was pretty much 100% of the time, I have tracked the culpret down pretty much to a couple of things- all driver related. Windows 7 x64 runs just fine until you allow Windows 7 to download the optional updates and install them. There are two major things that I have identified o the slightest accidental touchas the culprets in this particular situation I think. Number 1 is the Synaptics touchpad driver that Windows update installs, every time I allow that to be installed I have gotten blue screens at startup and have to either go into safe mode and roll back the driver or do a system restore. Both options remove the touchpad driver and have it ided by the os as a PS2 compatable mouse. In this state you can use the touchpad as a mouse but you lose all scrolling functionality and it is hyper sensitive to the slightest accidental touch, believe me I am learning a whole new way of typing as I attempt to do it while not hitting the touchpad at all. The plus side is that my laptop doesn't bluescreen. Hmmm, I have tried several touchpad drivers thus far and have yet to find one that doesn't bluescreen the laptop at startup, I am still working on this one. Synaptics prolly needs to be made aware of this as does Toshiba, of course most of the time they still put 32 bit OSes on their 64 bit capable machines as was this one when it started out with Vista. the other thing is the Toshiba Value Added Package, it enables the Fn key to do all the stuff like adjusting screen brightness and using the Toshiba zooming utility, it can be lived without easier than the touchpad can remain wacky. Without a driver installed for the touchpad you also lose the ability to disable it when a regular usb mouse is connected. This is all a pain in the but I know but the RC sure is faster and more responsive than Vista ever was. Be very careful when messing with that Value Added Package, be sure you have a good restore point before attempting to install any version of it, if it gives you problems and you don't go back with a restore point the thing is next to impossible to get to completely uninstall even in safe mode, at least it was in Vista x64 anyway. Let me know if you discover a good fix for any of these issues.Charles

Ah... great. Im going to rollback the driver for my touchpad and uninstall the Value package.We'll see if that makes a difference. I will also try some other drivers and report if they change anything.Cheers!C Day

I rolled back the driver and it fixed my situation as far as the blue screen went however when I did it created more problems. First of all the touchpad was pretty much uncotrolled, the cursor would jump around all over the screen while I was typing with the slightest touch and sometimes it seemed like it did it even without a touch. It was quite annoying when I was in the middle of typing a scentence and suddenlt the cursor would jump up three or four lines and what I was typing was suddenly inserted into what was previously a completed sentence. Also I don't think the Atheros Wireless driver that Windows update downloads agreed with the 64 bit version either. I became very familiar with startup repair screen, system restore, Windows 7 Safe Modes and a lot of things I would rather have not had as much familiarity with. Eventually after several attempts to find drivers that would not kill the system the laptop just got to where it bluescreened on every boot and it didn't matter if I tried system restore, startup repair or safe mode (it got to where it would bluescreen booting into safe mode) nothing would work. Eventually I stuck in a G-Parted Live CD rebooted and formated the HD. I tossed out the x64 version and installed the 32 bit version. That was early Saturday and everything has been stable since. Every update has downloaded (with the exception of extra language packs which Ididn't need) and installed without a hitch and is working perfectly. I am starting a new PC build based on a Phenom X4 9600 proc. ASUS M3A78-EM mobo with 4 GB of OCZ Fatal1ty1066 RAM. I am planning on installing Windows 7 x64 on this system and seeing how it does, my guess is with no Synaptics Touchpad to deal with (and thus no drivers for one), no Toshiba Value Added Package and no wireless LAN driver it will probably do well. At this point I think these Windows 7 issues are not Microsoft's fault, I think it ismostly due to lack of good third party drivers for proprietary peices of hardware and that is basically the same problem that we have had with every 64 bit OS that has come down the pike in the last several years. Although I think that Linux is beginning to pull ahead of Windows in the area of x64 support. I recently took x64 Ubuntu 9.04 for a spin on this laptop (while I was throwing OSes this way and that I figured why not) and it ran pretty nice, though I think the ATI graphics drivers need a little tweaking.Charles

Hi, The presence of incompatible drivers in the system might be the reason for the blue screen error. That means you could fix that issue by removing those drivers from the system. If the system shows the name of any of the drivers, then those drivers will be the actual cause of the blue screen issue. Either by upgrading or by the replacement of the driver, you could fix the issue. Get more information to fix Windows 7 Blue Screen on startup : http://supportformicrosoft.iyogi.com/windows-7/windows-7-blue-screen-on-startup.html Hope this information helps you.

If at all possible I would suggest doing a clean install of the release version of Windows 7 and then installing SP1. That may not resolve the issue, but troubleshooting blue screens on a two-year old pre-release version of Windows...well, if you can get on a released version and service pack it, it certainly simplifies troubleshooting. If you are able to load it up in windbg as Jabez recommended, just do a !analyze -v and paste the results back in the forum.