Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after updating Video Drivers (Crimson 16.4.1 Win7)

09 Apr 2016   #1
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 
BSOD after updating Video Drivers (Crimson 16.4.1 Win7)

Hey guys.

So I updated my video card drivers to the latest Crimson 16.4.1 (hotfix) and my system started crashing to random BSODs. First it was 0x0AE (or EA) and now it's "DRIVER_CORRUPTED_EXPOOL (c5)". Unfortunately CCleaner cleaned and removed the other BSOD so I only have 0x0C5. Here's the dump info.

Quote:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040916-14617-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19110.amd64fre.win7sp1_gdr.151230-0600
Machine Name:
Kernel base = 0xfffff800`06804000 PsLoadedModuleList = 0xfffff800`06a4b730
Debug session time: Sat Apr 9 14:44:21.431 2016 (UTC + 1:00)
System Uptime: 0 days 0:01:37.649
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {8, 2, 0, fffff800069b0b15}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+249 )

Followup: Pool_corruption
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800069b0b15, address which referenced memory

Debugging Details:
------------------


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+249
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: fffff88003999940 -- (.trap 0xfffff88003999940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80006a0c6d0
rdx=fffffa800016e350 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800069b0b15 rsp=fffff88003999ad0 rbp=0000000000000000
r8=0000000000000000 r9=fffffa800016e350 r10=0000000000000001
r11=fffffa800016e360 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!ExDeferredFreePool+0x249:
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11 ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800068771a9 to fffff80006877c00

STACK_TEXT:
fffff880`039997f8 fffff800`068771a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03999800 fffff800`06875e20 : fffffa80`0b1fcb10 fffffa80`0b36b040 fffffa80`0b273040 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03999940 fffff800`069b0b15 : 00000000`00000000 00000000`00000000 00000000`00000000 70696d57`00000000 : nt!KiPageFault+0x260
fffff880`03999ad0 fffff800`069b01b1 : 00000000`00000000 fffffa80`1082ba70 00000000`00000000 fffff800`06acf180 : nt!ExDeferredFreePool+0x249
fffff880`03999b60 fffff800`06acf5b5 : 00000000`c0000001 fffffa80`1082ba80 fffff8a0`3377444e 00000000`00000324 : nt!ExFreePoolWithTag+0x411
fffff880`03999c10 fffff800`06acf484 : fffffa80`1082ba80 00000000`00000000 fffffa80`0eaab901 00000000`00000000 : nt!WmipProcessEvent+0x101
fffff880`03999c80 fffff800`06881a69 : fffff800`06a22200 fffff800`06b71401 fffffa80`0b273000 fffffa80`0b273040 : nt!WmipEventNotification+0x38
fffff880`03999cb0 fffff800`06b10926 : 00000000`00000000 fffffa80`0b273040 00000000`00000080 fffffa80`0b1fcb10 : nt!ExpWorkerThread+0x111
fffff880`03999d40 fffff800`068690e6 : fffff880`038a4180 fffffa80`0b273040 fffff880`038af040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03999d80 00000000`00000000 : fffff880`0399a000 fffff880`03994000 fffff880`039999e0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+249
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!ExDeferredFreePool+249

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: X64_0xC5_2_nt!ExDeferredFreePool+249

BUCKET_ID: X64_0xC5_2_nt!ExDeferredFreePool+249

Followup: Pool_corruption
---------

1: kd> lmvm Pool_Corruption
start end module name
1: kd> !driver
No export driver found
1: kd> .trap 0xfffff88003999940
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80006a0c6d0
rdx=fffffa800016e350 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800069b0b15 rsp=fffff88003999ad0 rbp=0000000000000000
r8=0000000000000000 r9=fffffa800016e350 r10=0000000000000001
r11=fffffa800016e360 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!ExDeferredFreePool+0x249:
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11 ds:00000000`00000008=????????????????
I should provide notice that my system was not BSODing before I installed/updated the video drivers. I have new RAM too. (all 4 sticks are brand new) I will be having a new model motherboard on Monday installed so I'll need to do a clean-up of all the old board drivers.

System seems stable in Safe Mode with Networking. (I did the minidump stuff in SMw/Networking.

EDIT: It may also seem I have some errors when I ran chkdsk in SafeModew/ Networking.




Attached Images
BSOD after updating Video Drivers (Crimson 16.4.1 Win7)-ss-2016-04-09-03.31.35-.png 
Attached Files
File Type: zip KYLE-PC-09_04_2016_150529_84.zip (462.0 KB, 3 views)
My System SpecsSystem Spec
.
09 Apr 2016   #2
axe0

Windows 10 Pro
 
 

Hi IoNGeNeRaL,

Before we proceed, please remove all kinds of piracy from your system.
Troubleshooting a system where piracy is present may cause various of trouble, noticeable and in the background, and may make it difficult to proper troubleshoot problems. This is an important reason why with BSOD analysis most analysts won't try to analyze a dump where there is piracy present on the system.

Another important reason is that all sorts of piracy: asking for guidance with a crack, asking for a crack, discussing piracy, illegal programs present on a system when troubleshooting is going on and all other forms of piracy is against Forum Rule #4
Code:
127.0.0.1 3dns.adobe.com 3dns-1.adobe.com 3dns-2.adobe.com 3dns-3.adobe.com 3dns-4.adobe.com activate.adobe.com activate-sea.adobe.com activate-sjc0.adobe.com activate.wip.adobe.com
127.0.0.1 activate.wip1.adobe.com activate.wip2.adobe.com activate.wip3.adobe.com activate.wip4.adobe.com adobe-dns.adobe.com adobe-dns-1.adobe.com adobe-dns-2.adobe.com adobe-dns-3.adobe.com adobe-dns-4.adobe.com
127.0.0.1 adobeereg.com practivate.adobe practivate.adobe.com practivate.adobe.newoa practivate.adobe.ntp practivate.adobe.ipp ereg.adobe.com ereg.wip.adobe.com ereg.wip1.adobe.com
127.0.0.1 ereg.wip2.adobe.com ereg.wip3.adobe.com ereg.wip4.adobe.com hl2rcv.adobe.com wip.adobe.com wip1.adobe.com wip2.adobe.com wip3.adobe.com wip4.adobe.com
127.0.0.1 www.adobeereg.com wwis-dubc1-vip60.adobe.com www.wip.adobe.com www.wip1.adobe.com
127.0.0.1 www.wip2.adobe.com www.wip3.adobe.com www.wip4.adobe.com wwis-dubc1-vip60.adobe.com crl.verisign.net CRL.VERISIGN.NET ood.opsource.net
My System SpecsSystem Spec
09 Apr 2016   #3
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 

Hey Axe. Thanks for your response.

The only thing I can see in my hosts file is the following. Not sure where or which hosts file that is in.


Attached Thumbnails
BSOD after updating Video Drivers (Crimson 16.4.1 Win7)-ss-2016-04-09-09.41.07-.png  
My System SpecsSystem Spec
.

09 Apr 2016   #4
axe0

Windows 10 Pro
 
 

There is only 1 hosts file present on a system used by Windows which doesn't have an extension, when I look at your pic it shows hosts.ics, wondering if that is right.
My System SpecsSystem Spec
10 Apr 2016   #5
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {fffffa800e527610, 0, 0, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa800e527610, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------


FAULTING_THREAD:  fffffa800e527610

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88005247f63 to fffff800068c53c0

STACK_TEXT:  
fffff880`02fe02a8 fffff880`05247f63 : 00000000`000000ea fffffa80`0e527610 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fe02b0 00000000`000000ea : fffffa80`0e527610 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`05247f63
fffff880`02fe02b8 fffffa80`0e527610 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`05247e28 : 0xea
fffff880`02fe02c0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`05247e28 00000000`00000028 : 0xfffffa80`0e527610


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

Followup: MachineOwner
---------

4: kd> lmvm Unknown_Module
start             end                 module name
Piracy removed. Hosts file edited and removed adobe activation server links.

This new BSOD was today, and another graphics driver fault. My Graphics Card was fine before I tried to update it's drivers. The card itself is not faulty.


Attached Files
File Type: zip KYLE-PC-10_04_2016_141434_75.zip (419.9 KB, 1 views)
My System SpecsSystem Spec
10 Apr 2016   #6
axe0

Windows 10 Pro
 
 

This is from the BSOD from yesterday
Please replace Kaspersky with Microsoft Security Essentials while troubleshooting
Code:
fffff880`039996f8  fffff880`0469e670Unable to load image \SystemRoot\system32\DRIVERS\kneps.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kneps.sys
*** ERROR: Module load completed but symbols could not be loaded for kneps.sys
 kneps+0x22670
fffff880`03999700  fffffa80`0fce65b0
fffff880`03999708  fffff880`00c064bdUnable to load image \SystemRoot\system32\DRIVERS\kltdi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for kltdi.sys
 kltdi+0x64bd
What exactly were you doing at the time the BSOD occcured today?
My System SpecsSystem Spec
10 Apr 2016   #7
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 

I'd rather not replace my KIS with MSE as I still have 253 days of my license left. (Yes, I bought a year license ) I was listening to this on YouTube:

Whenever I seem to watch something on YouTube or stream something my graphics drivers go into an infinite loop for some reason. my display goes blank, reappears, goes blank, and so on. Then it crashes to the BSOD.

EDIT: And MSE doesn't protect my system well enough like KIS does. I've had issues with MSE letting some infectious diseases in whereas KIS and MBAM stop them in their tracks.

EDIT#2: I just tried to launch GTA V and it crashed. (the game)


Attached Files
File Type: zip gta_crash.zip (2.6 KB, 3 views)
My System SpecsSystem Spec
10 Apr 2016   #8
axe0

Windows 10 Pro
 
 

Replacing Kaspersky with MSE is only temporary while troubleshooting, not trying this would make troubleshooting only difficult.

Regarding your display issues, please try following
Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to ONLY install the drivers using custom/advanced options.
BSOD after updating Video Drivers (Crimson 16.4.1 Win7)-ss-2015-12-13-01.09.13-.png


My System SpecsSystem Spec
10 Apr 2016   #9
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 

It just crashed again as I was downloading the new display drivers and trying to sfc /scannow.


Attached Files
File Type: zip KYLE-PC-10_04_2016_151802_68.zip (420.1 KB, 1 views)
My System SpecsSystem Spec
10 Apr 2016   #10
IoNGeNeRaL

Windows 10 Pro x64 (UPGRADED - 10/20/2016)
 
 

For some reason I can't uninstall KIS. I get this error.


Attached Thumbnails
BSOD after updating Video Drivers (Crimson 16.4.1 Win7)-ss-2016-04-10-03.45.23-.png  
My System SpecsSystem Spec
Reply

 BSOD after updating Video Drivers (Crimson 16.4.1 Win7)




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Getting BSOD after updating GPU drivers
Hi experts, I was working on video project, I got a notification about new GPU drivers so i updated it, after that im getting this Blue screen error frequently like 3-4 times a day, I have attached all files needed in a zip below please help me with this, Just help me to find wat is the real...
BSOD Help and Support
BSOD after updating video card
Hi there, I have again another bsod after an update. During my last session, I installed: the latest Nvidia Geforce GT 630 M drivers; Tomb Raider Videogame. The BSOD happened after about 10 minutes I opened the video game: I had a complete freeze so I had to force the shutdown. After that, this...
BSOD Help and Support
BSOD for the first time after updating the drivers
Hello I have Asus K56C crushed for the first time after updating my driver using " Driver Genius"; I want to know if this is a driver problem or a physical one. I have uploaded the dump file thank you :)
BSOD Help and Support
ATI Radeon HD 4350 not updating drivers on Win7 Ult 64
I'm stumped. I have an ATI Radeon HD 4350. Currently I am using the WDDM 1.1 drivers that came with my Win7 Ultimate 64-bit install (store-bought). It's been working fine for normal use, but the drivers are 2 years out of date and no games want to work on my system. I tried installing the...
Graphic Cards
New BSOD after updating drivers
Running fresh install of 7 x64 ultimate. Was having lots of BSOD. Was told they were driver issues. Updated drivers and computer was running fine. Shut down computer for a couple hours and when I turned it back on I got another BSOD. Can someone please debug this dump and let me know what caused...
BSOD Help and Support
Need help with Updating /Drivers/BSOD!
Hello All. So I am working with Toshiba Satellite A205-S5855. It is about 2 years old. Originally I purchased this laptop with the OS Vista on it. Had several issues with it over the past two years that included getting two hard drives and a mother board replaced under warranty. This warranty...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:30.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App