Page 1 of 2 12 LastLast
  1.    26 Nov 2016 #1


    Hi, i'm having a really frustrating time with a BSOD that states USB_BUGCODE ERROR this frequently happens during the day and has caused my computer to crash at incredibly inconvenient times. I have tried to view the minidump files for this exact error to find the cause but for some strange reason my computer will under no circumstance create a minidump for this BSOD. Every other BSOD creates one but not this one so i'm pretty lost. All of my drivers are updated to their most recent driver and I am just completely stumped as this point as I have no clue what to do from here. Any and all help is appreciated.
    Last edited by Nick9195; 26 Nov 2016 at 21:45.
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 6,592
    Windows 10 Pro X64 1809 17763.134
       26 Nov 2016 #2

    The zip file you uploaded is empty. Can you try again following the instructions.
      My ComputersSystem Spec

  3.    26 Nov 2016 #3

    I'm not quite sure why it didn't work the first time. I re uploaded the file. Sorry for the inconvenience.
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 6,592
    Windows 10 Pro X64 1809 17763.134
       27 Nov 2016 #4

    Better, thanks.

    The first thing I noticed is you are way down level on updates. You are at 10586.672. which was well over a year ago. You should be at 14393.447. There were a lot of fixes between the two releases.

    Please apply all Windows Updates until you are current. Then if still problems, run DM_Log_collector and upload the new zip please.
      My ComputersSystem Spec

  5.    01 Dec 2016 #5

    I updated Windows and did as you said. Everything seemed to working fine for a few days, but then out of nowhere, I got another bluescreen. Once again, I went to check for a minidump and there was none. I have a minidump related to a completely different bluescreen but not this one, very irritating. If it makes any difference, my computer crashed while rapidly pressing the W key but i'm not sure if that means anything considering it crashes even when i'm not at the computer at all sometimes. I've included another file with the minidump I received a few days ago as it may have something to do with my USB crashing. I'm just not sure at this point.
      My ComputerSystem Spec

  6. Ztruker's Avatar
    Posts : 6,592
    Windows 10 Pro X64 1809 17763.134
       02 Dec 2016 #6

    The last dump from 11/30 indicates a problem with your Nvidia card or driver.
    BugCheck 116, {ffffd88ecb6cd120, fffff8083e6a739c, ffffffffc000009a, 4}
    *** 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+95739c )
    You have version 372 date 9/15/2016. The Nvidia web site has version 376.09 dated 2016.11.28

    Remove and install latest Nvidia drivers:

    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

    Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    See if that gets rid of the problem. have driver version 372.90 dated 9/15/2016. The Nvidia website had version 376.09 dated 2016.11.28. Try this one as follows:
      My ComputersSystem Spec

  7.    03 Dec 2016 #7

    I had recently ordered an SSD so I just decided to do a fresh install of windows. So far everything is working fine, I will see how everything goes for a few days and report back as solved if everything is working alright. Thank you for your help.
      My ComputerSystem Spec

  8. Ztruker's Avatar
    Posts : 6,592
    Windows 10 Pro X64 1809 17763.134
       03 Dec 2016 #8

    You're welcome, good luck.
      My ComputersSystem Spec

  9.    04 Dec 2016 #9

    Alright so, after reinstalling windows, the USB_BUG_CODE BSOD's stopped. But after that I constantly received other crashes without a BSOD, just a freezing screen with no error message. I took your advice earlier and I updated my GPU drivers to their latest. Everything seemed to work fine for a while but then out of nowhere today i'm getting NMI_HARDWARE_FAILURE. I've chkdsk'ed all of my hard drives and they're functional, checked my ram and there's no errors, and this NMI error will not give me a minidump so I have no way of knowing what the cause is. The only thing that I can think of at this point is either my GPU or CPU but i'm not exactly sure how i'd even check for that. I'm including 3 BSODS I got earlier for completely unrelated errors as they might help out somewhat.
    Last edited by Nick9195; 04 Dec 2016 at 18:18.
      My ComputerSystem Spec

  10. Ztruker's Avatar
    Posts : 6,592
    Windows 10 Pro X64 1809 17763.134
       04 Dec 2016 #10

    BugCheck 50, {fffff80200000018, 0, fffff80ffeb323bb, 2}
    *** WARNING: Unable to verify timestamp for cpuz136_x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for cpuz136_x64.sys
    Could not read faulting driver name
    Probably caused by : cpuz136_x64.sys ( cpuz136_x64+23bb
    CPUZ is a diagnostic tool that you installed. You can try uninstalling it.

    Try stressing your CPU and GPU as follows:

    Follow this tutorial to stress test your CPU:
    Prime95 - Stress Test Your CPU - Windows 10 Forums

    Follow this tutorials to stress test your GPU:
    FurMark - GPU Stress Test - Windows 10 Forums

    If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

    Additionally you can try running with Driver Verifier enabled after running the above tests, not at the same time:

    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    and make sure the correct boxes are checked.

    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My ComputersSystem Spec

Page 1 of 2 12 LastLast

Related Threads
Hello, Recently upgraded to Windows 10 when free upgrade was offered. Actually I seem to remember being notified that time was running out and my old setup would no longer be supported. After finding PC in BSOD state, I found out my hp model was...
Hello, so i think i have dealt with this bluescreen 3times now, and it seemed to have gone away after i went from my amd system to intel. But now its there again. The most useful function ever, wake from sleep, is now bluescreening my computer. I...
Solved Random BSOD error Page Error in Non Paged Area in BSOD Crashes and Debugging
Hi, I have started getiing random BSOD atlaest 5-7 times today on my laptop. It just says Page File error in non paged area evrytime. The laptop is fairly new and used very mildly. Please guide what to do.
Hi, i got this computer about 3~ Weeks ago, and have gotten random BSOD's after that. System Information Bellow Intel Core i5-6600K 3.5Ghz @ 3.5 GeForce GTX960 2gb GDDR5, Physx CUDA 1TB Harddisk 7200RPM 8Gb DDR4 2133Mhz Dual Channel, 2x4gb...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:12.
Find Us