Windows 10: [BSOD] DRIVER_CORRUPTED_EXPOOL in Windows 10 Pro

Page 2 of 2 FirstFirst 12
  1.    22 Jan 2016 #11

    axe0 said: View Post
    Upload a new zip so I can check it please.
    I'm really sorry that I couldn't reply . Was a bit busy so almost forgot to update the latest zip until I faced 2 other BSOD's.

    Below is the updated zip ;-

    Attachment 60114
      My ComputerSystem Spec


  2. Posts : 11,546
    Windows 10 Pro
       22 Jan 2016 #12




    [BSOD] DRIVER_CORRUPTED_EXPOOL in Windows 10 Pro Diagnostic Test [BSOD] DRIVER_CORRUPTED_EXPOOL in Windows 10 Pro
     DRIVER VERIFIER

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My ComputersSystem Spec

  3.    22 Jan 2016 #13

    axe0 said: View Post


    [BSOD] DRIVER_CORRUPTED_EXPOOL in Windows 10 Pro Diagnostic Test [BSOD] DRIVER_CORRUPTED_EXPOOL in Windows 10 Pro
     DRIVER VERIFIER

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

    Ok. I'll run the driver verifier and report back..

    Meanwhile can you please tell if you were able to get any idea from the logs/minidmps as to what was the reason behind those BSOD's ?
      My ComputerSystem Spec


  4. Posts : 11,546
    Windows 10 Pro
       22 Jan 2016 #14

    Unfortunately I can't, either because some functionality are not documented or because I can't find the documentation.

    While going again through the dumps I noticed the Intel Management Engine driver being flagged.
    Please disable driver verifier, update the Intel ME driver and see if it improves system stability.
    • Open an admin command prompt
    • Enter "verifier/reset" (without quotes)

    Driver Reference Table - TeeDriverW8x64.sys
    Code:
    0: kd> !irp ffffe0018eff25a0
    Irp is active with 3 stacks 2 is current (= 0xffffe0018eff26b8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 ffffe0018dfe8aa0 00000000 fffff8029dd24d88-ffffe001964ce430 Success Error Cancel pending
    	      Unable to load image \SystemRoot\System32\drivers\TeeDriverW8x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for TeeDriverW8x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for TeeDriverW8x64.sys
     \Driver\MEIx64	nt!PopRequestCompletion
    			Args: 00015500 00000001 00000004 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe001964ce430    
    			Args: 00000000 00000000 00000000 00000000
    
    
    0: kd> lmvm teedriverw8x64
    start             end                 module name
    fffff800`f94a0000 fffff800`f94d0000   TeeDriverW8x64 T (no symbols)           
        Loaded symbol image file: TeeDriverW8x64.sys
        Image path: \SystemRoot\System32\drivers\TeeDriverW8x64.sys
        Image name: TeeDriverW8x64.sys
        Timestamp:        Tue Jul 07 19:43:32 2015 (559C0FC4)
        CheckSum:         000327ED
        ImageSize:        00030000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My ComputersSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
BSOD driver_corrupted_expool in BSOD Crashes and Debugging
The computer is only 3 days old. I had started to close a program and it asked if I wanted to save before I quit, I clicked no and received the error. File attached. Thanks
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...
Windows 10 has been stable for me, but recently saw BSOD with driver_corrupted_expool error. Any assistance would be much appreciated. 45676
I recently upgraded my htpc from 8.1 pro to Win 10 pro. I have had multiple BSOD since then. 4 were for store exception not handled and the last 2 were for kmode exception not handled mv91xx.sys. Please advise.
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 10:03.
Find Us