Before we begin, I ask you do the following:
1. If any of your hardware is overclocked,
PLEASE reset it to stock settings / optimized defaults whilst trying to diagnose BSOD related issues. You're absolutely more than welcome to re-overclock your hardware after we've gone through your issues.
2. If you have RAID, please update its driver. If you're unsure of how to do this or where to download the drivers, please don't hesitate to ask and I will do my best to point you in the right direction.
I have taken a look at your dump, and here's what I've found:
First off, the first bugcheck code is SYSTEM_SERVICE_EXCEPTION (3b). Nine times out of ten this is at the fault of video card drivers, so that's what we're going to do first.
Uninstall your video card drivers and then update your video card drivers to the latest version:
STAY AWAY FROM BETA DRIVERS WHILE DIAGNOSING BSOD RELATED ISSUES!IntelAMDnVidia
Drivers in need of update (do note that although drivers listed may not be the cause of your related issues, it is always best to have up to date drivers):
Quote:
secdrv.SYS - secdrv fffff880`06e9f000 fffff880`06eaa000 Wed Sep 13 09:18:38 2006 (4508052e) 00010b40
(Can be updated via Windows Upate)
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff80003493cfe, Address of the instruction which caused the bugcheck
Arg3: fffff880090c2c60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
FAULTING_IP:
nt!EtwpPsProvTraceImage+2e
fffff800`03493cfe 450fb7d1 movzx r10d,r9w
CONTEXT: fffff880090c2c60 -- (.cxr 0xfffff880090c2c60)
rax=fffff880090c3718 rbx=0000000000000000 rcx=fffffa8007638658
rdx=000000000000128c rsi=000000000000128c rdi=fffffa8007638658
rip=fffff80003493cfe rsp=fffff880090c3640 rbp=fffff80003287d00
r8=fffff880090c3958 r9=0000000000001401 r10=fffffa8003d96d40
r11=fffffa8003ef0f78 r12=fffffa8007638658 r13=fffff880090c3958
r14=000000000000128c r15=fffffa8007638658
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!EtwpPsProvTraceImage+0x2e:
fffff800`03493cfe 450fb7d1 movzx r10d,r9w
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: kldw.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003493cfe
STACK_TEXT:
fffff880`090c3640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!EtwpPsProvTraceImage+0x2e
FOLLOWUP_IP:
nt!EtwpPsProvTraceImage+2e
fffff800`03493cfe 450fb7d1 movzx r10d,r9w
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!EtwpPsProvTraceImage+2e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
STACK_COMMAND: .cxr 0xfffff880090c2c60 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!EtwpPsProvTraceImage+2e
BUCKET_ID: X64_0x3B_nt!EtwpPsProvTraceImage+2e
Followup: MachineOwner
The second bugcheck code was ATTEMPTED_WRITE_TO_READONLY_MEMORY, which again, nine times out of ten is related to a device driver (update your drivers), a service or incompatible firmware. However, it could be RAM as well.
As I've said earlier, let's try uninstalling the video card drivers and then reinstalling the latest version.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff900c0081000, Virtual address for the attempted write.
Arg2: 0e6000009932f021, PTE contents.
Arg3: fffff880099f2490, (reserved)
Arg4: 000000000000000b, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880099f2490 -- (.trap 0xfffff880099f2490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00ffffff00000000 rbx=0000000000000000 rcx=fffff900c0081000
rdx=00000000021538e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000154b34 rsp=fffff880099f2628 rbp=fffff880099f2920
r8=0000000000000008 r9=0000000000000001 r10=fffffa80060af8b0
r11=fffff900c0081000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k+0xc4b34:
fffff960`00154b34 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000302b5d2 to fffff8000307fc40
STACK_TEXT:
fffff880`099f2328 fffff800`0302b5d2 : 00000000`000000be fffff900`c0081000 0e600000`9932f021 fffff880`099f2490 : nt!KeBugCheckEx
fffff880`099f2330 fffff800`0307dd6e : 00000000`00000001 fffff900`c0081000 00000000`00000100 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x45c6e
fffff880`099f2490 fffff960`00154b34 : fffff960`0011b155 fffff880`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`099f2628 fffff960`0011b155 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k+0xc4b34
fffff880`099f2630 fffff880`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k+0x8b155
fffff880`099f2638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+c4b34
fffff960`00154b34 ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k+c4b34
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f10ff25
FAILURE_BUCKET_ID: X64_0xBE_win32k+c4b34
BUCKET_ID: X64_0xBE_win32k+c4b34
Followup: MachineOwner
Edited by pjBSOD - 2/16/12 at 3:10pm
