BSOD + Minidumps, please help

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 7 Professional x64
       #1

    BSOD + Minidumps, please help


    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
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    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:
    Code:
    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
    Code:
    
    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
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
      
      
     
    
      My Computer


  3. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #3

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


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    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
      My Computer


  5. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #5

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


  6. Posts : 5,705
    Win7 x64 + x86
       #6

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


  7. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #7

    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?
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

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


  9. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #9

    I haven't got any from then. I guess it's a good sign :P
      My Computer


  10. Posts : 12
    Windows 7 Professional x64
    Thread Starter
       #10

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


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About 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 21:51.
Find Us