none
bad_pool_caller BSOD windows 8.1 pro

    Question

  • Hi. Several times a week i get BSOD about bad_pool_caller or irq_less... so I would kindly ask for help. here is one minidump.

    https://onedrive.live.com/redir?resid=FBD3C7D7FBA9DAD0%214817

    thanks!

    Tuesday, April 22, 2014 7:00 AM

Answers

  • WDF_VIOLATION (10D)

    This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.

    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`2042e3e8 fffff800`90275caa nt!KeBugCheckEx
    ffffd000`2042e3f0 fffff800`9024636f Wdf01000!FxVerifierBugCheck+0x1e
    ffffd000`2042e430 fffff800`9022625a Wdf01000!FxIoTarget::SubmitLocked+0x3e63f
    ffffd000`2042e4d0 fffff800`9020802d Wdf01000!FxIoTarget::Submit+0x3a
    ffffd000`2042e500 fffff800`92b71d7a Wdf01000!imp_WdfRequestSend+0x12d
    ffffd000`2042e560 ffffe001`46871710 netr28ux+0xd1d7a
    ffffd000`2042e568 ffffe001`469848c0 0xffffe001`46871710
    ffffd000`2042e570 ffffe001`46864c60 0xffffe001`469848c0
    ffffd000`2042e578 ffffe001`46984a60 0xffffe001`46864c60
    ffffd000`2042e580 fffff800`92ce68c0 0xffffe001`46984a60
    ffffd000`2042e588 00001ffe`b979b398 netr28ux+0x2468c0
    ffffd000`2042e590 ffffd000`2042ea6c 0x00001ffe`b979b398
    ffffd000`2042e598 fffff800`92b715af 0xffffd000`2042ea6c
    ffffd000`2042e5a0 00001ffe`b967b738 netr28ux+0xd15af
    ffffd000`2042e5a8 00001ffe`b979b398 0x00001ffe`b967b738
    ffffd000`2042e5b0 fffff800`92cead00 0x00001ffe`b979b398
    ffffd000`2042e5b8 ffffe001`46984a60 netr28ux+0x24ad00
    ffffd000`2042e5c0 ffffd000`2042ea00 0xffffe001`46984a60
    ffffd000`2042e5c8 fffff800`0002b6cc 0xffffd000`2042ea00
    ffffd000`2042e5d0 00001ffe`00000968 0xfffff800`0002b6cc
    ffffd000`2042e5d8 00001ffe`b979b300 0x00001ffe`00000968
    ffffd000`2042e5e0 fffff800`92bf0fc8 0x00001ffe`b979b300
    ffffd000`2042e5e8 fffff800`92bf1c3c netr28ux+0x150fc8
    ffffd000`2042e5f0 ffffe001`00000000 netr28ux+0x151c3c
    ffffd000`2042e5f8 00001ffe`b967b738 0xffffe001`00000000
    ffffd000`2042e600 ffffe001`46984a60 0x00001ffe`b967b738
    ffffd000`2042e608 00000000`00000000 0xffffe001`46984a60
    

    ^^ netr28ux.sys attempted to send a framework request that has already been sent to an I/O target.

    This is the Ralink RT2870 series USB802.11n Wireless Adapter driver (you may have a different manufacturer).

    Ensure yours is up to date regarding its drivers, or remove it from the equation (what I recommend) for troubleshooting purposes.

    Regards,

    Patrick


    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Thursday, April 24, 2014 6:19 PM

