Sign in with
Sign up | Sign in
Your question

The Curious Case of Benjamin BSOD

Last response: in Windows 7
Share
January 23, 2013 11:53:07 AM

Hi All,

I wonder if I can get some opinions on something.

I have a system that has been experiencing BSOD pretty much since day 1 (May 2011). They are random, sometimes I go weeks without experiencing one, other times they are almost daily.

I don't want to bias any opinions, so I'm going to give some basic facts and can you give me your opinion on what the cause is:

Firstly, spec of the PC:

Motherboard:
ASUS M4A79XTD EVO
(Note: Drivers are up to Date - BIOS Version 2102)

Chipset:
AMD 790X (RD780) + SB750 Chipset

CPU:
AMD Phenom II X6 1090T (Socket AM3) @ 3200 Mhz

Memory:
Total 16 GB Made up of 4 x Cosair 4GB DDR3 SDRAM
Memory Speed: 800 Mhz (PC3-12800)

GPU:
AMD (ATI) Radeon HD 5870 (CYPRESS XT)
PCIe v2.0 x16 (5.0 Gb/s) @ x16 (5.0 Gb/s)
1024 MB GDDR5 SDRAM @ 256-bit
GPU Clock Speed: 400 Mhz
Memory Speed: 1200 Mhz

(Note: Drivers updated on 21-Jan to v13.1. Previously at v11.2. )

OS:
Windows 7 Home Premium 64-bit



Secondly a quick summary of the BSOD crashes experienced (using BSOD View):

23/01/2013 11:36
DRIVER_IRQL_NOT_LESS_OR_EQUAL
atikmdag.sys

21/01/2013 09:53
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
ntoskrnl.exe

20/01/2013 14:40
SYSTEM_SERVICE_EXCEPTION
No Cause Listed

14/01/2013 18:43
KMODE_EXCEPTION_NOT_HANDLED
No Cause Listed

10/01/2013 19:09
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
No Cause Listed

05/01/2013 15:47
MEMORY_MANAGEMENT
No Cause Listed

05/01/2013 15:13
PAGE_FAULT_IN_NONPAGED_AREA
ntoskrnl.exe

04/01/2013 11:23
NTFS_FILE_SYSTEM
Ntfs.sys

31/12/2012 10:38
IRQL_NOT_LESS_OR_EQUAL
No Cause Listed

15/12/2012 12:08
KMODE_EXCEPTION_NOT_HANDLED

13/10/2012 14:11
CACHE_MANAGER

02/06/2012 23:38
NTFS_FILE_SYSTEM
Ntfs.sys

02/06/2012 23:32
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
rdyboost.sys

10/05/2012 18:35
MEMORY_MANAGEMENT
ntoskrnl.exe

09/05/2012 10:18
NTFS_FILE_SYSTEM
amdppm.sys


Any ideas?

a b $ Windows 7
January 23, 2013 11:55:39 AM

did you run memtest for your ram sticks?
January 23, 2013 1:31:59 PM

I've run the Windows Memory Diagnostic tool - no issues found.

Should I run memTest86 to be sure?
Related resources
a b $ Windows 7
January 23, 2013 1:40:50 PM

yes download the iso and boot from the cd just to make sure. if no errors found your ram is not the issue
a b $ Windows 7
January 23, 2013 1:45:40 PM

Ouch you know what not being funny here just a thought since you say it has done it since day one of the build. I would have a close check of the gold pins on the under side of the Cpu pw2374, it looks like a pin maybe slightly bent, or worse broke off ect. By most of the reports it has something to do with the CPU.
The other exception to do with the ATI card drivers Has to do with an Irq conflict.
Each device is assigned its own IRQ number to talk directly to the Cpu. if it failing it can be a conflict with other hardware, or sign the Cpu is at fault. All and everything has to go through the Cpu in the list so if you think a bit logic here check the Cpu out for bent pins ect then do a re-seat of it see if it helps. You may want to look into the PSU aswell it can also be the cause of things you are listing if it is fluctuating in power and not steady.It can cause problems with ram ect when fluctuating causing errors. You never listed its brand and wattage. so if you can do so it may help so we can see if it is the culprit also pw2374. That is my two cents worth if it helps you in any way with some insight to the problem.
January 23, 2013 2:06:59 PM

Looks like your issues are all over.

The multiple memory failures can be cause by another issue, particularly the last one.

The atikmdag.sys is indicative of an ATI driver that ceased functioning. If it persists replace the driver and avoid installing catalyst.

ntoskrnl.exe: NT OS kernel failure. Your OS kernel may be corrupt or missing. This is the most likely fix I can find: http://support.microsoft.com/?kbid=314477

Ntfs.sys: this is your NT File System : http://www.computerhope.com/issues/ch001206.htm

rdyboost.sys :This is a bios setting that restarts your system automatically after a BSOD. You can disable it in BIOS. If it keeps causing random restarts after look here: http://windows7forums.com/windows-7-support/32312-windo...

amdppm.sys: seems to be a stack over write/ minidump issue. It could be malware causing a minidump as part of an exploit. Might want to run Driver Verifier to see what the actual bad boy is for this. I have also see Avast cause this. This is probably what is causing your memory BSODs

Here is a older BSOD listing if it keeps up: http://www.carrona.org/bsodindx.html#0x0000000A

Good luck!

a b $ Windows 7
January 23, 2013 2:14:21 PM

All good advice on things to ponder over
It may help you I hope it does pw2374.
May you have good luck in resolving the problems.
Good show Groundrat ones to think of looking at aswell.
And Alvine. :) 
January 23, 2013 2:21:58 PM

Memory is my bet. I'd try memtest86+ and if that doesn't find problems, start swapping out modules while trying to replicate the crash.

There are way too many different BSODs here for it to be related to pretty much anything else. There are also too many "causes" for them to make it seem plausible that those drivers are actually at fault. As Groundrat suggested, you could try Driver Verifier but I believe it's not going to be of much value if the "bugs" it finds are due to memory corruption.

DRIVER_IRQL_NOT_LESS_OR_EQUAL / IRQL_NOT_LESS_OR_EQUAL - Accessing paged memory from above APC_LEVEL. Could happen if the pointer is stored in a faulty memory area.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED / KMODE_EXCEPTION_NOT_HANDLED / SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - Unhandled exceptions. Probably generated from code regions that the developers did not expect to throw them. Memory corruption is a likely reason for this too.

MEMORY_MANAGEMENT / CACHE_MANAGER - Both indicate critical failures of memory management. Cache manager integrates tightly with memory manager, so I'm not surprised it failed as well.

PAGE_FAULT_IN_NONPAGED_AREA - Access to invalid memory again. Also likely result of memory corruption.

NTFS_FILE_SYSTEM - Not quite sure on this one but it's plausible that it suffered an internal failure due to memory corruption.

January 27, 2013 2:47:48 PM

Hey all,

Thanks for the posts. All good food for thought.

The PC has been stable for about 4 days now... it's really weird how it goes through patches of stability and instability.

I ran a memTest86 for 4 hours, it returned saying no errors found.

The CPU is interesting one.. will look into that.

Cheers

Paul
!