BSOD Computer Wont start without BSOD'ing
Hello All, I have this problem with my NV53 Gateway Laptop to where whenever I turn it on, it blue screens. From what i understand the following errors will help to know what the problem is:
If
0x000000E1
0x000000D1
0x000000D3
0x0000000A
The time at which I get these problems are random, and never a reason for one or the other. If somebody could tell me how to fix my computer without being able to get into the files, it would be much appreciated.
Also, safe mode does not work, it will either get BSOD before it gets to it, or will sit on a screen with "Safe Mode" in the four corners of the screen.
April 14th, 2011 7:17pm
Please use Microsoft Skydrive to upload dump files (%systemroot%\minidumps like c:\windows\minidumps). Once done post a link here.
If you want to debug dump files without my help, use Windbg and refer to this Microsoft article:
http://support.microsoft.com/kb/315263
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft
Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
April 15th, 2011 9:19am
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 debuggingPlease 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.
April 18th, 2011 4:31am