All replies

  • Hi,

    The attached DMP file is of the BAD_POOL_CALLER (c2) bug check.

    This indicates that the current thread is making a bad pool request.

    BugCheck C2, {7, 1200, 0, ffffc00186b2f840}

    2: kd> !pool ffffc00186b2f840
    Pool page ffffc00186b2f840 region is Unknown
     ffffc00186b2f000 size:  1a0 previous size:    0  (Allocated)  FMfn
     ffffc00186b2f1a0 size:   40 previous size:  1a0  (Allocated)  ViMm
     ffffc00186b2f1e0 size:   90 previous size:   40  (Allocated)  FSim
     ffffc00186b2f270 size:  150 previous size:   90  (Allocated)  ViMm
     ffffc00186b2f3c0 size:   40 previous size:  150  (Allocated)  DxgK
     ffffc00186b2f400 size:  110 previous size:   40  (Allocated)  IoNm
     ffffc00186b2f510 size:  1a0 previous size:  110  (Allocated)  FMfn
     ffffc00186b2f6b0 size:   c0 previous size:  1a0  (Allocated)  FIcs
     ffffc00186b2f770 size:   40 previous size:   c0  (Allocated)  NtFs
     ffffc00186b2f7b0 size:   60 previous size:   40  (Allocated)  CMpb Process: f98e18d9ecd92d7c
    *ffffc00186b2f810 size:   40 previous size:   60  (Allocated) *MmSm
    		Pooltag MmSm : segments used to map data files, Binary : nt!mm
     ffffc00186b2f850 size:  160 previous size:   40  (Allocated)  DxgK
     ffffc00186b2f9b0 size:  140 previous size:  160  (Allocated)  NtFS
     ffffc00186b2faf0 size:  510 previous size:  140  (Allocated)  Ntff
    

    ^^ MmSm - Segments used to map data files.

    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`20cf3998 fffff803`ee51a42a nt!KeBugCheckEx
    ffffd000`20cf39a0 fffff800`3be5f3c9 nt!ExFreePoolWithTag+0x114a
    ffffd000`20cf3a70 fffff800`3bec840c dxgkrnl!`vector destructor iterator'+0x31
    ffffd000`20cf3aa0 fffff800`3becb0b1 dxgkrnl!DXGSHAREDRESOURCE::~DXGSHAREDRESOURCE+0x40
    ffffd000`20cf3ad0 fffff800`3bec6ec5 dxgkrnl!DXGSHAREDRESOURCE::Destroy+0x1d
    ffffd000`20cf3b00 fffff800`3bec81ab dxgkrnl!DXGDEVICE::DestroyAllocations+0x6c5
    ffffd000`20cf3c10 fffff800`3bec5f81 dxgkrnl!DXGDEVICE::DestroyResource+0x5f
    ffffd000`20cf3c50 fffff800`3bec33e0 dxgkrnl!DXGDEVICE::ProcessTerminationList+0x1e9
    ffffd000`20cf3cd0 fffff803`ee3e37b3 dxgkrnl!DxgkCreateAllocation+0x340
    ffffd000`20cf3e40 00000000`77d6738a nt!KiSystemServiceCopyEnd+0x13
    00000000`0353cce8 00000000`00000000 0x77d6738a
    

    ^^ DirectX Kernel (dxgkrnl) was the kernel mode routine that caused the bug check. Generally when we see Windows kernel mode drivers attempting to access invalid memory, bad IRQLs, etc, it's because of a hardware fault.. or a 3rd party driver causing conflicts.

    -------------------

    1.


    2: kd> lmvm NTIOLib_X64
    start             end                 module name
    fffff800`3dd8c000 fffff800`3dd93000   NTIOLib_X64   (deferred)             
        Image path: \??\C:\Program Files (x86)\MSI\CommandCenter\CPU\NTIOLib_X64.sys
        Image name: NTIOLib_X64.sys
        Timestamp:        Tue Nov 20 00:14:23 2012

    ^^ MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5. Uninstall ASAP.

    2. If the above fails, please run Memtest for NO LESS than ~8 passes (several hours):

    Memtest86+:

    Download Memtest86+ here:

    http://www.memtest.org/

    Which should I download?

    You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

    Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

    How Memtest works:

    Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

    The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

    Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

    Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

    This information, if available to the program, can be displayed via a menu option.

    Any other questions, they can most likely be answered by reading this great guide here:

    http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Tuesday, April 22, 2014 6:11 PM
  • thanks for your help. i uninstalled msi live update and command center. i use the memtest often, but it never shows any problems. i also had an asus hd7750 graphics card and i received bsods almost every day for atikmdag.sys or different "ati" and directx things so i took it out. i'll just wait and see what happens :)

    Tuesday, April 22, 2014 6:21 PM
  • How long do you run Memtest for?

    Also, the GPU was my next point of discussion. If Memtest showed no errors for ~8 passes and crashes continued after the removal of MSI, it's likely a faulty GPU.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Tuesday, April 22, 2014 6:24 PM
  • i normally let it run for 12hours or more, i forgot how many passes it was, and there were never any problems. my pc also never crashed with hd7750 while playing games, it always crashed while surfing the web or just doing normal stuff.
    Tuesday, April 22, 2014 6:32 PM
  • Thanks for the information.

    Keep me updated!

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Tuesday, April 22, 2014 6:34 PM
  • will do. and thank you!

    best regards,

    Jan

    Tuesday, April 22, 2014 6:37 PM
  • Great, my pleasure!

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Tuesday, April 22, 2014 6:39 PM
  • hi. so i left the memtest running for 9 passes and no problems, then again for 4 passes and again no errors. the whole day went without a bsod, then all of a sudden a bsod - no programs running, nothing, just desktop. here is the minidump:

    https://onedrive.live.com/redir?resid=FBD3C7D7FBA9DAD0%215215

    Wednesday, April 23, 2014 4:42 PM
  • KERNEL_SECURITY_CHECK_FAILURE (139)

    This bug check indicates that the kernel has detected the corruption of a critical data structure.

    BugCheck 139, {3, ffffd00021074410, ffffd00021074368, 0}
    

    ^^ The 1st parameter of the bugcheck is 3 which indicates that a LIST_ENTRY was corrupted. Code 3, LIST_ENTRY corruption. This type of bug check can be difficult to track down and indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list).

    2: kd> .exr 0xffffd00021074368
    ExceptionAddress: fffff801a262f9f7 (dxgmms1!VIDMM_LINEAR_POOL::Free+0x00000000000002af)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
    

    ^^ The exception occurred in dxgmms1!VIDMM_LINEAR_POOL::Free+0x2af.

    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`210740e8 fffff802`ca5e9ae9 nt!KeBugCheckEx
    ffffd000`210740f0 fffff802`ca5e9e10 nt!KiBugCheckDispatch+0x69
    ffffd000`21074230 fffff802`ca5e9034 nt!KiFastFailDispatch+0xd0
    ffffd000`21074410 fffff801`a262f9f7 nt!KiRaiseSecurityCheckFailure+0xf4
    ffffd000`210745a0 fffff801`a262f568 dxgmms1!VIDMM_LINEAR_POOL::Free+0x2af
    ffffd000`210745e0 fffff801`a262ff96 dxgmms1!VIDMM_PROCESS_HEAP::FreeSmallAllocation+0x90
    ffffd000`21074610 fffff801`a2631300 dxgmms1!VIDMM_PROCESS_HEAP::Free+0x46
    ffffd000`21074650 fffff801`a26315e0 dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xa0
    ffffd000`210746b0 fffff801`a2631430 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x150
    ffffd000`21074780 fffff801`a32ba983 dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x4c
    ffffd000`210747c0 fffff801`a32bc1ab dxgkrnl!DXGDEVICE::DestroyAllocations+0x183
    ffffd000`210748d0 fffff801`a32b9f81 dxgkrnl!DXGDEVICE::DestroyResource+0x5f
    ffffd000`21074910 fffff801`a32b73e0 dxgkrnl!DXGDEVICE::ProcessTerminationList+0x1e9
    ffffd000`21074990 fffff802`ca5e97b3 dxgkrnl!DxgkCreateAllocation+0x340
    ffffd000`21074b00 00007fff`a5e5138a nt!KiSystemServiceCopyEnd+0x13
    00000000`1c5bdee8 00000000`00000000 0x00007fff`a5e5138a
    

    At this point, possible faulty video card. I would go ahead and uninstall the video card drivers, shut down, physically remove the video card, and at this point either swap to integrated video (if available), or a secondary video card. Once you've done that, boot back into Windows and install the latest drivers for whichever you chose.

    Regards,

    Patrick


    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Wednesday, April 23, 2014 5:51 PM
  • as i said yesterday, i already took out my asus hd7750 because i had exactly the same issues and am using right now the integrated intel hd4600 and again the same issues. i deleted ati drivers, even did a clean install of windows and yet again and again i get the same errors. must be something software/driver related, i just can't pinpoint it.
    Wednesday, April 23, 2014 6:03 PM
  • My apologies, I missed that.

    This is not software/driver, that's for sure. If it is software, the only drivers I can really see having this sort of DirectX related impact are the video card drivers. With this said, ensure you are on the latest drivers, and if you already are, try a few versions before, or perhaps the beta if available.

    In the 0xC2, the pool was valid, yet there was a 7 as the first parameter. This indicates that the current thread attempted to free the pool, which was already freed. We can see that it was a DirectX Kernel routine, because it calls into nt!ExFreePoolWithTag.

    The second bug check I've seen here, 0x139, was introduced due to security failure interruption. In your case, this was also caused by DirectX.

    -------------------

    To be absolutely sure this isn't a low-level driver possibly causing corruption, could you please do two things?

    1. Upload and paste the link to a kernel-dump. Kernel-dumps are located at C:\Windows and named MEMORY.DMP. If there is nothing there, you may need to enable generation of them - http://msdn.microsoft.com/en-us/library/windows/hardware/ff540128%28v=vs.85%29.aspx

    2. Enable Driver Verifier:

    Driver Verifier:

    What is Driver Verifier?

    Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

    Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

    Before enabling Driver Verifier, it is recommended to create a System Restore Point:

    Vista - START | type rstrui - create a restore point
    Windows 7 - START | type create | select "Create a Restore Point"
    Windows 8/8.1 - http://www.eightforums.com/tutorials/4690-restore-point-create-windows-8-a.html

    How to enable Driver Verifier:

    Start > type "verifier" without the quotes > Select the following options -

    1. Select - "Create custom settings (for code developers)"
    2. Select - "Select individual settings from a full list"
    3. Check the following boxes -
    - Special Pool
    - Pool Tracking
    - Force IRQL Checking
    - Deadlock Detection
    - Security Checks (Windows 7 & 8)
    - DDI compliance checking (Windows 8)
    - Miscellaneous Checks
    4. Select  - "Select driver names from a list"
    5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
    6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
    7. Click on Finish.
    8. Restart.

    Important information regarding Driver Verifier:

    - If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

    - After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

    If this happens, do not panic, do the following:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > Search > type "cmd" without the quotes.

    - To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
    ・    Restart and boot into normal Windows.

    If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

    - Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

    - Once in Safe Mode - Start > type "system restore" without the quotes.

    - Choose the restore point you created earlier.

    -- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

    How long should I keep Driver Verifier enabled for?

    I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

    My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

    They will be located in %systemroot%\Minidump

    Any other questions can most likely be answered by this article:
    http://support.microsoft.com/kb/244617

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Wednesday, April 23, 2014 6:21 PM
  • hi. i just received another bsod dxgmms1.sys. "whoCrashed" says that the crash took place in a standard Microsoft module, so it could also be a windows issue?! i noticed that my windows defender gets turned off once in a while and i can't turn it on manually.

    here is the latest bsod minidump:

    https://onedrive.live.com/redir?resid=FBD3C7D7FBA9DAD0%215216

    and Memory.dmp

    https://onedrive.live.com/redir?resid=FBD3C7D7FBA9DAD0%215217

    again thanks for your help

    Jan

    Wednesday, April 23, 2014 8:45 PM
  • i'll run driver verifier over night.
    Wednesday, April 23, 2014 8:46 PM
  • SYSTEM_SERVICE_EXCEPTION (3b)

    This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

    This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

    BugCheck 3B, {c0000005, fffff8003a8bd4ad, ffffd0011e032620, 0}

    0: kd> ln fffff8003a8bd4ad
    (fffff800`3a8bd490)   dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x1d   |  (fffff800`3a8bd7c0)   dxgmms1!VIDMM_GLOBAL::xWaitOnDMAReferences

    ^^ The exception occurred in  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation, as we've seen before/above.


    --------------------

    For your own person knowledge purposes, BlueScreenView is the most absolute basic software. It doesn't really tell you anything at all, other than essentially running !analyze -v does with WinDbg, and maybe even less than that.

    When a kernel component of Windows is faulted, such as a variant of the NT Kernel (such as ntoskrnl.exe), it's simply because Windows is aware kernel corruption occurred, but doesn't know what caused the corruption, so it faults the NT Kernel. Nothing more/less.

    At this point, if the next verifier enabled kernel-dump doesn't show anything other than DirectX again, this is a faulty motherboard.

    Regards,

    Patrick


    “Be kind whenever possible. It is always possible.” - Dalai Lama


    Wednesday, April 23, 2014 8:56 PM
  • So let's say that it's a faulty mobo, i still have it under warranty...what should i say that is wrong with it so they'll replace/repair it?

    regards,

    Jan

    Wednesday, April 23, 2014 9:14 PM
  • The people you'll be speaking to won't understand the actual problems from the debugging, they're just basic level 1/2 tech support in charge of processing replacements, etc. With that said, there's no need to go super in-depth.

    Simply let them know that you're having consistent DirectX Kernel faults, even after a clean install + on integrated graphics. Also notify them Memtest is clean after overnight runs, etc. Besides, if it's under warranty, they generally don't interrogate you, and as long as you're clear & polite with what the actual problem is, it'll be accepted for RMA.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Wednesday, April 23, 2014 9:55 PM
  • hi. so i let my pc running through the night, no bsod. but now, while surfing the web and watching a movie i got one. here's the minidump:

    https://onedrive.live.com/redir?resid=FBD3C7D7FBA9DAD0%215227

    regards,

    Jan

    Thursday, April 24, 2014 8:53 AM
  • WDF_VIOLATION (10D)

    This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.

    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd000`2042e3e8 fffff800`90275caa nt!KeBugCheckEx
    ffffd000`2042e3f0 fffff800`9024636f Wdf01000!FxVerifierBugCheck+0x1e
    ffffd000`2042e430 fffff800`9022625a Wdf01000!FxIoTarget::SubmitLocked+0x3e63f
    ffffd000`2042e4d0 fffff800`9020802d Wdf01000!FxIoTarget::Submit+0x3a
    ffffd000`2042e500 fffff800`92b71d7a Wdf01000!imp_WdfRequestSend+0x12d
    ffffd000`2042e560 ffffe001`46871710 netr28ux+0xd1d7a
    ffffd000`2042e568 ffffe001`469848c0 0xffffe001`46871710
    ffffd000`2042e570 ffffe001`46864c60 0xffffe001`469848c0
    ffffd000`2042e578 ffffe001`46984a60 0xffffe001`46864c60
    ffffd000`2042e580 fffff800`92ce68c0 0xffffe001`46984a60
    ffffd000`2042e588 00001ffe`b979b398 netr28ux+0x2468c0
    ffffd000`2042e590 ffffd000`2042ea6c 0x00001ffe`b979b398
    ffffd000`2042e598 fffff800`92b715af 0xffffd000`2042ea6c
    ffffd000`2042e5a0 00001ffe`b967b738 netr28ux+0xd15af
    ffffd000`2042e5a8 00001ffe`b979b398 0x00001ffe`b967b738
    ffffd000`2042e5b0 fffff800`92cead00 0x00001ffe`b979b398
    ffffd000`2042e5b8 ffffe001`46984a60 netr28ux+0x24ad00
    ffffd000`2042e5c0 ffffd000`2042ea00 0xffffe001`46984a60
    ffffd000`2042e5c8 fffff800`0002b6cc 0xffffd000`2042ea00
    ffffd000`2042e5d0 00001ffe`00000968 0xfffff800`0002b6cc
    ffffd000`2042e5d8 00001ffe`b979b300 0x00001ffe`00000968
    ffffd000`2042e5e0 fffff800`92bf0fc8 0x00001ffe`b979b300
    ffffd000`2042e5e8 fffff800`92bf1c3c netr28ux+0x150fc8
    ffffd000`2042e5f0 ffffe001`00000000 netr28ux+0x151c3c
    ffffd000`2042e5f8 00001ffe`b967b738 0xffffe001`00000000
    ffffd000`2042e600 ffffe001`46984a60 0x00001ffe`b967b738
    ffffd000`2042e608 00000000`00000000 0xffffe001`46984a60
    

    ^^ netr28ux.sys attempted to send a framework request that has already been sent to an I/O target.

    This is the Ralink RT2870 series USB802.11n Wireless Adapter driver (you may have a different manufacturer).

    Ensure yours is up to date regarding its drivers, or remove it from the equation (what I recommend) for troubleshooting purposes.

    Regards,

    Patrick


    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Thursday, April 24, 2014 6:19 PM