Blue Screen of Death after a while playing

Toggle sidebar Toggle sidebar
P

Phelipe Andrade

Reputable
Nov 14, 2014
7
0
4,510
My Specs:
Windows 7 x64
16GB 4x4 1600Mhz (Corsair, dual channel)
Video Card Asus 5870 1GB GDDR5
MotherBoard Asus M5A97 AM3+
FX-8150 Black Edition
HD Sata 3 Samsung
- My drivers are all up-to-date
- My motherboard BIOS is up-to-date
- The problem isn't my HD, cause when the blue screen appears i can't hear any different noise then the usual
- I've tested to raise my video card fan (worried if the cause come from overheat) and nothing changed
- I've just formatted my windows
I was thinking that the reason could be the Memory, something related to the dual channel, cause when i bought them, it was 1 pack with 3 (the same serie number) and another separated, or the problem could be my PCI-E slot, i'll try to change the video card slot but i'd like some help before doing something useless...

Thanks!
 
Solution
Vic 40
You could up the voltage on the ram to 1.55V (max. up to 1.65V) and see if still gives problems.
You could test the ram with prime95@blend or memtest86+.
You could give "whocrashed" a shot to see if this gives some usefull info about the bluescreens,
http://www.resplendence.com/downloads
you'll find it under "Crash Analysis Tools".

You could look with cpu-z->spd tab,if the ram sticks have different specs,give the info here or do the next to see if this gives the same info,

Download hwinfo32,
http://www.hwinfo.com/download32.html
open it,click run,close the top window which is the system summary,click save report at the left top,in the next window at the bottom check=dot "short text report" after that next,you'll get to see what is in...
Sort by date Sort by votes
Vic 40

Vic 40

Titan
Ambassador
Oct 22, 2013
20,885
994
87,990
You could up the voltage on the ram to 1.55V (max. up to 1.65V) and see if still gives problems.
You could test the ram with prime95@blend or memtest86+.
You could give "whocrashed" a shot to see if this gives some usefull info about the bluescreens,
http://www.resplendence.com/downloads
you'll find it under "Crash Analysis Tools".

You could look with cpu-z->spd tab,if the ram sticks have different specs,give the info here or do the next to see if this gives the same info,

Download hwinfo32,
http://www.hwinfo.com/download32.html
open it,click run,close the top window which is the system summary,click save report at the left top,in the next window at the bottom check=dot "short text report" after that next,you'll get to see what is in your pc,copy that by clicking "copy to clipboard" and right click and paste in you next post.
 
Upvote 0 Downvote
Solution
P

Phelipe Andrade

Reputable
Nov 14, 2014
7
0
4,510
CPU: AMD FX-8150 (Zambezi, OR-B2 (Orochi))
3600 MHz (18.00x200.0) @ 1404 MHz (7.00x200.7)
Motherboard: ASUS M5A97
Chipset: AMD 970 (RX980) + SB920/SB950
Memory: 16384 MBytes @ 802 MHz, 9.0-9-9-24
- 4096 MB PC12800 DDR3 SDRAM - Corsair CMZ12GX3M3A1600C9
- 4096 MB PC12800 DDR3 SDRAM - Corsair CMZ4GX3M1A1600C9
- 4096 MB PC12800 DDR3 SDRAM - Corsair CMZ12GX3M3A1600C9
- 4096 MB PC12800 DDR3 SDRAM - Corsair CMZ12GX3M3A1600C9
Graphics: ASUS EAH5870
ATI/AMD Radeon HD 5870, 1024 MB GDDR5 SDRAM
Drive: Hitachi HDS721075KLA330, 732.6 GB, Serial ATA 3Gb/s
Drive: WDC WD10EZEX-00RKKA0, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: HL-DT-ST DVD-RAM GH15L, DVD+R DL
Sound: ATI/AMD SB800/Hudson-1 - High Definition Audio Controller
Sound: ATI/AMD Cypress - High Definition Audio Controller
Network: RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC
OS: Microsoft Windows 7 Ultimate (x64) Build 7600

Whocrashed gave me this... i was guessing the problem was related to memory dump but "whocrashed" said it was my processor clock or something like that.. i'm gonna try to raise the voltages and see what happens


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 14/11/2014 23:39:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111414-18189-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003115180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 14/11/2014 23:39:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003115180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 14/11/2014 22:25:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111414-16598-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D76C8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 
Upvote 0 Downvote
Vic 40

Vic 40

Titan
Ambassador
Oct 22, 2013
20,885
994
87,990
Spec wise should the ram be compatibel,let's see if the higher voltage will run better and how the tests go.
Maybe also see if you have the latest bios.If you open hwinfo again and don't close the system summary can you,at the left side bottom quarter,see which bios the motherboard has.
 
Upvote 0 Downvote
Vic 40

Vic 40

Titan
Ambassador
Oct 22, 2013
20,885
994
87,990
You could try that.

Try to find the next under the "AI Tweaker" in the bios "Cpu/northbridge voltage" set this to manual and go up a notch which should be about 0.00625,maybe even two notches.
See if this helps as well if upping the dram voltage isn't enough.
 
Upvote 0 Downvote
P

Phelipe Andrade

Reputable
Nov 14, 2014
7
0
4,510
And it happened again, but now i did some tests and my conclusion is that the reason why it's happening is related with my video card voltage or overheating, cause when i started a game and monitoring FPS and temperature, i've noticed that my OS crashes when my video card temperature pass the 70 C. When i'd set the fan to work at 50%, the temperature took more time to get at that number, but it crashed anyway.... Is there a reason why this is happening? because 70C isn't a high working temperature of video cards...

PS.: I did exactly what you've said (raising the north bridge voltage) and it crashed anyway =(
 
Upvote 0 Downvote
Vic 40

Vic 40

Titan
Ambassador
Oct 22, 2013
20,885
994
87,990
I don't often do this,but can you do this,

You can open hwinfo32,after that open the sensor window by marking sensors=V,after that click run,,then click at the bottom "Logging start" ,after that choose a name and place for the log.like Hwinfolog at your desktop.Leave it open and do game/stresstest or whatever you do until a crash.The log will end at that point but will be saved.
After the restart upload the log to a site without to much crap (!),for instance dropbox,and leave a link to it here.You could also look at the log yourself with either excel or libre office calc.

It's an old card so maybe it can't handle the heat that good anymore.You could look at replacing the cooling paste and cleaning the cooler.
 
Upvote 0 Downvote
J

jaohjor

Distinguished
Mar 21, 2009
3
0
18,510
Download the 13.9 driver from here then use AMD Uninstall Utility to remove all traces of your current driver, CCC etc. Reboot and install the 13.9 driver. NOTE: When installing choose 'Advanced' or 'Custom' (whichever option is available, just not Express) and uncheck everything except the video driver.

(original: http://www.sevenforums.com/bsod-help-support/336910-bsod-random-situations-caused-atikmdag-sys.html)

WORKED FOR ME !!!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom