New
#1
BSOD while watching YouTube video, 0x0000000A
I've been having random BSODs recently. I suspect it's my Radeon video card, but I'm not particularly adept in memory dump diagnosing. Can someone tell me if my hunch is valid? Thanks!
I've been having random BSODs recently. I suspect it's my Radeon video card, but I'm not particularly adept in memory dump diagnosing. Can someone tell me if my hunch is valid? Thanks!
Hi Strahan.
Uninstall the installed display driver using Display Driver Uninstaller. Then install the CCC 14.4 WHQL only.
Let us know for any further BSOD after doing it.
________________________________________
Code:BugCheck A, {0, 2, 0, fffff80002cdaa22} Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f ) Followup: MachineOwner --------- 5: 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: 0000000000000000, 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: fffff80002cdaa22, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f10100 GetUlongFromAddress: unable to read from fffff80002f101c0 0000000000000000 Nonpaged pool CURRENT_IRQL: 2 FAULTING_IP: nt!KiSignalSynchronizationObject+42 fffff800`02cdaa22 488b3f mov rdi,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre TRAP_FRAME: fffff880022e9a00 -- (.trap 0xfffff880022e9a00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffff88003288180 rdx=fffffa800e70a260 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002cdaa22 rsp=fffff880022e9b90 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=fffff80002c61000 r11=fffff880022e9c20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!KiSignalSynchronizationObject+0x42: fffff800`02cdaa22 488b3f mov rdi,qword ptr [rdi] ds:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002cd2fe9 to fffff80002cd3a40 STACK_TEXT: fffff880`022e98b8 fffff800`02cd2fe9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`022e98c0 fffff800`02cd1c60 : fffff880`022e99f8 00000000`00000001 00000000`00000000 fffffa80`0e70a268 : nt!KiBugCheckDispatch+0x69 fffff880`022e9a00 fffff800`02cdaa22 : fffffa80`0e70a1f0 fffff800`02cda9e3 00000000`00000010 00000000`00200246 : nt!KiPageFault+0x260 fffff880`022e9b90 fffff800`02cd8dd6 : 00000000`00000000 fffff880`04a0b1d8 00000000`00000000 fffffa80`0bb90410 : nt!KiSignalSynchronizationObject+0x42 fffff880`022e9be0 fffff880`04a1b47f : fffffa80`00000000 00000000`00000000 fffffa80`0e85d900 fffff880`022e9ca0 : nt!KeSetEvent+0x106 fffff880`022e9c50 fffff880`04a392e9 : fffffa80`00000000 fffffa80`0bb90410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x5f fffff880`022e9ca0 fffff880`04a38574 : fffff880`0328d040 fffffa80`0ea638b0 00000000`00000000 fffffa80`0bb90410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39 fffff880`022e9cd0 fffff880`04a38012 : 00000000`00000000 fffffa80`0ea638b0 00000000`00000080 fffffa80`0bb90410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`022e9d00 fffff800`02f6daba : 00000000`04111779 fffffa80`0c000b50 fffffa80`09d61040 fffffa80`0c000b50 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`022e9d40 fffff800`02cc5426 : fffff880`03288180 fffffa80`0c000b50 fffff880`032930c0 fffff880`015aa975 : nt!PspSystemThreadStartup+0x5a fffff880`022e9d80 00000000`00000000 : fffff880`022ea000 fffff880`022e4000 fffff880`022e9400 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidMmiProcessTerminationCommand+5f fffff880`04a1b47f 33d2 xor edx,edx SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: dxgmms1!VidMmiProcessTerminationCommand+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc13 IMAGE_VERSION: 6.1.7601.18126 FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xa_dxgmms1!vidmmiprocessterminationcommand+5f FAILURE_ID_HASH: {24a5b05f-0da8-ee02-b6e4-43c87a433b59} Followup: MachineOwner ---------
Thanks a lot! I'll give that a whirl.