My pc suddenly shutdown
My pc has suddenly shutdown without any warning, it happened twice. this is the info that win 7 gave me. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: fe BCP1: 0000000000000005 BCP2: FFFFFA8006BAC1A0 BCP3: 0000000080863B34 BCP4: FFFFFA800A3CAC50 OS Version: 6_1_7600 Service Pack: 0_0 Product: 768_1 Files that help describe the problem: C:\WINDOWS\Minidump\041211-36925-01.dmp C:\Users\Hector\AppData\Local\Temp\WER-64475-0.sysdata.xml Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt and these are the dump files which I don't know how to read them http://cid-ee5d2ddf31e19a71.office.live.com/self.aspx/New%20folder/dmp.zip I wonder if you can help me to find what cused the shutdown. Thank you.
April 13th, 2011 5:34pm

I give you the link to the motherload of blue screen info. You probably want to click on BSODINDEX once you are there. BSOD and Driver Links - Carrona A little duplicity here from link above, but: BSOD Black Screen Troubleshooting BSOD Index BSOD Index and much more Bug Check Codes (Windows Driver Kit) Crash Dumps - Analyse Bugcheck and Process - Vista Forums
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 9:37pm

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 15th, 2011 5:05am

Thank you
Free Windows Admin Tool Kit Click here and download it now
April 18th, 2011 11:48pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics