New
#11
I did run the tests with Furmark and Memtest86+. I ran a brief test with Prime95, but I haven't had a chance yet to run for a full 12 hours. I got the OS directly from Microsoft; its a personal license.
BSOD w/ AMD 890FX Chipset
-
-
New #12
As in, you got an ISO file from Technet/MSDN (or similar)? If so, did you use DVD or USB to install it?
-
New #13
No, I got a DVD directly from Microsoft.
-
New #14
Ok. Let us know how the hardware tests go.
-
New #15
I ran the FFT test in Prime95 for roughly 10 hours and got no failures. An interesting thing has happened though. I reinstalled the OS again, but have not run Windows update or installed any of the hardware drivers (save the chipset RAID driver and the graphics driver), and I'm not longer able to reproduce the BSOD. I can boot up fine with driver verifier enabled, and I have gone 24 hours without a BSOD during use (which is, sadly, unprecedented).
-
New #16
Ok. This time - install the critical Windows updates manually one-by-one (or in groups of about 3). Reboot after each and see if you get BSODs. If you do get BSODs - make sure you know exactly what update caused it.
Then - if you get it fully updated without problems install any other necessary drivers one by one too.
-
New #17
I installed several of the chipset drivers, and got a BSOD during boot with driver verifier enabled. After uninstalling one of the drivers, I was able to boot up properly with driver verifier enabled. However, I still got a BSOD during normal use. When I tried reinstalling win 7, I got a BSOD during the install (twice, in fact). I reran Prime95, and this time I did get a failure during the Blend test (all the results text file stated was that it was a fatal error due to rounding inaccuracy). Is the CPU to blame for this? Or could the motherboard/RAM/powersupply also be the cause?
-
-
New #19
I've attached the BSOD report. Usbfilter.sys is the driver I had to disable to get my system to boot with driver verifier enabled. The second BSOD listed occurred when I had driver verifier enabled and was able to boot properly.
-
New #20
The short answer to your question is yes, it could be any of the causes you mentioned. Remove all of your RAM but one stick and see how your system runs. The only way I know to test a power supply is to borrow a known good power supply and try it. That fact that you got error running Prime indicates a definitely hardware problem.
Your Driver Verifier enabled dump pints to a Direct X driver as likely not the real cause. I have found that when Direct X is blamed, it can be the video card, the network adapter, or even the sound card as well as hardware problems like RAM or CPU.
Windows 7 is finicky about RAID arrays. I have seen RAID cause all sorts of irritating problems.
Before you do anything drastic, let's look at out of date drivers and update them. In general, third party drivers should be dated July 13, 2009 or later to be up to date for Win 7.
amdsbs.sys Fri Mar 20 14:36:03 2009 - AMD Technology AHCI Compatible Controller Driver for Windows family is a driver file from AMD Technologies Inc. belonging to AMD Technology AHCI Compatible Controller.
ahcix64s.sys Wed Jul 01 03:05:27 2009 - AMD AHCI driver
Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver for Realtek 8101E/8168/8169 PCI/PCIe Adapters
Quote
Related Discussions