Bluescreen errors started happening even though I haven't updated anything

hensie

Honorable
May 15, 2012
21
0
10,510
I haven't changed any hardware/driver, I've been using this system for 1,5 years now without any problems. And 2 days ago I had a BSOD, I've had it 3 times since then, every time during using Chrome. Funny thing is I played some games for hours before that and nothing happened, so it doesn't necessarily happen during stressful situations.

I've tried to update my GPU drivers but it didn't fix it cause I had a BSOD yesterday after I had updated as well.

On saturday for example I didn't have BSOD even though I used the PC for about 10 hours, even gaming.

These are the error logs I have:

012014-7956-01.dmp 2014.01.20. 22:24:19 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`00146373 fffff880`08075070 00000000`00000000 dxgmms1.sys dxgmms1.sys+c095 x64 ntoskrnl.exe+6f840 C:\Windows\Minidump\012014-7956-01.dmp 4 15 7600 275 480 2014.01.20. 22:25:36

011714-68375-01.dmp 2014.01.17. 15:34:04 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`00156373 fffff880`07ca7070 00000000`00000000 atikmdag.sys atikmdag.sys+7cd0b x64 ntoskrnl.exe+6f840 C:\Windows\Minidump\011714-68375-01.dmp 4 15 7600 275 480 2014.01.17. 15:36:10

012114-7768-01.dmp 2014.01.21. 0:54:37 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff900`c4620310 00000000`00000000 fffff960`003625ad 00000000`00000000 dxgkrnl.sys dxgkrnl.sys+6487c x64 ntoskrnl.exe+6f840 C:\Windows\Minidump\012114-7768-01.dmp 4 15 7600 275 480 2014.01.21. 10:14:38

Could it be a hardware problem? Like GPU is failing or something?
Cause I find it hard to believe that it's a driver problem, cause I haven't installed anything new so why would it start happening now?

System specs:

AMD Phenom X4 955 3.2 GHz
AMD Sapphire 6870 1GB
8 GB ram
Windows 64bit OS
Asus m5a87 mobo
FSP 600W PSU


 

hensie

Honorable
May 15, 2012
21
0
10,510
I've already done that. I updated to the latest AMD driver from the same link you gave me, and I still had a BSOD after that. However I didn't have BSOD today yet.
But that was the same yesterday it only happened after like 10 hours, weird.
 
Memory corruption by a device driver will have different BSOD with each boot. Windows attempts to load the modules in a different section of memory on each boot to make it harder on viruses to hack in. Basically, a device driver that corrupts memory will corrupt the memory of the device driver next to it. That driver then fails. Most drivers do not check for corruption but some of microsofts drivers do and they call a bugcheck to stop the system so the problem can not be ignored.

you may also find that conflicts in audio drivers can cause this problem. Video cards that support HDMI or display port will have a high def audio driver, this driver might have conflicts with other audio drivers on your system (web cam, sound card, video card, mother board sound drivers)
you might want to go to control panel, hardware devices, device manager and find your sound sources and disable all of the ones you are not using and see if your issue goes away. for example I only have speakers connected to my mother board and wireless bluetooth via USB. I turn off the sound in my graphics driver, and web cam. I pulled my extra sound card because of other problems.

Note: don't un install or plug and play will just reinstall the driver again for you. (disable the device in device manager)
 

hensie

Honorable
May 15, 2012
21
0
10,510
Thanks, I've disabled them , will see if I still experience BSOD's , it's kinda hard to tell cause it doesn't happen often.
So most likely it's not a hardware related problem but a driver issue?
 
it can still be hardware, often you will find that the corruption is cause by certain kinds of memory transfers.
best way to eliminate drivers is to boot memtest86 on a CD and run the memory tests. If it comes up clean, you swap you memory modules and run it again. if it is still ok you start looking at the device drivers.

if the test fail you update the BIOS and try to fix memory settings and re run. Or try another set of memory.