Solved BSOD frequently occurring after Windows update, WIN7_DRIVER_FAULT

[ellecdwt]

Hello,

I had been having bsod issues for awhile last year and had gotten help on here and the problem had gone away. Before this recent string of bsods I had only had one in April and none for several months before that. I had a Windows update on the 3rd and didn't notice anything different, but beginning yesterday I began having a slew of bsods. They happened both in high graphic games, browsing the internet, and even just when sitting there. This last one happened when windows was just starting up, I think. I used DriverMax to update all of my drivers, and I even tried doing a restore point from before the update on the 3rd and that seemed to lower the frequency, but then I started getting them again. Any help is much appreciated. I'm attaching the mini dump and the requested zip file.

 

[Arc]

If you think that your earlier issue was solved, mark http://www.sevenforums.com/bsod-help-support/276584-bsods-keep-happening-during-d3-other-games.html as solved and continue here.

Uninstall Virtual Clone Drive.

PNP Device ID    ROOT\SCSIADAPTER\0000

Such a thing may cause this type of BSOD.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh
5. Apply > OK
6. Accept then restart.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If memtest comes to be free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_______________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff80081b0bf58, 2, 0, fffff800032d1238}

Probably caused by : win32k.sys ( win32k!NtUserPeekMessage+a7 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80081b0bf58, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032d1238, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003503100
GetUlongFromAddress: unable to read from fffff800035031c0
 fffff80081b0bf58 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeferredReadyThread+338
fffff800`032d1238 498b9cea40dc2a00 mov     rbx,qword ptr [r10+rbp*8+2ADC40h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  sidebar.exe

TRAP_FRAME:  fffff8800d69a6d0 -- (.trap 0xfffff8800d69a6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800d69a898
rdx=0000000000004e10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032d1238 rsp=fffff8800d69a860 rbp=000000000fcc1063
 r8=0000000000000020  r9=fffffa80095e6850 r10=fffff80003256000
r11=0000000002c9f920 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KiDeferredReadyThread+0x338:
fffff800`032d1238 498b9cea40dc2a00 mov     rbx,qword ptr [r10+rbp*8+2ADC40h] ds:fffff800`81b0bf58=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032cb1a9 to fffff800032cbc00

STACK_TEXT:  
fffff880`0d69a588 fffff800`032cb1a9 : 00000000`0000000a fffff800`81b0bf58 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d69a590 fffff800`032c9e20 : 00000000`00000000 00000000`00000000 fffff960`0031f200 fffff880`009b3104 : nt!KiBugCheckDispatch+0x69
fffff880`0d69a6d0 fffff800`032d1238 : fffff880`0d69a940 fffffa80`0d743c58 00000000`00000001 fffff960`000b6e0e : nt!KiPageFault+0x260
fffff880`0d69a860 fffff800`032ab7a7 : fffff880`009b3180 fffff880`009b310d 00000000`00000001 00000000`00000000 : nt!KiDeferredReadyThread+0x338
fffff880`0d69a8e0 fffff800`032c122f : fffffa80`095e680d fffff880`009b3180 00000000`00000000 00000000`00000000 : nt!KeSetEventBoostPriority+0x137
fffff880`0d69a950 fffff800`032d4aaa : 00000000`02c9f920 00000000`00000001 00000000`00000001 00000000`00000000 : nt!ExpReleaseResourceForThreadLite+0x2bf
fffff880`0d69a9b0 fffff960`00134a77 : 00000000`00000000 00000000`00000000 00000000`00000289 00000000`00000001 : nt!ExReleaseResourceAndLeavePriorityRegion+0x12
fffff880`0d69a9e0 fffff800`032cae93 : fffffa80`0d743b50 00000000`02c9f8b8 fffff880`0d69aa88 00000000`00000000 : win32k!NtUserPeekMessage+0xa7
fffff880`0d69aa70 00000000`778d908a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02c9f898 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778d908a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!NtUserPeekMessage+a7
fffff960`00134a77 8bc3            mov     eax,ebx

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  win32k!NtUserPeekMessage+a7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dccb

FAILURE_BUCKET_ID:  X64_0xA_win32k!NtUserPeekMessage+a7

BUCKET_ID:  X64_0xA_win32k!NtUserPeekMessage+a7

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

 

[ellecdwt]

Okay, I uninstalled VCD and I removed the start ups as well. Just had another crash. Here is the minidump and .zip. I will run memtest, but am wanting to wait until tonight, if possible.

 

[Arc]

OK, enable Driver Verifier now?

 

[ellecdwt]

Okay, I will do that now. Any idea why I can no longer access sevenforums from my computer?
I am using my phone for it now, which is kind of a pain.

 

[ellecdwt]

Okay I ran it and when I restarted it went right to a blue screen. It's now repairing and doing a system restore. I will post the dump and .zip
When I can get back on it.

 

[ellecdwt]

Because I can't access your website from my computer anymore for some reason, I'm trying to attach the dump from my phone, but it doesn't seem to be working. Please let me know how to regain access to your site on my pc and I will attach the .dmp. thanks

 

[ellecdwt]

Fixed. It was daemon tools causing the bsod. No blue screens since I uninstalled it. Thanks for the help, driver verifier helped me pinpoint it.

 

[Arc]

Good to know the issue is fixed.