DRIVER_IRQL_NOT_LESS_OR_EQUAL on a fresh install of Win 7 64-bit

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by CrashmanX, Jan 14, 2013.

  1. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    Copy/Pasted from the other thread (I'm sorry! I made it in the wrong sub-forum!)

    Hey there, a bit new to these forums but trying to figure out what exactly is going on. About 2 weeks ago I installed a Wireless card into my PC, I started getting very random and odd blue screens. I attributed them to the Wireless card and removed it. About 1 week ago I decided to re-install Windows 7 (64-Bit, Ultimate) because the blue screens were persisting and they seemed to be driver related. I had been doing fine and not getting any Blue Screens till yesterday and today. I'm now up to 3 already and they're all IRQL_NOT_LESS_OR_EQUAL. Now I fear this would mean RAM issue but I had MemTest 86 going for over 9 hours and it came up with no errors. So I'm not 100% sure what the issue is. I've tried using WinDbg to figure out the cause but it keeps coming back to Ntkrnlmp.exe, which I'm not 100% exactly what the program does but I do know it's an integral part of Windows 7 for Multi-core machines.

    Any help would be appreciated. (Minidumps attached)View attachment 22277

    Few more BSOD'sView attachment 22290
     
  2. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Was the Wireless Card from:
    A) a USB/Plug in (Putting it into a USB Port/Firewire/Any other external port)
    B) Integrated/Dedicated (which you stuck on to your motherboard, opposed to the first option)

    Did you also install the correct drivers for the card, without any problem?

    Also use this tool: http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html to collect the minidumps and other important info - minidumps aren't conclusive, AND I don't have my minidump analyzer with me.

    How did you reinstall Windows? There could be a possibility that the reinstall didn't go so well, and may have gotten corrupted some where along the line.
    (IMO: Reinstalling Windows should always be the last choice)

    Have you tried updating your:
    Chipset Drivers
    Network Drivers
    BIOS
     
  3. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    Integrated PCI Wireless Card. A RealTek 8185L to be exact.
    The drivers were a bit of a bitch to install. I had to use the generic drivers that came with the package in-order for it to connect at all. Which I was fine with, I only needed a basic connection. Once I was having issues with it though I did my best to remove it and switched over to an Asus USB which worked fine.
    AFTER that however I re-formatted and Re-installed windows via Flash Drive that I had setup using Microsoft's ISO-To-USB program.
    Installation went fine, however at end it mentioned being unable to read the flash drive, but the installation was already complete so I thought nothing of it.

    Already checked for Chipset, Network, and BIOS updates. Nothin. Everything is up to date. I initially thought Drivers might've been an issue but that's seeming to not be the case.

    After a few more Bluescreens I'm beginning to fear something may have gone wrong on the Mother Board. I want to be sure though before I make a conclusion.

    View attachment BSOD.zip
    All bundled up and attached.
     
    #3 CrashmanX, Jan 15, 2013
    Last edited: Jan 15, 2013
  4. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    These are difficult to analyze without the help of Driver Verifier. Please follow the instructions on the linked article carefully otherwise it may give us false readings. Send us any resulting crashdumps after it has been enabled (remember to restart after setup). If it causes a boot loop, you can go into Safe Mode and disable it from there. If you cannot get into Safe Mode, then you have a bigger problem than just software (hardware issue), since DV is not active on Safe Mode so something else is causing it.
     
  5. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    Well, anymore I'm fairly certain it isn't drivers. I fear it may be my Mother Board actually.
    Since the error occurred with some different drivers I feared that may have been the issue initially. However since the same error occurs without said drivers it led me to believe that the issue was Hardware. I've tried all configurations of my RAM (2x4GB 1333 and 2x1GB native 1600 clocked down to 1333) and I still end up with the same BSOD (this includes removing each stick).
    I just want to be certain it's the Mobo.

    However I will install Driver Verifier and I'll update this post later with any BSODs after it has been installed.
     
  6. Vir Gnarus

    Vir Gnarus Active Member

    Joined:
    Jan 8, 2013
    Messages:
    199
    Likes Received:
    9
    You don't need to install it, it's already in Windows. You just need to set it up, restart system, let the system crash a time or two, and then send us the resulting crashdumps. Simple. :)

    Even if it is a hardware issue, the DV-related crashdumps may provide some more reliable details to go on. Granted with hardware anything can happen, but at least with DV on one can safely and completely rule out drivers as suspect.
     
  7. GeneralHiningII

    GeneralHiningII Honorable Member

    Joined:
    Sep 21, 2012
    Messages:
    745
    Likes Received:
    7
    Unless DV bricks your computer.But, like Vir said, give it a run any way. If it crashes, you know one of your drivers is bad.If it runs through without a problem, then we can probably blame the motherboard (or... >)
     
  8. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    OK. Well I tried using Driver Verifier, however, whenever it'd normally blue screen (Being under a decent load) it'd just lock up the whole system and I'd have to force a restart. Had to disable Verifier for the time being.
     
  9. jcgriff2

    jcgriff2 Honorable Member
    Microsoft MVP

    Joined:
    Sep 12, 2009
    Messages:
    195
    Likes Received:
    29
  10. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    Unfortunately I have no way of running the SeaTools right now as I don't have a Disc Burner nor a floppy drive installed ATM.
    Does a program already exist to use the ISO and make a bootable flash drive out of it?
    That aside, I don't believe it's the Hard Drive going bad. I haven't gotten an NTFS error outside of the first. I initially thought HDD as well but I haven't run across anything else that would suggest such. All programs have installed just fine and everything reads/writes without an issue. Not saying it's not the problem, just a little doubtful.
     
  11. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    Bumping for a little hope and new Minidumps. Still getting BSOD's after doing just about everything hardware side short of replacing the MoBo/CPU. Even tried switching over to internal video for a while (Both ATI so they share drivers) and I still had the issue.
     

    Attached Files:

  12. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Use Yumi (free here: YUMI - Multiboot USB Creator (Windows) | USB Pen Drive Linux ) to make a flash drive that can boot all sorts of ISO's. Learning curve is a bit steep at first, but just follow the instructions. Then you'll be able to easily boot to any ISO.

    When using it, scroll to the bottom of STEP 2 in order to add an ISO.
    Run the Yumi exe file each time you want to add another ISO to it.
    Copy the Yumi exe to the flash drive and you'll be able to run it wherever you are.

    Download the Seatools ISO from here: SeaTools for DOS | Seagate And use it on both hard drives (run the long/extended test).

    Please un-install the wireless USB X-Box controller and physically remove the device from your system. The drivers date from 2009 and are known to cause BSOD's in some Win7 systems (and AFAIK there aren't any updates available). After we've stopped the BSOD's, please feel free to try it again, but understand that it may start BSODing again (and the fix is to completely remove it).

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    Analysis:
    The following is for informational purposes only.
    Code:
    [FONT=lucida console]**************************Mon Jan 28 02:14:00.920 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012813-27190-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 3:38:07.559[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!KeWaitForSingleObject+65 )[/B]
    BugCheck [B]1E, {ffffffffc0000096, fffff80002ed4c55, 0, 0}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001E"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL]
    Arguments: 
    Arg1: ffffffffc0000096, The exception code that was not handled
    Arg2: fffff80002ed4c55, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000096
    PROCESS_NAME: [B]TESV.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x1E_c0000096_nt!KeWaitForSingleObject+65[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sun Jan 27 22:35:11.689 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012713-24242-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]1 days 7:45:09.327[/B]
    Probably caused by :[B]win32k.sys ( win32k!NtUserWindowFromPoint+1c )[/B]
    BugCheck [B]A, {fffff8002367fb88, 2, 1, fffff80002eee099}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
    Arguments: 
    Arg1: fffff8002367fb88, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002eee099, address which referenced memory
    BUGCHECK_STR:  0xA
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]Skype.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0xA_win32k!NtUserWindowFromPoint+1c[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sat Jan 26 00:19:09.075 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012513-28204-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 21:26:53.340[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiRetireDpcList+1a9 )[/B]
    BugCheck [B]A, {1c4, 2, 0, fffff80002e996d9}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
    Arguments: 
    Arg1: 00000000000001c4, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002e996d9, address which referenced memory
    BUGCHECK_STR:  0xA
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]chrome.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiRetireDpcList+1a9[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Jan 25 02:23:40.620 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012513-34164-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]1 days 3:22:57.884[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!SwapContext+0 )[/B]
    BugCheck [B]A, {80, 2, 0, fffff80002e86120}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
    Arguments: 
    Arg1: 0000000000000080, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002e86120, address which referenced memory
    BUGCHECK_STR:  0xA
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0xA_nt!SwapContext+0[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Wed Jan 23 23:00:09.039 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-27814-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 3:30:07.303[/B]
    Probably caused by :[B]USBPORT.SYS ( USBPORT!USBPORT_Core_InitTimeout+1d )[/B]
    BugCheck [B]1E, {0, 0, 0, 0}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001E"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL]
    Arguments: 
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]audiodg.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x1E_USBPORT!USBPORT_Core_InitTimeout+1d[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Wed Jan 23 19:29:07.565 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\012313-32385-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]3 days 3:55:42.830[/B]
    Probably caused by :[B]USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSetState+46 )[/B]
    BugCheck [B]D1, {4f444648, 2, 0, fffff880042f35de}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x000000D1"]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/URL]
    Arguments: 
    Arg1: 000000004f444648, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880042f35de, address which referenced memory
    BUGCHECK_STR:  0xD1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+46[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sat Jan 19 23:15:47.789 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011913-52759-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 4:55:31.428[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48d4a )[/B]
    BugCheck [B]18, {fffffa800822eb40, fffffa800a89e970, 1, 1}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000018"]REFERENCE_BY_POINTER (18)[/URL]
    Arguments: 
    Arg1: fffffa800822eb40, Object type of the object whose reference count is being lowered
    Arg2: fffffa800a89e970, Object whose reference count is being lowered
    Arg3: 0000000000000001, Reserved
    Arg4: 0000000000000001, Reserved
        The reference count of an object is illegal for the current state of the object.
        Each time a driver uses a pointer to an object the driver calls a kernel routine
        to increment the reference count of the object. When the driver is done with the
        pointer the driver calls another kernel routine to decrement the reference count.
        Drivers must match calls to the increment and decrement routines. This bugcheck
        can occur because an object's reference count goes to zero while there are still
        open handles to the object, in which case the fourth parameter indicates the number
        of opened handles. It may also occur when the object?s reference count drops below zero
        whether or not there are open handles to the object, and in that case the fourth parameter
        contains the actual value of the pointer references count.
    BUGCHECK_STR:  0x18
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]hl2.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+48d4a[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Wed Jan 16 20:44:04.150 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011613-29218-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:29:26.789[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )[/B]
    BugCheck [B]7F, {8, 80050031, 6f8, fffff80002eac4de}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000007F"]UNEXPECTED_KERNEL_MODE_TRAP (7f)[/URL]
    Arguments: 
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff80002eac4de
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME: [B]NexusClient.ex[/B]
    FAILURE_BUCKET_ID: [B]X64_0x7f_8_nt!KiDoubleFaultAbort+b2[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Wed Jan 16 00:00:36.982 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011513-21840-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 4:58:27.262[/B]
    Probably caused by :[B]hardware ( USBPORT!USBPORT_InitializeIsoTransfer+4ad )[/B]
    BugCheck [B]1E, {0, 0, 0, 0}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000001E"]KMODE_EXCEPTION_NOT_HANDLED (1e)[/URL]
    Arguments: 
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]audiodg.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Tue Jan 15 19:01:35.503 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011513-24242-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 19:55:35.783[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
    BugCheck [B]D1, {fffff80000000000, 2, 8, fffff80000000000}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x000000D1"]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/URL]
    Arguments: 
    Arg1: fffff80000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff80000000000, address which referenced memory
    BUGCHECK_STR:  0xD1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]System[/B]
    FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Jan 14 22:55:19.506 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011413-19422-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 1:02:41.160[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiRetireDpcList+1a9 )[/B]
    BugCheck [B]A, {1c4, 2, 0, fffff80002e996d9}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
    Arguments: 
    Arg1: 00000000000001c4, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002e996d9, address which referenced memory
    BUGCHECK_STR:  0xA
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]winamp.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiRetireDpcList+1a9[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Jan 14 21:52:01.839 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011413-23119-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 20:09:22.493[/B]
    Probably caused by :[B]ntkrnlmp.exe ( nt!KiRetireDpcList+1a9 )[/B]
    BugCheck [B]A, {1c4, 2, 0, fffff80002eea6d9}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000000A"]IRQL_NOT_LESS_OR_EQUAL (a)[/URL]
    Arguments: 
    Arg1: 00000000000001c4, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002eea6d9, address which referenced memory
    BUGCHECK_STR:  0xA
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]chrome.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiRetireDpcList+1a9[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Jan 14 01:39:30.508 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011413-29343-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:58:10.803[/B]
    Probably caused by :[B]hardware ( win32k!HmgLockEx+122 )[/B]
    BugCheck [B]50, {fffffa81025a36d1, 1, fffff80002eddc6d, 5}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000050"]PAGE_FAULT_IN_NONPAGED_AREA (50)[/URL]
    Arguments: 
    Arg1: fffffa81025a36d1, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002eddc6d, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    BUGCHECK_STR:  0x50
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]Steam.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Jan 14 00:40:46.920 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011313-49218-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:06:15.200[/B]
    Probably caused by :[B]Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+2bf0 )[/B]
    BugCheck [B]D1, {fffff8800133b0c0, 0, 8, fffff8800133b0c0}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x000000D1"]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/URL]
    Arguments: 
    Arg1: fffff8800133b0c0, memory referenced
    Arg2: 0000000000000000, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff8800133b0c0, address which referenced memory
    BUGCHECK_STR:  0xD1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]uTorrent.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2bf0[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sun Jan 13 22:54:19.758 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011313-39031-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 0:09:07.022[/B]
    Probably caused by :[B]AuthenticAMD[/B]
    BugCheck [B]124, {0, fffffa800946f028, b6004000, 5d000135}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800946f028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b6004000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000005d000135, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME: [B]chrome.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Sun Jan 13 22:44:36.334 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\011313-40934-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime:[B]0 days 7:14:53.599[/B]
    Probably caused by :[B]hardware ( nt!MiInitializePfn+b7 )[/B]
    BugCheck [B]50, {fffffa8051aeb6a1, 0, fffff80002eda507, 5}[/B]
    BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000050"]PAGE_FAULT_IN_NONPAGED_AREA (50)[/URL]
    Arguments: 
    Arg1: fffffa8051aeb6a1, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002eda507, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    BUGCHECK_STR:  0x50
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME: [B]chrome.exe[/B]
    FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED[/B]
      BIOS Version                  V3.11
      BIOS Release Date             05/24/2011
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7576
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    [/FONT]
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    [FONT=lucida console]**************************Mon Jan 28 02:14:00.920 2013 (UTC - 5:00)**************************
    LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
    LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
    amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    Rt64win7.sys                Thu Feb 16 00:39:50 2012 (4F3C96A6)
    [COLOR=RED][B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
    MpFilter.sys                Thu Aug 23 19:03:14 2012 (5036B6B2)
    kerneld.x64                 Sun Oct 28 07:04:11 2012 (508D112B)
    AtihdW76.sys                Tue Nov  6 16:41:51 2012 (5099841F)
    RTKVHD64.sys                Tue Nov 20 06:10:14 2012 (50AB6516)
    atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
    atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Fri Jan 25 02:23:40.620 2013 (UTC - 5:00)**************************
    AtihdW76.sys                Fri May 11 04:25:40 2012 (4FACCD04)
    atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Wed Jan 23 19:29:07.565 2013 (UTC - 5:00)**************************
    [COLOR=RED][B]xusb21.sys                  Wed Apr  8 10:28:44 2009 (49DCB49C)[/B][/COLOR]
    MijXfilt.sys                Sat May 12 00:27:12 2012 (4FADE6A0)
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Tue Jan 15 19:01:35.503 2013 (UTC - 5:00)**************************
    DirectIo64.sys              Mon Aug 13 00:30:24 2012 (502882E0)
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    **************************Mon Jan 14 22:55:19.506 2013 (UTC - 5:00)**************************
    X6va011                     Tue Sep 11 01:16:02 2012 (504EC912)
    [/FONT]
    http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
    http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
    http://www.carrona.org/drivers/driver.php?id=kerneld.x64
    http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=xusb21.sys
    http://www.carrona.org/drivers/driver.php?id=MijXfilt.sys
    DirectIo64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    X6va011 - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
     
  13. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    Both MotionJoy (Which installs said Xbox Drivers) and AMD OverDrive were installed well before BSODs became a problem. Neither of which are in use or even active when the machine BSODs. I doubt those are the problem, but I'll remove them just to see.
    Thanks for the links to Yumi. I'll test the HDDs later today.
     
  14. usasma

    usasma Fantastic Member
    Microsoft Community Contributor

    Joined:
    Mar 22, 2010
    Messages:
    3,048
    Likes Received:
    83
    Back in the XP days BSOD's were fairly straight forward.
    Since Vista, they've become progressively more complicated.

    Now it's rare to find one that doesn't have components of several different problems.

    Although it may have had those programs for a while before the BSOD's started, that doesn't mean that they can't cause it.
    Although the programs may have been present before the BSOD's started - your system is not a static device. It changes with each download/update/setting change that is made. If you have a poorly designed driver, it may work with Windows the way it is now - but when Windows Updates come out it may not work with them. IMO this is a major cause of problems - and is why we identify older drivers when analyzing BSOD's.
     
  15. CrashmanX

    CrashmanX New Member

    Joined:
    Jan 12, 2013
    Messages:
    18
    Likes Received:
    0
    OK well I removed motion joy and installed just the AMD Driver (No CCC) so we'll see how long before we BSOD if at all. If I BSOD within the next few days I'll run the HDD tests to be sure.
     

Share This Page

Loading...