BSOD crash when connecting Kindle, error involves partmanager.sys


  1. Posts : 3
    Windows 10 64-bit
       #1

    BSOD crash when connecting Kindle, error involves partmanager.sys


    I've had a Kindle paperwhite for a few years no and never had an issue with connecting it via USB. However, after the recent Windows 10 updates, my computer BSOD's and force restarts almost as soon as I plug my Kindle in. Other storage devices I've tried (phone and PSVita) haven't had the same problem.

    The error message on BSOD states "system thread exception not handled" and refers to partmanager.sys

    I have include the DM log zip file.

    Thanks in advance for any help.

    I have also run a program called WhoCrashed, which provided this information:

    System Information (local)

    Computer name: HEATHLAPTOP
    Windows version: Windows 10 , 10.0, build: 14393
    Windows dir: C:\WINDOWS
    Hardware: K73SV, ASUSTeK Computer Inc.
    CPU: GenuineIntel Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 6350340096 bytes total




    Crash Dump Analysis


    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.

    On Mon 15-Aug-16 3:21:02 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\081516-30890-01.dmp
    This was probably caused by the following module: partmgr.sys (partmgr+0x191D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80AB716191D, 0xFFFFDD00D3D0D478, 0xFFFFDD00D3D0CCA0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\partmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Partition driver
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Mon 15-Aug-16 3:21:02 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: partmgr.sys (partmgr+0x191D)
    Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80AB716191D, 0xFFFFDD00D3D0D478, 0xFFFFDD00D3D0CCA0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    file path: C:\WINDOWS\system32\drivers\partmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Partition driver
    Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Mon 15-Aug-16 3:05:45 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\081516-37765-01.dmp
    This was probably caused by the following module: partmgr.sys (partmgr+0x191D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80E96A3191D, 0xFFFF9F81F0D94478, 0xFFFF9F81F0D93CA0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\partmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Partition driver
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Mon 15-Aug-16 2:58:40 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\081516-39203-01.dmp
    This was probably caused by the following module: partmgr.sys (partmgr+0x191D)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803E07B191D, 0xFFFFC181EA13B478, 0xFFFFC181EA13ACA0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\WINDOWS\system32\drivers\partmgr.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Partition driver
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
      My Computer


  2. Posts : 14,904
    Windows 10 Pro
       #2

    Please remove all pirated programs and such from your system before we can start troubleshooting.
    The Forum Rules is meant for everything regarding piracy
    • Discussing it,
    • Asking for guidance,
    • Asking for a crack,
    • The use of it,
    • Etc.

    4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).
      My Computers


  3. Posts : 3
    Windows 10 64-bit
    Thread Starter
       #3

    Not a problem. Are you able to tell me exactly which programs I'll need to remove?
      My Computer


  4. Posts : 14,904
    Windows 10 Pro
       #4

    Aren't you? :)
      My Computers


  5. Posts : 3
    Windows 10 64-bit
    Thread Starter
       #5

    I'll be honest, this laptops well old and I don't remember a few things. I know Office and Photoshop are the two main offenders, but is there anything else?
      My Computer


  6. Posts : 14,904
    Windows 10 Pro
       #6

    is there anything else?
    That would be something you need to check, many illegal activations are done through exploits which we cannot find easily.
      My Computers


 

  Related Discussions
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 22:32.
Find Us




Windows 10 Forums