Been having random BSODS for a couple weeks now, usually happens when I have a video playing, already did a complete reinstall of windows, running windows 7 home premium 64 bit, I have attached a SF file.
Last edited by jordonws; 16 Jul 2014 at 21:47. Reason: Fixing attachments
Hi jordonws.
The BSODs are caused by the display driver. A complete uninstall of the display driver and then a clean install may help.
Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install the display driver again.
Plus, out of personal curiosity, I want to know something from you, if you dont mind. Yours a R9 280X. I want to know how hot the GPU runs. The reason behind the curiosity is this thread: BSOD shuts down PC
Let us know how the computer is running after performing the clean install of the display driver.
__________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8800f4d42ec, fffff88009008950, 0} Probably caused by : atikmdag.sys ( atikmdag+b12ec ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8800f4d42ec, Address of the instruction which caused the bugcheck Arg3: fffff88009008950, 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+b12ec fffff880`0f4d42ec 488b02 mov rax,qword ptr [rdx] CONTEXT: fffff88009008950 -- (.cxr 0xfffff88009008950;r) rax=fffff8800f64f620 rbx=0000000000000000 rcx=fffffa800cee3028 rdx=0000000000000000 rsi=fffff8800900994c rdi=fffff8800f64eff0 rip=fffff8800f4d42ec rsp=fffff88009009330 rbp=fffff88009009461 r8=000000000e76621f r9=0000000000000001 r10=0000000000000008 r11=0000000000000000 r12=fffffa800fcdb900 r13=0000000000000051 r14=0000000000000000 r15=fffffa8008f39240 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210286 atikmdag+0xb12ec: fffff880`0f4d42ec 488b02 mov rax,qword ptr [rdx] ds:002b:00000000`00000000=???????????????? Last set context: rax=fffff8800f64f620 rbx=0000000000000000 rcx=fffffa800cee3028 rdx=0000000000000000 rsi=fffff8800900994c rdi=fffff8800f64eff0 rip=fffff8800f4d42ec rsp=fffff88009009330 rbp=fffff88009009461 r8=000000000e76621f r9=0000000000000001 r10=0000000000000008 r11=0000000000000000 r12=fffffa800fcdb900 r13=0000000000000051 r14=0000000000000000 r15=fffffa8008f39240 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210286 atikmdag+0xb12ec: fffff880`0f4d42ec 488b02 mov rax,qword ptr [rdx] ds:002b:00000000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: iexplore.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800f4d42ec STACK_TEXT: fffff880`09009330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0xb12ec FOLLOWUP_IP: atikmdag+b12ec fffff880`0f4d42ec 488b02 mov rax,qword ptr [rdx] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+b12ec FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 53bd610a STACK_COMMAND: .cxr 0xfffff88009008950 ; kb FAILURE_BUCKET_ID: X64_0x3B_atikmdag+b12ec BUCKET_ID: X64_0x3B_atikmdag+b12ec ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x3b_atikmdag+b12ec FAILURE_ID_HASH: {953e808a-0919-1ac0-1e92-05cd8644bf08} Followup: MachineOwner --------- 3: kd> lmvm atikmdag start end module name fffff880`0f423000 fffff880`103cc000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Wed Jul 09 21:04:34 2014 (53BD610A) CheckSum: 00F46306 ImageSize: 00FA9000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Just finished reinstalling, will wait to see if I get another BSOD, to answer your temp question, I run around 41 C at idle and max ive seen was 71 when stress testing.
Was playing Borderlands 2 and computer BSOD again
If you report about a BSOD, Post it following the Blue Screen of Death (BSOD) Posting Instructions.
Add the data in your next post.
Sorry here is the updated info and logs.
Display issue continues, even with another version of the display driver.
Stress test the Graphics Card using Furmark.Code:BugCheck 116, {fffffa800f03e010, fffff8800488fdac, 0, 2} Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+bdac ) Followup: MachineOwner ---------
Video Card - Stress Test with Furmark
Let us know the result. Also, let us know the wattage of your PSU.
Computer crashed as soon as I hit burn in test, tried twice, psu is 875 w
The temperature is very normal.
Power Supply is enough sufficient.
Still display is crashing, irrespective of driver version. So it gives a hint that the GPU might be failing itself.
Now, you are trying to perform a burn test, and the computer crashes instantly. It makes it sure that the GPU is failing to take any load.
You need to change the GPU, unfortunately. If it is within warranty, RMA it and ask for a replacement. Use onboard graphics in the mean time.
Quote