Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD + Minidumps, please help

19 Jun 2010   #11
Microsoft MVP


Please run Driver Verifier according to these directions:
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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.

- 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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun 19 12:54:36.325 2010 (UTC - 4:00)
System Uptime: 0 days 6:11:32.792
BugCheck A, {fffffb8006779200, 2, 0, fffff80002898c74}
Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+c4 )

My System SpecsSystem Spec
19 Jun 2010   #12

Windows 7 Professional x64

After the "Windows is starting" window I got a BSOD, again with IRQ_NOT_EQUAL_OR_LESS

Here's the minidump.
My System SpecsSystem Spec
19 Jun 2010   #13
Microsoft MVP


OK, it's blamed CI.dll - a Windows module (but we were testing for 3rd party modules!)
So, this either means that there's a Windows issue - or a hardware issue.

I'd suspect hardware as you've already reinstalled Windows.
But, try this first:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.
Then, if the crashes keep coming:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:
FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Prime95 download site:
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
My System SpecsSystem Spec

19 Jun 2010   #14

Windows 7 Professional x64

With the driver verifier still on, I got a BSoD blaming ntfs.sys, minidump attached below.
After that another 2 BSoDs without minidumps, another IRQ not equal or less, after that a windows hang at "Starting Windows", had to hard reset.

So I disabled the driver verifier now, no BSoDs on restart.

Quote   Quote: Originally Posted by SFC scan
C:\Users\Administrator>SFC.EXE /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
After this, I'll try the HD diagnostic tools for my 3 WD HDDs.
My System SpecsSystem Spec
20 Jun 2010   #15

Windows 7 Professional x64

These out of the blue(lol) BSoDs are the most annoying, watching a video on youtube, boom, MEMORY_MANAGEMENT STOP

Minidump attached.
My System SpecsSystem Spec
20 Jun 2010   #16
Microsoft MVP


What are the results of the diagnostics that I asked you to run?
My System SpecsSystem Spec
20 Jun 2010   #17

Windows 7 Professional x64

I had already ran before asking here memtest86+ for a good 6-7 passes, both memories and 1 by 1, and in different slots, and no problems there.
Prime95 with no errors, the same for furmark.

The only one left is for the HDDs.
Which the CD version doesn't seem work, it freezes with a black screen on boot from the CD.
I'm trying the windows version now...
My System SpecsSystem Spec
20 Jun 2010   #18
Microsoft MVP


If it's Western Digital drives - the best way to run it is through Windows
Otherwise, try the Seagate Seatools for a bootable disk. If that doesn't work, then try the Hitachi Drive Fitness Test. As a last resort, try the HDTune tool from within Windows.
My System SpecsSystem Spec
20 Jun 2010   #19

Windows 7 Professional x64

Well, something came up in Prim95, when I used the blend option.

3 out of 4 workers stopped the first minute, and the last one, lasted about 3 minutes.

This is the result file
[Mon Jun 21 02:23:10 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
I'm starting to think the memory is the problem. Wherever I see this problem, BSoDs and prime95 errors like mine, the memory most of the times is OCZ. And the same, no memtest86 errors...

Someone said that they fixed this by increasing the voltage or frequency, but I wouln't knew which ones to increase...

Oh, and also 2 out of the 3 HDD's passed the quick and extended tests, I'll test the last one, but I dont think the drives are the problem...

And to top it off, a BAD_POOL_HEADER BSoD, minidump below.
My System SpecsSystem Spec
20 Jun 2010   #20
Microsoft MVP


Run the Small FFT's and the Large FFT's tests to see what happens with them.
The Blend test stresses a lot of the memory - so Memtest should've shown something (IMO)
My System SpecsSystem Spec

 BSOD + Minidumps, please help

Thread Tools

Similar help and support threads
Thread Forum
BSOD + minidumps
I got this new laptop few months back and now when i play certain games like cod4 and now apb beta, i get the BSOD and automatically restarts. I'm not really sure why its doing that, it could be over working it self but its a gaming laptop with pretty good specs so why is it doing it? Can someone...
BSOD Help and Support
BSOD + miniDumps
Hey guys, I'm new here and I've brought along with me a problem that seems to be bugging a few other people as well. Hopefully the assload of miniDumps I attached can give you guys enough information to tell me what is screwing with my computer (probably a driver issue, whatever) Every time my...
BSOD Help and Support
BSOD (Please look at my minidumps)
Hi, Getting some minidumps the last few days, restarted 3 times on it's own when I've been away from the PC. I don't know whats causing it, but I've uploaded the minidumps for someone to look at. Hopefully you can help me find what is causing it, as it's been fine for a few months untill the...
BSOD Help and Support
BSOD and my minidumps.
I have a new Asus G73H laptop, and lately I have been getting BSOD's.. I'm including my .dmp's so hopefully someone smarter than me can at least tell me maybe what's going on. Any help would be greatly appreciated...
BSOD Help and Support
BSOD, no minidumps
I'm getting a BSOD of a frequency of about one every couple of days. I looked in C: Windows but there is no minidump folder or file there. In the system recovery settings it's currently set to create a kernel memory dump, should I change it to small memory dump instead? What else should I...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 02:15.
Twitter Facebook Google+