• Hey there, Guest! Share your idea for a new trophy in the forums and win bragging rights and a $100 Amazon gift card! Check out the New Community Trophy Contest here!
  • Pardon our dust as we work on some regularly scheduled forum maintenance. You may notice some missing features during this time. Thank you for your patience!

DRIVER_CORRUPTED_EXPOOL blue screen haunts me

Da Rossa

Reputable
Dec 17, 2015
29
0
4,530
0
Hi, I have been experiencing the above BSOD error as well as with others, such as PAGE FAULT IN NONPAGED AREA. The reason I put both in the same topic is because of the time coincidence. Since some time ago, it has been happening regularly, but not always the same message.

Typically happens when I'm playing Starcraft II, but I have a feeling that it's unrelated to the game. Also, 90% of the time I was voice chatting with someone. Sometimes playing mp3 in the background. A split second before the BSOD occurs, I hear a “broken record”, horrible glitch sound, like an old Atari or Sega Master System with a loose-contact cartridge. When the blue screen kicks in, the glitch sound will continue indefinitely.

When it happened the 2nd time, I formatted my PC and reinstalled Windows, only to find out I wasted my time.

The minidump details are these:

Dump File = 090617-9234-01.dmp
Crash Time = 06/09/2017 00:28:11
Bug Check String = DRIVER_CORRUPTED_EXPOOL
Bug Check Code = 0x000000c5
Parameter 1 = 00000000`00000000
Parameter 2 = 00000000`00000002
Parameter 3 = 00000000`00000000
Parameter 4 = fffff802`46f14a75
Caused By Driver = ntoskrnl.exe
Caused By Address = ntoskrnl.exe+16c560
File Description = NT Kernel & System
Product Name = Microsoft® Windows® Operating System
Company = Microsoft Corporation
File Version = 10.0.15063.540 (WinBuild.160101.0800)
Processor = x64
Crash Address = ntoskrnl.exe+16c560
Stack Address 1 = (blank)
Stack Address 1 = (blank)
Stack Address 1 = (blank)
Computer Name = (blank)
Full Path = C:\WINDOWS\Minidump\090617-9234-01.dmp
Processor Count = 4
Major Version = 15
Minor Version = 15063
Dump File Size = 550.532
Dump File Time = 06/09/2017 00:29:42


My Setup:
Processor: Intel Core i5 3450 @3.1GHz
MoBo: Gigabyte Z77M-D3H
Memory: 8192MB DDR3 Corsair 1333MHz
VGA: Saphire ATI Radeon HD 7770 1024MB 128 bits @1920x1080
SSD: Kingston SUV400S372240G 240GB
Hard Drive 2: Seagate ST3500413AS 465 GB 7200RPM
Hard Drive 3: Seagate ST3750330AS 698 GB 7200RPM
Hard Drive 4: Western Digital WD20EARX 1863GB IntelliPower
Hard Drive 5: Western Digital WD20EZRX 1863GB IntelliPower
Power Supply: Corsair VX450
OS: Windows 10 Home
Monitor: Samsung T270B350 @1920x1080


I don't mean to advance suggestions but for some reason I have a feeling it's about the motherboard audio driver. Upon installing, I'll always see three audio devices on the device manager:


    * AMD High Definition Audio Device
    * High Definition Audio Device (with the yellow alert sign)
    * VIA HD Audio


The first and the third are OK, but the second has this status:


This device could not be started (Code 10)
{Operation failed}
Requested operation did not succeed.



I went to Gigabyte's site to download the latest audio driver for Gigabyte Z77M-D3H. Installed, rebooted Windows, then I see that on the device manager again.

Now, there is no telling when the BSOD will happen again. However, I do hear the glitch sound here and there sometimes during music or video playback, like it *was* going to enter in blue screen, but the glitch sound doesn't take more than half a second and it passes.

Please, help me :(

Edit: can this by power related?
 

Da Rossa

Reputable
Dec 17, 2015
29
0
4,530
0




Thanks 21, but sorry, this doesn't look to be the issue. Anyway I did what you instructed. The BSOD did not happen, but the glitch sound did. I tested with the two RAM sticks individually. At some point, the glitch sound went off for 0.25 seconds, but audible. Which means the problem persists :(
 

Da Rossa

Reputable
Dec 17, 2015
29
0
4,530
0
Turns out my two RAM sticks were installed in a way that it would not benefit from the dual channel configuration. I relocated one of them, and curiously the problem did not happen again. Thanks ComputerGeek21!