New
#1
BSOD after full wipe fresh install
Ok quick backstory, my comp is custom built I started having bsods frequently. Ran memtest 2 errors. I had a feeling (because of going through 6 mem stick initially) it was the mobo not the ram. Replaced the mobo, passed memtest today no errors. I did a full wipe and reinstall everything re formatted when I installed the mobo. I only mention this to take bad memory out of the equation.
So since I installed win 7 yesterday I've noticed an odd occurrence after about a half hour of not doing anything my display will switch from Aero to basic theme, then my monitor will go blank (like a screen saver) once i goes black i hit my space bar and move my mouse, and there is windows again. Now I double checked my power savings it is set at 4 hours for both and I don't have a screen saver enabled. So while i was watching TV my monitor went blank, I ignored it, an hour later I couldnt get my comp to respond, I reset it, windows loaded saying it wasnt shut down properly and I get a message that windows BSOD'd (now it never bsod'd it black screen of deathed in a way lol). I installed windbg and got the following info.
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88004961817, Address of the instruction which caused the bugcheck
Arg3: fffff88003b368e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
atikmdag+90817
fffff880`04961817 8b4820 mov ecx,dword ptr [rax+20h]
CONTEXT: fffff88003b368e0 -- (.cxr 0xfffff88003b368e0)
rax=0000000000000000 rbx=fffffa8007817130 rcx=fffffa8006a282e0
rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8006a44340
rip=fffff88004961817 rsp=fffff88003b372c0 rbp=fffffa8006a282e0
r8=0000000000000015 r9=fffff88004d23970 r10=fffffa8006a44290
r11=fffff88003b37410 r12=0000000000000000 r13=fffffa8007576340
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0x90817:
fffff880`04961817 8b4820 mov ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88004961817
STACK_TEXT:
fffff880`03b372c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x90817
FOLLOWUP_IP:
atikmdag+90817
fffff880`04961817 8b4820 mov ecx,dword ptr [rax+20h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+90817
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cef1f94
STACK_COMMAND: .cxr 0xfffff88003b368e0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_atikmdag+90817
BUCKET_ID: X64_0x3B_atikmdag+90817
Followup: MachineOwner
now dwm malfunctioning could explain the change from aero to basic, and ati is definitely my video card driver. Whats odd though is usually with the screen going black I would be getting the "video card has stopped responding" message and I never have. I have the latest drive from ATI which is in a way a beta. Do you think something in the driver could be causing the switch from aero to basic to a mini shut down every half hour. It just seems odd. Any help would be appreciated.
Quote