BSOD on client's PC with no apparent error

[BTT]

I have attached a zip file of the appropriate .dmp file (of which I cannot figure out how to read, probably because I am a dummy >.<).

The synopsis is this:

Client calls me up saying that his computer restarts after trying to open up an application (there is not much given to me other then that...sorry). Upon looking at the Event Viewer, I read that there is a bug check and then the kernel loses power, but no other apparent application errors before or after.

PC is running Windows 7 Professional 64-bit


If someone could please analyze the dump file and maybe point me in the right direction as to a hardware issue, or maybe software by chance, it would be GREATLY appreciated!!!

 

[Arc]

A stray crash dump is not enough, mate.

Click on button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[BTT]

Ok give me a bit and I'll get that here, thanks for the reply

 

[BTT]

Ok so sorry for the original stray crash dump file, I read a post that stated thats all I needed (but going back now I realized it was an old post, and I did not catch the newer one...sorry). ALL that being said...I have the new zip file attached.

Again if someone could point me in the right direction, that would be fantastic please!

 

[Arc]

Still the zip does not contain the msinfo32 file. upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Also, Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[BTT]

Got the msinfo32 for you, and am checking the drivers as we speak. It will be a few days until I can check the RAM (thanks for your patience!!). I will let you know the results!!

 

[Arc]

OK, no problem. Let us know when the tests are done.