DRIVER_IRQL and BSOD and random screen freezes

Page 1 of 5 123 ... LastLast

  1. Posts : 26
    Windows 7 Ultimate 64bit
       #1

    DRIVER_IRQL and BSOD and random screen freezes


    This has just recently started happening over these past 2 months, although it has increased in frequency lately. I thought it was originally my old 5850 graphics card, so I replaced it with a 6970, but the problem persists. I attached the minidump and BSOD analyzer documents as well.

    My current system
    Windows 7 Ultimate 64 bit
    Crucial m4 60gb SSD
    HIS Radeon 6970
    4gb 1600mhz DDR3 RAM
    Gigabyte 890FX UD5 motherboard
    Asus Xonar Essence ST sound card
    Corsair 750TX PSU

    Windows is full retail version, and the OS install is less than 6 months old
      My Computer


  2. Posts : 26
    Windows 7 Ultimate 64bit
    Thread Starter
       #2

    any help?
      My Computer


  3. Posts : 26
    Windows 7 Ultimate 64bit
    Thread Starter
       #3

    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/Windows 7 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 (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:
    Code:
    Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Windows 7):
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Ma
    I ran this Driver Verifier found above and within minutes of logging into World of Warcraft and playing I was presented with the following BSOD similar to one I saw earlier. I have also attached the dump file from the crash.
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Start with the steps in Stop 0x124 - what it means and what to try and post back if you need further troubleshooting steps after proceeding through that thread.

    Also, take note of post#2 by usasma. The ssd portion of that post may be of interest.

    Since usasma is viewing this thread, he may be able to help more with his experience.
    Last edited by writhziden; 04 Feb 2012 at 11:59. Reason: usasma's SSD post added.
      My Computer


  5. Posts : 26
    Windows 7 Ultimate 64bit
    Thread Starter
       #5

    I was having it run Driver Verifier overnight again and I got it to crash while I was asleep again. Dmp file is attached.
      My Computer


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

    I missed writhziden's post and your last post while I was composing this.
    Here's my suggestions that I typed previous to that:

    We've seen a number of BSOD issues with SSD's recently. Here's the information that I've compiled:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
    - Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
    Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
    You have AMD OverDrive installed, please do the following:
    - uninstall all ATI stuff from Control Panel...Programs...Uninstall a program
    - download and install the latest drivers from ATI Radeon
    - check perfmon /report to see if the AODDriver is still mentioned near the top of the report (under Diagnostic Reports - Errors, Warnings, and Informational sections)

    Beyond that, this is likely to be a hardware problem. If overclocking, please stop while we're troubleshooting.
    Post back if the above stuff hasn't fixed the BSOD's and we'll move on to hardware diagnostics.

    Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

    The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
    3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
    - Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
    - Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
    - DO NOT use Windows Update or the Update Drivers function of Device Manager.
    - Please feel free to post back about any drivers that you are having difficulty locating.
    - Windows Update exceptions may be noted below for Windows drivers.
    Code:
    
    vmbus.sys        Sat Nov 20 04:57:29 2010 (4CE79B89)
    jraid.sys        Wed Jan 27 03:58:17 2010 (4B600029)
    SCDEmu.SYS       Mon Apr 12 04:52:25 2010 (4BC2DF49)
    nusb3hub.sys     Fri Nov 20 05:15:57 2009 (4B066C5D)
    winhv.sys        Sat Nov 20 04:20:02 2010 (4CE792C2)
    amdsata.sys      Wed Oct 07 16:13:09 2009 (4ACCF655)
    amdxata.sys      Wed Oct 07 16:13:10 2009 (4ACCF656)
    cpuz135_x64.sys  Tue Nov 09 08:33:36 2010 (4CD94DB0)
    AODDriver2.sys   Wed Jun 15 04:38:35 2011 (4DF86F8B)
    AppleCharger.sys Mon Apr 26 23:54:05 2010 (4BD65FDD)
    atikmpag.sys     Thu Sep 08 12:52:41 2011 (4E68F2D9)
    amdiox64.sys     Thu Feb 18 10:17:53 2010 (4B7D5A21)
    VKbms.sys        Thu Sep 30 12:16:33 2010 (4CA4B7E1)
    Rt64win7.sys     Mon Mar 22 05:57:14 2010 (4BA73EFA)
    GEARAspiWDM.sys  Mon May 18 08:17:04 2009 (4A1151C0)
    cmudaxp.sys      Thu Mar 10 02:44:15 2011 (4D78814F)
    nusb3xhc.sys     Fri Nov 20 05:16:01 2009 (4B066C61)
    usbfilter.sys    Tue Dec 22 03:26:22 2009 (4B3082AE)
    atikmdag.sys     Thu Sep 08 13:26:08 2011 (4E68FAB0)
    rtkio.sys        Sat Jun 20 02:00:25 2009 (4A3C7AF9)
    dump_amdsata.sys Wed Oct 07 16:13:09 2009 (4ACCF655)
    AtihdW76.sys     Tue Oct 18 03:09:49 2011 (4E9D263D)
    danew.sys        Tue Mar 23 04:37:33 2010 (4BA87DCD)
    nx6000.sys       Wed Jan 27 18:36:09 2010 (4B60CDE9)
    aswSP.SYS        Mon Nov 28 12:53:57 2011 (4ED3CAB5)
    aswMonFlt.sys    Mon Nov 28 12:52:10 2011 (4ED3CA4A)
    aswFsBlk.SYS     Mon Nov 28 12:51:52 2011 (4ED3CA38)
    aswTdi.SYS       Mon Nov 28 12:52:18 2011 (4ED3CA52)
    aswRdr.SYS       Mon Nov 28 12:52:20 2011 (4ED3CA54)
    aswSnx.SYS       Mon Nov 28 12:54:05 2011 (4ED3CABD)
    cmudaxp.sys      Thu Oct 28 04:27:22 2010 (4CC933EA)
    jraid.sys        Mon Jan 11 06:28:18 2010 (4B4B0B52)
    vsflt53.sys      Tue Apr 12 07:31:35 2011 (4DA43817)
    snapman.sys      Wed Mar 09 08:22:38 2011 (4D777F1E)
    timntr.sys       Thu Jul 29 13:29:24 2010 (4C51BA74)
    vididr.sys       Tue Apr 12 07:31:24 2011 (4DA4380C)
    AtiPcie.sys      Tue May 05 11:00:22 2009 (4A005486)
    CLBUDF.SYS       Wed Oct 07 02:42:23 2009 (4ACC384F)
    AsIO.sys         Thu Apr 22 07:18:03 2010 (4BD0306B)
    nusb3hub.sys     Thu Jan 21 22:22:18 2010 (4B5919EA)
    CLBStor.SYS      Wed Oct 07 02:42:27 2009 (4ACC3853)
    ASACPI.sys       Wed Jul 15 23:31:29 2009 (4A5E9F11)
    nusb3xhc.sys     Thu Jan 21 22:22:21 2010 (4B5919ED)
    usbfilter.sys    Wed Oct 07 03:44:08 2009 (4ACC46C8)
    athrx.sys        Tue Nov 23 19:11:58 2010 (4CEC584E)
    nvhda64v.sys     Thu Jul 07 12:21:14 2011 (4E15DCFA)
    000.fcl          Fri Sep 26 09:11:22 2008 (48DCDF7A)
    Rt64win7.sys     Thu Mar 04 08:42:52 2010 (4B8FB8DC)
    nvlddmkm.sys     Sat Oct 15 02:07:55 2011 (4E99233B)
    atikmpag.sys     Wed Nov 09 21:12:44 2011 (4EBB331C)
    EIO64.sys        Tue Jul 21 22:34:42 2009 (4A667AC2)
    atikmdag.sys     Wed Nov 09 21:52:46 2011 (4EBB3C7E)
    IOMap64.sys      Thu Feb 04 20:55:34 2010 (4B6B7A96)
    
    http://www.carrona.org/drivers/driver.php?id=vmbus.sys
    http://www.carrona.org/drivers/driver.php?id=jraid.sys
    http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
    http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys
    http://www.carrona.org/drivers/driver.php?id=winhv.sys
    http://www.carrona.org/drivers/driver.php?id=amdsata.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=cpuz135_x64.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=amdiox64.sys
    http://www.carrona.org/drivers/driver.php?id=VKbms.sys
    http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=cmudaxp.sys
    http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=rtkio.sys
    http://www.carrona.org/drivers/driver.php?id=dump_amdsata.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
    http://www.carrona.org/drivers/driver.php?id=danew.sys
    http://www.carrona.org/drivers/driver.php?id=nx6000.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.SYS
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswFsBlk.SYS
    http://www.carrona.org/drivers/driver.php?id=aswTdi.SYS
    http://www.carrona.org/drivers/driver.php?id=aswRdr.SYS
    http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS
    http://www.carrona.org/drivers/driver.php?id=cmudaxp.sys
    http://www.carrona.org/drivers/driver.php?id=jraid.sys
    http://www.carrona.org/drivers/driver.php?id=snapman.sys
    http://www.carrona.org/drivers/driver.php?id=timntr.sys
    http://www.carrona.org/drivers/driver.php?id=CLBUDF.SYS
    http://www.carrona.org/drivers/driver.php?id=AsIO.sys
    http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys
    http://www.carrona.org/drivers/driver.php?id=CLBStor.SYS
    http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
    http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys
    http://www.carrona.org/drivers/driver.php?id=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=athrx.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=000.fcl
    http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=EIO64.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=IOMap64.sys

    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020412-20607-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Feb  4 01:47:36.006 2012 (UTC - 5:00)
    System Uptime: 0 days 0:06:02.146
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  Wow.exe
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_VRF_PROCESSOR_CACHE
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`05981028 00000000`b471a000 00000000`21000135
    BiosVersion = F4
    BiosReleaseDate = 07/23/2010
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020312-13540-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Fri Feb  3 23:58:29.606 2012 (UTC - 5:00)
    System Uptime: 4 days 6:57:35.627
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Wow.exe
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`04b01028 00000000`b62a4000 00000000`00000135
    BiosVersion = F4
    BiosReleaseDate = 07/23/2010
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020312-15100-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Fri Feb  3 01:19:29.929 2012 (UTC - 5:00)
    System Uptime: 0 days 0:01:19.505
    BugCheck D1, {0, 2, 8, 0}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+33c803 )
    PROCESS_NAME:  System
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nvlddmkm+33c803
    Bugcheck code 000000D1
    Arguments 00000000`00000000 00000000`00000002 00000000`00000008 00000000`00000000
    BiosVersion = 2301   
    BiosReleaseDate = 07/18/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011912-12183-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Jan 19 02:29:31.129 2012 (UTC - 5:00)
    System Uptime: 1 days 2:13:41.253
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Wow.exe
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    Bugcheck code 00000124
    Arguments 00000000`00000000 fffffa80`04b11028 00000000`b6004000 00000000`15000135
    BiosVersion = F4
    BiosReleaseDate = 07/23/2010
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011712-11622-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Tue Jan 17 23:54:29.197 2012 (UTC - 5:00)
    System Uptime: 0 days 0:08:15.290
    BugCheck D1, {fffff880013440a4, 2, 8, fffff880013440a4}
    Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+6e58 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  AvastSvc.exe
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+6e58
    Bugcheck code 000000D1
    Arguments fffff880`013440a4 00000000`00000002 00000000`00000008 fffff880`013440a4
    BiosVersion = F4
    BiosReleaseDate = 07/23/2010
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-11793-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sat Jan 14 21:25:19.908 2012 (UTC - 5:00)
    System Uptime: 0 days 17:48:39.672
    Probably caused by : hardware ( win32k!SetWakeBit+f8 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
    Bugcheck code 0000000A
    Arguments 00000000`00000003 00000000`00000002 00000000`00000001 fffff800`02ee3ce5
    BiosVersion = F4
    BiosReleaseDate = 07/23/2010
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  7. Posts : 26
    Windows 7 Ultimate 64bit
    Thread Starter
       #7

    While attempting to update drivers and BIOS I received another BSOD, this time with a new code. Dump files attached one more time, along with the File Collection.

    This is getting extremely aggravating =\ Driver Verifier was running during this crash as well.
      My Computer


  8. Posts : 26
    Windows 7 Ultimate 64bit
    Thread Starter
       #8

    bumping this with saying that now my machine will refuse to POST sometimes, giving me beeping errors and a black screen until I hold down power and restart the computer. Also, it seems to sometimes hang when loading the OS from my solid state drive.

    I'm starting to think it may be the MOBO/time for a replacement?
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Mike\Downloads\crash info\020412-15615-01\020412-15615-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`03052670
    Debug session time: Sat Feb  4 11:05:57.556 2012 (GMT-7)
    System Uptime: 0 days 0:15:51.350
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C1, {fffff98018fc8ff0, fffff98018fc8ffc, 37000c, 24}
    
    Unable to load image \??\C:\Windows\gdrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for gdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
    Probably caused by : gdrv.sys ( gdrv+30c7 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98018fc8ff0, address trying to free
    Arg2: fffff98018fc8ffc, address where bits are corrupted
    Arg3: 000000000037000c, (reserved)
    Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC1_24
    
    SPECIAL_POOL_CORRUPTION_TYPE:  24
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  gwflash.exe
    
    CURRENT_IRQL:  1
    
    IRP_ADDRESS:  fffffa80057ad06b
    
    LAST_CONTROL_TRANSFER:  from fffff80002f8bb54 to fffff80002e89c40
    
    STACK_TEXT:  
    fffff880`0ba124d8 fffff800`02f8bb54 : 00000000`000000c1 fffff980`18fc8ff0 fffff980`18fc8ffc 00000000`0037000c : nt!KeBugCheckEx
    fffff880`0ba124e0 fffff800`02fb793b : fffff800`02e0d000 00000000`20206f49 00000000`000383a1 fffffa80`045d44b0 : nt!MmFreeSpecialPool+0x374
    fffff880`0ba12620 fffff800`02e9f09e : 00000000`00000000 fffffa80`057ad0e0 fffffa80`045ad0e0 fffffa80`080add30 : nt!ExDeferredFreePool+0xf33
    fffff880`0ba126d0 fffff800`02e8d34a : fffffa80`057ad0e3 00000000`00000001 00000000`00000001 fffff800`02f46803 : nt!IopCompleteRequest+0x5ce
    fffff880`0ba127a0 fffff800`0332919f : fffffa80`057ad010 fffffa80`0535b000 fffffa80`057ad000 00000000`00000000 : nt!IopfCompleteRequest+0x66a
    fffff880`0ba12890 fffff880`099970c7 : fffff880`09997a50 00000000`00000008 00000000`00000000 fffffa80`057ad0e0 : nt!IovCompleteRequest+0x19f
    fffff880`0ba12960 fffff880`09997a50 : 00000000`00000008 00000000`00000000 fffffa80`057ad0e0 00000000`00000001 : gdrv+0x30c7
    fffff880`0ba12968 00000000`00000008 : 00000000`00000000 fffffa80`057ad0e0 00000000`00000001 00000000`00000000 : gdrv+0x3a50
    fffff880`0ba12970 00000000`00000000 : fffffa80`057ad0e0 00000000`00000001 00000000`00000000 00000000`00000001 : 0x8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    gdrv+30c7
    fffff880`099970c7 ??              ???
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  gdrv+30c7
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: gdrv
    
    IMAGE_NAME:  gdrv.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49b9d175
    
    FAILURE_BUCKET_ID:  X64_0xC1_24_VRF_gdrv+30c7
    
    BUCKET_ID:  X64_0xC1_24_VRF_gdrv+30c7
    
    Followup: MachineOwner
    ---------
    Update gdrv.sys from from GIGABYTE - Motherboard - Socket AM3 - GA-890FXA-UD5 (rev. 2.0)
    Code:
        Loaded symbol image file: gdrv.sys
        Image path: \??\C:\Windows\gdrv.sys
        Image name: gdrv.sys
        Timestamp:        Thu Mar 12 21:22:29 2009 (49B9D175)
        CheckSum:         000105CE
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    faunts said:
    bumping this with saying that now my machine will refuse to POST sometimes, giving me beeping errors and a black screen until I hold down power and restart the computer. Also, it seems to sometimes hang when loading the OS from my solid state drive.

    I'm starting to think it may be the MOBO/time for a replacement?
    Your system is going to be very unstable with Verifier running. It does not mean the motherboard is bad. We will have to determine the cause yet and see if it is a hardware issue.

    You can disable verifier by running an Elevated Command Prompt and typing verifier /reset if you want more stability.
      My Computer


  10. Posts : 26
    Windows 7 Ultimate 64bit
    Thread Starter
       #10

    Weird, I dont think I ever installed the Easy Energy Saver from Gigabyte. Oh well, I will now. Will report back what I find.
      My Computer


 
Page 1 of 5 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 01:07.
Find Us