BSOD's not saving minidumps, multiple 0x9F crashes

[piehole1983]

Hi there,

I have been getting lots of 9F crashes on a HP DV7 laptop running 64bit Windows 7 Home Premium.

Problem is the the minidumps are not being saved! I have set it up to save them (small dumps) and not to automatically restart. I cant debug it without them .

Any ideas why they wouldnt be saving?

Thanks!

 

[zigzag3143]

There are several reasons that may prevent you from having a DMP file in the usual places.

If your control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.




Please provide us with your Event Viewer administrative logs by following these steps:


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

 

[piehole1983]

Thanks, here is the requested information.

 

[zigzag3143]

Thanks, here is the requested information.

Literally hundreds of these

: The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

 

[piehole1983]

I know, I have updated the BIOS to the latest version and even tried flashing old versions to see if it helped. I noticed one entry from volume manager saying there was and error with saving the dump file. Do you think I have a hardware problem?

 

[zigzag3143]

I know, I have updated the BIOS to the latest version and even tried flashing old versions to see if it helped. I noticed one entry from volume manager saying there was and error with saving the dump file. Do you think I have a hardware problem?

Yes. I dont know how far back your log goes before you cleared it last but those errors are virtually the only thing in there.

 

[piehole1983]

The OS was reinstalled this very day so errors are all fresh and happen evry switch on and switch off. I started another thread about the 9F errors and managed to get one dump file which I think you looked at.

Am I looking at a new mobo? I ask because this is actually a "new" mobo, fitted about 3 weeks ago. It's 2nd user but new to this system. The old mobo did exactly the same thing.

 

[piehole1983]

New mobo's are not available any more from HP.

 

[zigzag3143]

The OS was reinstalled this very day so errors are all fresh and happen evry switch on and switch off. I started another thread about the 9F errors and managed to get one dump file which I think you looked at.

Am I looking at a new mobo? I ask because this is actually a "new" mobo, fitted about 3 weeks ago. It's 2nd user but new to this system. The old mobo did exactly the same thing.

I doubt it is a mobo.

More likely ram or a driver.


If you havent run memtest and driver verifier please do/.



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[piehole1983]

Thanks for the advice. I ran memtest for 16 passes with no faults and driver verifier for a couple of days with only one issue showing on another BSOD that woild not save.

Here is a picture of it:

 

[zigzag3143]

Unfortunately useless without the DMP. It appears to be a driver in the picture.

Whats the other link where you posted a DMP?

 

[piehole1983]

Here's the link for the previous thread:

http://www.sevenforums.com/crashes-debugging/217832-bsod-0x9f-hp-pavillion-dv7-3111ea.html

 

[zigzag3143]

Here's the link for the previous thread:

http://www.sevenforums.com/crashes-debugging/217832-bsod-0x9f-hp-pavillion-dv7-3111ea.html

There was no DMP file uploaded in the first post of the previous thread (just the rest of the data collected.) so we are at an impasse.

 

[piehole1983]

The zip file is on the bottom of post 1!

 

[piehole1983]

Here's a link to it:

http://www.sevenforums.com/attachme...lion-dv7-3111ea-windows_nt6_bsod_jcgriff2.zip

 

[zigzag3143]

The zip file is on the bottom of post 1!

Um, no it isnt!

 

[zigzag3143]

Here's a link to it:

http://www.sevenforums.com/attachme...lion-dv7-3111ea-windows_nt6_bsod_jcgriff2.zip

The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error


Run CHKDSK. delete and rebuild the page file.


http://www.sevenforums.com/tutorials/433-disk-check.html

 

[piehole1983]

Excellent, I'll give that a try shortly! Thanks!

 

[piehole1983]

The zip file is on the bottom of post 1!

Um, no it isnt!

With regard to this, I said it was in a different thread I had started and not this one. I even gave a link for it!

 

[zigzag3143]

I give up

The other thread has a zip folder but NO DMP in it.