Windows 10: Bsod system thread exception not handled

Discus and support Bsod system thread exception not handled in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, since updating with the Windows 10 Anniversary Update, on Aug 3rd. I have had 8 BSOD occurrences Each giving the same Stop Code: THREAD EXCEPTION... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by billt4g, Aug 8, 2016.

  1. billt4g Win User

    Bsod system thread exception not handled


    Hi, since updating with the Windows 10 Anniversary Update, on Aug 3rd. I have had 8 BSOD occurrences Each giving the same
    Stop Code: THREAD EXCEPTION NOT HANDLED also What failed? partmgr.sys.
    Each time I had to power off and restart.
    I looked up this driver in the Driver Reference Table which says this is;
    Partition Management Driver - Windows Update

    I ran your debug download which created the following file:Attachment 95143

    Can you help me?
    ps. (Did my attachment work?)

    :)
     
    billt4g, Aug 8, 2016
    #1

  2. BSOD System Thread Exception Not Handled - SPUVCbv64.sys

    We are volunteers willing to help you try to resolve this issue. I am a 10 time and dual award MVP specializing in Windows troubleshooting including BSOD events.

    Both minidumps were essentially the same and I fully analyzed them to be sure other processes were not implicated.

    Since the computer is new and still under warranty please contact HP Support and the seller. As OEM HP is responsible for the proper operation of both the hardware and Windows. So regardless of the cause it is theirs to resolve. And the unit is under full warranty
    and may be in need of repairs or replacement. Added that even if you are able to resolve the issue you would want it fully documented just in case there are related problems down the road. Remember the more you do the more they will say it is something you
    have done.

    BugCheck 1000007E, {ffffffffc0000005, fffff807e4f6ad53, ffffef862b01f768, ffffef862b01efb0}

    Probably caused by : SPUVCbv64.sys ( SPUVCbv64+6ad53 )

    SPUVCbv64.sys dated 10/30/2017 AVStream driver SUNPLUS INNOVATION TECHNOLOGY.

    BiosVersion = F.36

    BiosReleaseDate = 10/25/2017

    SystemManufacturer = HP

    SystemProductName = HP Spectre x360 Convertible 13-ac0XX

    SystemFamily = 103C_5335KV HP Spectre

    SystemVersion =

    SystemSKU = 2EN69EA#ABZ

    BaseBoardManufacturer = HP

    BaseBoardProduct = 827E

    BaseBoardVersion = 94.61

    CPUID: "Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz"

    MaxSpeed: 2500

    CurrentSpeed: 2712

    HP Support/Troubleshooting & Drivers

    HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

    Contact HP

    http://welcome.hp.com/country/us/en/contact_us....

    HP Forums

    Home - HP Support Forum

    Please let us know the results and if you need further assistance.
     
    SpiritX MS MVP, Aug 8, 2016
    #2
  3. enrijerry Win User
    BSOD System Thread Exception Not Handled - SPUVCbv64.sys

    On a 2 months old hp laptop (hp spectre x360 with kaby lake intel proc.) I had 2 BSOD in the last day shortly after
    waking the laptop from sleep while using the
    windows hello feature.

    I have updated recently the pc to windows 10 pro (from home) and I have activated the hyper-v and Bitlocker features (but i think the problem is unrelated to these things).

    The hp camera driver was also udpate recently (SunplusIT 27/10/2017 ver. 3.6.8.7). Maybe I should revert back to an older version?

    Minidump file and system info here Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

    I would appreciate any suggestion.

    I will be grateful for any help any community member can provide.

    Enri
     
    enrijerry, Aug 8, 2016
    #3
  4. Ztruker Win User

    Bsod system thread exception not handled

    The zip file you uploaded is empty. Please try again.
     
    Ztruker, Aug 9, 2016
    #4
  5. billt4g Win User
    Ran the debug download again. however this is also an empty .zip file!!

    so what does that say?
    So can you still advise me with out it? What is with this "partmgr.sys" file/driver?
    Should I go back to 1511, only a couple of days left.
     
    billt4g, Aug 9, 2016
    #5
  6. billt4g Win User
    It happen'd again last night, this time the .zip file is not empty. I this any better?

    Attachment 95436

    By the way, I have noticed that this BSOD seems to only happen when I plug my Kindle to charge. (USB 2 port)

     
    billt4g, Aug 10, 2016
    #6
  7. Ztruker Win User
    Latest dump indicates a problems with gwdrv.sys:
    Code: BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for gwdrv.sys *** ERROR: Module load completed but symbols could not be loaded for gwdrv.sys[/quote] This belongs to GlassWire. GlassWire is a free network monitor & security tool with a built in firewall.
    I suggest you uninstall it and see if that resolves the problem.

    Dump also mentioned memory_corruption which could be due to defective RAM or driver problems.

    Prevous dump has the following:
    Code: ffffb680`e0335a88 fffff80f`fe31a943Unable to load image \SystemRoot\System32\drivers\USBSTOR.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for USBSTOR.SYS *** ERROR: Module load completed but symbols could not be loaded for USBSTOR.SYS USBSTOR+0xa943[/quote] This belongs to USB Mass Storage Driver.

    Code: ffffb680`e03345c8 fffff800`00000000Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64[/quote] This belongs to Realtek RT640. See if you can find a newer driver, this one is dated Tue May 05 12:21:03 2015.

    It would also be a very good idea for you to test your PC memory:
    ===================================================
    RAM:


    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums


    Bsod system thread exception not handled [​IMG]
    Information

    Bsod system thread exception not handled [​IMG]


    MemTest86+
    is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.


    Bsod system thread exception not handled [​IMG]
    Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.


    Bsod system thread exception not handled [​IMG]
    Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
     
    Ztruker, Aug 10, 2016
    #7
  8. billt4g Win User

    Bsod system thread exception not handled

    Hi, thanks for your post,
    I have uninstalled the GlassWire site (not needed).
    Don't know what to do about the USB Mass Storage Driver.
    Device Manger says the Realtek RT640 is current one.

    I need help with the MemTest86:
    I downloaded the, installed and put to USB stick the MemTest86+ USB installer
    My problem is with Step 11;


    "With your USB stick inserted, boot into BIOS. Select Boot options and select the bootable USB stick you created. When you exit the BIOS after saving your changes your PC will boot into MemTest86+ and it will start running automatically, you do not have to do anything after selecting the boot device and exiting the BIOS."

    This is not clear (forgive my inexperience) could you please explain Step by Step. (because when I booted into BIOS the options were not clear..)
    Please explain.


    "

     
    billt4g, Aug 11, 2016
    #8
  9. Ztruker Win User
    You have a Dell. Leave the BIOS alone.
    Insaert the USB flash drive then boot.
    Press F12 to bring up the Boot Options menu and select the flash drive to boot from.
     
    Ztruker, Aug 12, 2016
    #9
  10. billt4g Win User
    Hi, it just happen'd again working ok all day, then I plugged in my Kindle to charge via USB 2.0 port an Bam BSOD - same message, same driver "partmgr.sys". restarted the machine with kindle still plugged in, and we're off and running, go no problem. See new .zip file below. I'm going to try the MemTest+ tonight, see what happens

    .Attachment 95965
     
    billt4g, Aug 12, 2016
    #10
  11. Ztruker Win User
    Latest dump shows 4 different problems:

    Code: BugCheck 1000007E, {ffffffffc0000005, fffff80ea32f191d, ffffb18095afb478, ffffb18095afaca0} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption[/quote] Code: ffffb180`95afa4d8 fffff80e`a3b9e646*** WARNING: Unable to verify timestamp for tcpip.sys *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys tcpip+0x3e646[/quote] Code: ffffb180`95afba88 fffff80e`a55aa943Unable to load image \SystemRoot\System32\drivers\USBSTOR.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for USBSTOR.SYS *** ERROR: Module load completed but symbols could not be loaded for USBSTOR.SYS USBSTOR+0xa943[/quote] Code: ffffb180`95afa468 fffff80e`a2e91c09Unable to load image \SystemRoot\system32\drivers\Wdf01000.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Wdf01000.sys *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys Wdf01000+0x11c09[/quote] Make sure you run memtest86+ for a minimum of 8 passes. Any error then stop as that means you have defective ram.

    A similar problem here: Windows 7 BSOD with USB connections - Tech Support Forum
     
    Ztruker, Apr 5, 2018
    #11
