BSOD + Minidumps, please help

[alex2005]

I was getting so many BSOD's on my windows 7 pro x64, that I decided to re-install it, and so I did.

But now I'm getting if not more, the same amount of BSODs from all over...

All the drivers are up to date, I ran memtest86+ on the memory with no errors.

I have no idea what to do, please help me analyse these dumps.

In the zip there are 6 minidumps, I guess I had 6 BSODs today only(14/06/2010)

Thanks

 

[usasma]

6 memory dumps from today
3 different STOP errors, with 6 different causes
This is most likely a hardware or compatibility problem.

And, I'm pretty sure that there's a problem with your Diamondback Mouse. One of the errors blames it, and there's been a rash of Razer problems over the last week or two.

Uninstall the Razer software and see if that stops the BSOD's. If not, use another mouse and that should fix it.

Also, please see what's raised it's ugly little head:

ASACPI.sys   Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

Let us know if that doesn't work and we'll try some other stuff.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 16:32:43.418 2010 (UTC - 4:00)
System Uptime: 0 days 0:27:48.495
BugCheck 3B, {c0000005, fffff80002b7eae3, fffff88007a6a0c0, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+153 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 16:04:23.452 2010 (UTC - 4:00)
System Uptime: 0 days 3:04:59.919
BugCheck 3B, {c0000005, fffff9600014766e, fffff8800863ef90, 0}
Probably caused by : win32k.sys ( win32k!RFONTOBJ::bMakeInactiveHelper+2e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 12:55:22.944 2010 (UTC - 4:00)
System Uptime: 0 days 2:11:23.411
BugCheck 3B, {c0000005, fffff88004020be8, fffff88008ac5a00, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+1a0 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 10:43:29.074 2010 (UTC - 4:00)
System Uptime: 0 days 1:46:09.541
BugCheck 50, {fffffa8007081000, 0, fffff8000287f370, 0}
*** WARNING: Unable to verify timestamp for habu.sys
*** ERROR: Module load completed but symbols could not be loaded for habu.sys
Probably caused by : habu.sys ( habu+16b2 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  razerhid.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 13 23:10:05.774 2010 (UTC - 4:00)
System Uptime: 0 days 1:13:35.241
BugCheck 3B, {c0000005, fffff8800fef5b96, fffff8800753dbb0, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+e9b96 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 13 21:56:01.515 2010 (UTC - 4:00)
System Uptime: 0 days 1:58:05.592
BugCheck 24, {1904fb, fffff88003193738, fffff88003192fa0, fffff880012bd17d}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteReservedBitmap+31 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[alex2005]

Thanks you very much for your reply, I appreciate your help.

I've uninstalled the razer habu drivers, if I'll still be getting BSODs I'll change the mouse to see if anything changes...

The 2005 version of ASACPI.sys was found here
c:\Windows\System32\DriverStore\FileRepository\atk2000.inf_amd64_neutral_a91abe245a6c41c8\
I installed the 2009 version, and it's located here
c:\Windows\System32\DriverStore\FileRepository\asacpi.inf_amd64_neutral_a7ca2c2f114f9353\

Is it using the new one, or the old one?


Do you think any of my hardware is incompatible, you can see them on "My system specs", could it be the OCZ memory?

Thanks again.

 

[usasma]

Check in C:\Windows\System32\drivers for the ASACPI.sys file - that's the one that has to have the 2009 date stamp. If it's not there, let us know.

If you're concerned about compatibility, check hardware and software at this link: Windows 7 Compatibility: Software Programs and Hardware Devices: Find Updates, Drivers, and Downloads

 

[alex2005]

There is no ASACPI.sys in the Drivers folder, see the attachment.

 

[usasma]

Rename the old one to ASACPI.BAK
Copy the 2009 one to the C:\Windows\System32\drivers folder

 

[alex2005]

I can't rename neither of them, they are write protected.
But I copied the 2009 version to the Drivers folder.

How can I check to see which one is used?

 

[usasma]

Wait for the next BSOD and we'll see if it's named again.

 

[alex2005]

I haven't got any from then. I guess it's a good sign

 

[alex2005]

I just got the weirdest of BSODs.
I was watching a movie, while trying to make Steam validate some files, it gave me an IRQ_NOT_EQUAL_OR_LESS BSOD

Nothing changed on my computer driver wise, so I dont know why would I get it.

Minidump in the attachment, thanks.

 

[usasma]

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

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
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 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/FONT]

 

[alex2005]

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

Here's the minidump.

 

[usasma]

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:

SFC.EXE /SCANNOW
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: http://www.mersenne.org/freesoft/
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.

 

[alex2005]

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.

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.

 

[alex2005]

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

Minidump attached.

 

[usasma]

What are the results of the diagnostics that I asked you to run?

 

[alex2005]

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...

 

[usasma]

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.

 

[alex2005]

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...


Edit
And to top it off, a BAD_POOL_HEADER BSoD, minidump below.

 

[usasma]

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)