I have the BSOD on my Windows 7 64 bit. I tried to restore to a previous checkpoint from about a month ago but it still doesn't work. When I log into Safe Mode with Networking (which I am now), it works fine. However if I log in normally then after a minute, it shows me the blue screen and my laptop restarts. I also have created a different administrator account to try to login normally but that does not work either and after about a minute, I get the blue screen also. The error code I get is 0x0000007E.

A bugcheck (BSOD) is a mechanism to protect your PC from damage. Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED This bug check indicates that a system thread generated an exception that the error handler did not catch. http://msdn.microsoft.com/en-us/library/ff559239%28VS.85%29.aspx It is also helpful to take a look at the dumps with the Debugging Tools for Windows. Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your Skydrive [1] and post a link here, so that I can look at the dumps with the debugger and to to see the cause of the crash. André [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

You may boot in Clean Boot Mode. Perform a clean startup to determine whether background programs are interfering with your game or program If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause. Another way is enable muni-dump and use Windbg. Please refer: How to read the small memory dump files that Windows creates for debugging You may paste the result in your next post for analyzing. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.