Thema:

Bsod system thread exception not handled

Loading...
  1. Bsod system thread exception not handled - Similar Threads - Bsod system thread

  2. BSOD - SYSTEM THREAD EXCEPTION NOT HANDLED

    in Windows 10 BSOD Crashes and Debugging
    BSOD - SYSTEM THREAD EXCEPTION NOT HANDLED: Hello, I was on google chrome with many tabs and application open when my computer gave me a BSOD.I went and updated the graphics driver and the network drivers through device manager. It said I had the best installed one. I looked at the event logger to try and find the...
  3. BSOD - SYSTEM THREAD EXCEPTION NOT HANDLED

    in Windows 10 Gaming
    BSOD - SYSTEM THREAD EXCEPTION NOT HANDLED: Hello, I was on google chrome with many tabs and application open when my computer gave me a BSOD.I went and updated the graphics driver and the network drivers through device manager. It said I had the best installed one. I looked at the event logger to try and find the...
  4. BSOD - SYSTEM THREAD EXCEPTION NOT HANDLED

    in Windows 10 Software and Apps
    BSOD - SYSTEM THREAD EXCEPTION NOT HANDLED: Hello, I was on google chrome with many tabs and application open when my computer gave me a BSOD.I went and updated the graphics driver and the network drivers through device manager. It said I had the best installed one. I looked at the event logger to try and find the...
  5. BSOD system exception thread not handled

    in Windows 10 BSOD Crashes and Debugging
    BSOD system exception thread not handled: HELP! Every time my laptop powers on it BSOD and shows the error code 'system exception thread not handled'. It will then auto-restart and work fine after this. Any ideas on how I can fix this initial boot issue would be great!...
  6. System Thread Exception Not Handled BSOD

    in Windows 10 BSOD Crashes and Debugging
    System Thread Exception Not Handled BSOD: Recently I've been getting the BSOD with the message "your PC ran into a problem and needs to restart" and stopcode: SYSTEM THREAD EXCEPTION NOT HANDLED. At first this happened maybe once a week, but it has gotten more and more frequent. Links to the dmp files:...
  7. BSOD system thread exception not handled

    in Windows 10 BSOD Crashes and Debugging
    BSOD system thread exception not handled: My PC just had a BSOD. While following instructions from another post and running verifier my PC was stuck in a crash loop. Booted up after system restore kicked in, good thing I didn't skip the restore point step. I uploaded a .rar with 3 files: the MSinfo32, the older DMP...
  8. BSOD system thread exception not handled

    in Windows 10 BSOD Crashes and Debugging
    BSOD system thread exception not handled: Hello :) I recently god this BSOD in an endless loop: STOP CODE: system thread exception not handled win ver: 2004 19041.572 I attach the V2 log as requested. Hopefully you can help me solve this issue. thank you so much! DESKTOP-HOLLOWC-(2020-12-11_20-19-28).zip 170250
  9. BSOD System thread exception not handled.

    in Windows 10 BSOD Crashes and Debugging
    BSOD System thread exception not handled.: Hello everyone! I'm here with an issue, that came up yesterday afternoon. There was a windows update, PC restarted, and I left it sitting idle for a while, like 40 minutes or so. After I came back, it was sitting on the wimdows restore screen, telling me it failed to...
  10. BSOD System thread exception not handled

    in Windows 10 BSOD Crashes and Debugging
    BSOD System thread exception not handled: So, a few weeks ago I had a problem with daily blue screens. That problem got fixed since it was a driver that was the problem. Just now, I had another blue screen but this time it was a differant problem. I looked in the events but unfortantly I cannot see what the problem...