PC Unscheduled Random Shutdowns

[muzikfreakah]

---

I been having Unscheduled shudowns recently.

Do you guys know how to access the Windows memory dump so I can see which hardware/software is causing this?

Specs:
E8500
Asus P5B Deluxe
RAM: OCZ 2x2G
Windows 7 Release candidate build: 7100 <I mite just go ahead and install new build if I dont solve this issue.


I think its a hardware compatibility issue, because I do notice a BSOD screens coming out if maka timing ko sa shutdown.

What I want to do is open and read the memory.dmp file.

[poldopunk]

For Windows 7, the memory dump is located on the system root directory:

C:\WINDOWS or %systemroot%

Use Windows Debugger to identify what file is causing the stop error provided this is a driver or software-related issue.

If you want, you can email me the memory dump, then i'll debug it for you. From what I experienced, the power-saving feature of the processors have something to do with this (C1E, C2E, EIST) because when I disabled mine, nawala ang mga stop errors but every case is different as they say.

**edit**

Para maka benefit tanan, I'll teach everyone here how to debug stop error codes. if the computer can still boot in safe mode with networking or normally, download and install the debugger for your platform (x86) or (x86-64) else, you would have to obtain the dump file through the recovery console or by connecting the hard drive to a known-good system. Make sure to run the debugger as administrator para maka download sa symbols from microsoft.

Once the program is opened, you need to set the symbols to the following: (File > Symbol File Path)



Then open the location of the memory.dmp file. For Windows XP and Windows Vista, the location is C:\WINDOWS\MEMORY DUMP, for Windows 7, its on C:\WINDOWS



From this look, naa naka idea what file is in question (hint: cm11264) but if you want to get into details, you need to run analyze in verbose mode. Your debugger will connect to Microsoft database for the symbols - "!analyze -v"



This is the detailed result of the verbose mode analysis. You'll see the driver file causing the problem. In my case, its a sound card driver (google), my recent hardware changes was the Asus Xonar U1 file so I suspected it might be it. I examined the files used by the device through device manager and it was confirmed. Then, I downloaded the latest driver available from Asus and it worked fine from there.



Remember, that 90% of stop error codes are caused by drivers and not through a hardware failure unless if issue is caused by a failing power supply where the error returned would be different each time the system blue-screens. Lastly, stop error codes or blue screen of death as many people would call it is not your enemy, its actually a tool providing you information about the problem - its up to you to enable yourself on how you use the tool instead of cursing it.