Repeated BSOD's Last 3 Days

[goosegas]

Hi All-

I think I have attached all the requested files for review, and maybe even a few extra. Forgive me if I sent too much, but I have posted many places and it has been a bit confusing to remember exactly who asked for what. In addition to the 5 embedded screenshots, I have attached a diagnostic zipfile.

2 days ago, I went to my computer which was running all night and turned on the monitor. There was a BSOD on the screen. I pulled the following information from the event viewer log.

- System

- Provider


[ Name] Microsoft-Windows-Kernel-Power


[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}



EventID 41


Version 2


Level 1


Task 63


Opcode 0


Keywords 0x8000000000000002

- TimeCreated


[ SystemTime] 2011-03-15T06:30:49.484017400Z



EventRecordID 15758


Correlation

- Execution


[ ProcessID] 4


[ ThreadID] 8



Channel System


Computer Rick-PC

- Security


[ UserID] S-1-5-18

- EventData

BugcheckCode 0

BugcheckParameter1 0x0

BugcheckParameter2 0x0

BugcheckParameter3 0x0

BugcheckParameter4 0x0

SleepInProgress false

PowerButtonTimestamp 0



I also received about 4 or 5 more BSOD's in the 2 days following, with the same codes as the first.

The only common factor here is that 2 of these BSOD's were when my son was playing Runescape. That is certainly not a very demanding game, so I opened up Left for Dead 2, and played for a full hour on all the highest settings without any problems. None of the 4 temperature settings moved above 38 degrees, including the GPU, so overheating sure doesn't seem to be the problem.

I ran virus scans, spyware scans, registry scans, and didn't come up with anything.

I don't have automatic updates set for anything, as I like to not have these things come on while gaming. I do regularly do all the windows updates and I did update my GPU driver. I don't see any change either way after doing that.

My computer specs are as follows:

· Cooler Master HAF 912 Gaming Case
· Corsair 750TX 750W 80 Plus Certified PSU
· AMD Phenom ll X4 925 Quad Core Processor w/Hyper Transport
· ADATA 1600MHz 8 GB DDR3 Dual Channel Memory
· Gigabyte GA-870-UD3 Motherboard
· Asetek 510LC Liquid Cooling System w/120MM Radiator & Fan
· 1 TB SATA-lll 6.0 GB/s 64MB Cache 7200RPM HDD
· Windows 7 Home Premium 64 Bit OS
· NVIDIA GeForce GTX 460 SE 1GB GDDR5 16X PCIe Video Card
· AeroCool 2000 LCD Fan Controller
· Samsung Syncmaster 2433BW 24” 1920 x 1200 LCD Monitor
· APC XS 1300 Battery Backup

This computer is only 3 months old and I have not done any overclocking of any kind, or changed any settings that might be contributing to this problem.

Any help would be greatly appreciated!!!!

 

[Jonathan_King]

Hello,

I've closed the TSF thread: BSOD's for 3 Days - Tech Support Forum
Please do not post in multiple places, as it becomes difficult to manage.

Here is our first problem:

Event[232]:
  Log Name: System
  Source: Microsoft-Windows-Subsys-SMSS
  Date: 2011-03-15T00:32:43.946
  Event ID: 12
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Rick-PC
  Description: 
The crash dump file could not be created due to a lack of free space on the destination drive. Increasing the amount of free space on the destination drive may help prevent this error.

You have 731GB free on your C drive, which is where the crash dumps should be saved. On your E drive, however, I see only 17GB free. I'm not sure what to make of that quite honestly; just make sure your OS partition has the letter C. If that's already the case, set the computer to write only minidumps.

Right-click on My Computer, and select Properties.
In the right pane, click on "Advanced System Settings".
Under the Crashes section, click "Settings".
Change the setting from Kernel Dump to Small dump.

For now, run driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Also, run some hardware diagnostics. Start by running the three Prime95 tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Run Memtest86 for 7 passes: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

A few driver updates won't hurt.

Module Name:       b57nd60a
Display Name:      Broadcom NetXtreme Gigabit Ethernet - NDIS 6.0
Link Date:         4/26/2009 7:14:55 AM
http://www.broadcom.com/support/ethernet_nic/downloaddrivers.php

Module Name:       JRAID
Display Name:      JRAID
Link Date:         1/27/2010 3:58:17 AM
ftp://driver.jmicron.com.tw/SATA_Controller/Windows/JMB36X_WinDrv_R1.17.62_WHQL.zip

 

[goosegas]

I am sorry that you had to close one post.

I believe that the post you closed was a power supply issue, and not a BSOD post.

Anyway, the E: drive is my external hard drive, and the OS partition does have the letter "C".

I made the change from Kernel Dump to mini dump, hopefully that might help.

I will update the drivers as you suggested.

As far as the memtest86, their website tells me that the utility is not for Windows 7 64 bit, just for 32 bit versions.

One quick question about my memory.

One person who looked at my submission told me that my gigabyte 870A-UD3 motherboard doesn't support the 1600MHz memory installed. He claims the memory standard does not include it. I went to the Gigabyte website, where I found that same information, but when I click on the support tab of the MB, I believe I see my memory on the list as verified....I certainly see 1600MHz DDR3 as verified.

Can you give me your thoughts on that?

Thank You

 

[Jonathan_King]

It appears the 1600 MHz is an overclocked speed; the board by default only runs RAM at 1333MHz. That having been said, a motherboard can support RAM rated for speeds higher than listed, just not lower.

What is the model of your RAM? Also, please download CPU-Z and post a screenshot of both the Memory and SPD tabs.

Memtest86 is not dependent on the OS version installed; the latest versions support more than 4GB as well. Please use the link found in my Memtest86 tutorial, that will get you the latest version (4.20).

 

[goosegas]

Jon-

The screenshots for CPUID & HWMonitor were included in the original post.

Please take a look at those, and in the meantime I will run the hardware tests you suggested.

Also, I want you to know that since changing from kernel dump to mini dump, the computer frooze one, but didn't go to BSOD. I don't know if this is significant, but I figured I would include it. The event viewer revealed the same codes and info as with the BSOD's which were included in the original post.

Thank You

ps: I changed my power supply from a crappy XtremeGear to a Corsair a few days ago. I am certain I didn't bump anything, but I figure any bit of information might be helpful.

 

[Jonathan_King]

Did the BSODs start before or after the PSU change?

I don't think the dump type change will make a different on the stability of the system; I suspect that freeze is coincidental, but I could be wrong.

I do see your RAM listed as compatible for your board. I was confused by the 1600; 1600 MHz is not the speed, it's just the model. The speed is 667 MHz.

Do run Memtest86: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

That may be telling.

Also run the three Prime95 tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

 

[goosegas]

I am now officially confused. My memory can't be 667MHz, as I paid $100 extra for the 1600MHz upgrade pasted below. The part number on my sticks also reflects the part number on the A-Data website for 1600MHz memory.

There were some BSOD's back in Jan. w/old PSU, none recently until just after install of new Corsair PSU. Is it a coincidence or is it actually possible that the new psu created the problem? I was extremely careful not to bump into anything during the process.


Series Gaming Series Speed Rating PC3-12800 Tested Speed 1600Mhz Size 2GB Kit Cas Latency 9 Voltage 1.65V ECC No Type 240-Pin DDR3 SDRAM

 

[Jonathan_King]

Here is the webpage for your RAM: A-DATA OC Offical Website

Let me summon a RAM expert to give their say in this.

In the mean time, please run Memtest86 at the very least; run the Prime95 Blend test now too. Run the other two Prime95 tests when you get the chance.

Could you try replacing the old PSU, and see if that fixes anything?

 

[goosegas]

Jon-

I am currently on the 6th pass of Memtest, and so far there are no errors.

I have the list of remaining hardware tests that you and others have suggested, which will test the hard drive and the GPU as well.

Are you asking me to put the old PSU back in, to see if the BSOD's stop?

If so, is it because there is a chance that the new PSU is causing the problem?...wasn't sure that it was even possible, taking out the XtremeGear junk, thinking it is destroying my unit, and replacing it with a quality component....go figure.

Normally this might be a good option, but with this setup, which took me several hours to install the new Corsair, I would like to leave that as the last resort. I am hoping that the fact that this series of BSOD's beginning after the PSU switch out is just coincidental....tell me your thoughts on that.

Thank You

 

[Jonathan_King]

Are you certain you connected both the 24-pin motherboard power cable and the 8-pin auxiliary cable?

 

[goosegas]

Yes....I tripled checked, and both are connected and are firmly in place.

 

[goosegas]

I ran Memtest86 for 8 passes with zero errors.

I ran Prime95 with no errors

I ran Furmark with no errors

I ran Seatolols with no errors

I ran Driver Verifier, but I am not sure what it actually did. The computer needed to be restarted for the verifier to run, but the computer froze on the windows screen. I restarted the computer in safe mode, typed verifier /reset and the computer restarted normally.

I am out of ideas, I hope you guys aren't.

Again, all connections are snug inside the case.

Any chance the new Corsair PSU could do this?

If not, I think I am going to reformat the computer, as maybe we are dealing with a driver problem.

Please let me know what you think.

 

[Jonathan_King]

Driver Verifier runs in the background, testing drivers for bugs. Try enabling it again, and keep trying to boot (up to 6 times or so) until it lets you in. Once you're in, open a command prompt and enter verifier /query.

If you prefer to do a fresh install, that will immediately solve all software problems, unless you then reinstall the buggy program or driver. If the problem is hardware related, a fresh install will do no good.

I can't imagine how a healthy, higher powered PSU would cause any problems, but a defective PSU might. That's why it may be helpful to install the old PSU again.

 

[Dave76]

Hello goosegas, Jon has asked me to take a look at your issues.

First, Many people post their issues on several forums, hoping to get it resolved as quickly as possible.
This is not the best approach, if you are taking advice from another forum you need to give the details of what you have done to the other forums. Anything you do can affect the issues. Without full information on what you have done the people helping you will not be able to be effective.
If you are taking steps provided from another forum, give the details and steps taken, also when you have done them.


Second, there is a known issue with AMD CPUs integrated memory controllers having problems running RAM at 1600 MHz and above.

VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS

Change your RAM settings in BIOS to the lower 1333MHz, settings.
This will need to be done to rule out this issue.

Use the settings given on the CPUZ SPD tab, JEDEC #4, but use 667 MHz.
Manually set all these in BIOS.
The listed timings are 9-9-9-25 for the first four timings, leave the rest on 'Auto'.
Voltage 1.5v.
If you need help doing this, just let us know.

Go to your BIOS and tell us what the RAM and North Bridge (NB) voltages are.

Ususally 8GB RAM will require a NB voltage bump, report the NB voltage in your next post.
Do not change this voltage until we know what it is set at, too high voltage on this can damage your CPU.

Let us know if you have any questions, and any steps you have taken that are not posted in this thread.

 

[goosegas]

Thanks Dave-

I will be back to you shortly on the matter.

Regards

 

[goosegas]

Hi Dave-

I am going to make the memory adjustments tomorrow, but I just wanted to make you aware of a BSOD I just received which was different than the others.

This one read: "Memory Management"

Does this seem to be something that might respond favorably to the memory adjustments you suggested?

Thank You

 

[Dave76]

Yes, this is a common BSoD for the issues mentioned.

Tell us the BIOS voltage reading for CPU NB VID Control, this is important.

Let us know how it's going.

 

[goosegas]

Dave-

I went in BIOS, but I am not certain that I was able to find exactly what you are looking for.

I have listed what I did find below. If this is what you need, then please advise as to the changes you think I should make if any.

If not, please tell me how to navigate through the BIOS to find what you need.

CPU NB FREQUENCY AUTO 2800MHz
X CPU FREQUENCY (MHz) 200
MEMORY CLOCK X8.00 1600mHz
SYSTEM VOLTAGE AUTO
NB VOLTAGE CONTROL AUTO

*SYSTEM VOLTAGE OPTIMIZED*

SYSTEM VOLTAGE CONTROL AUTO
DRAM VOLTAGE CONTROL AUTO
NB VOLTAGE CONTROL AUTO
NB PCIE VOLTAGE CONTROL AUTO
CPU NB VID CONTROL AUTO

Thanks again for your help!

 

[Dave76]

Dave-

I went in BIOS, but I am not certain that I was able to find exactly what you are looking for.

I have listed what I did find below. If this is what you need, then please advise as to the changes you think I should make if any.

If not, please tell me how to navigate through the BIOS to find what you need.

CPU NB FREQUENCY AUTO 2800MHz
X CPU FREQUENCY (MHz) 200
MEMORY CLOCK X8.00 1600mHz
SYSTEM VOLTAGE AUTO
NB VOLTAGE CONTROL AUTO

*SYSTEM VOLTAGE OPTIMIZED*

SYSTEM VOLTAGE CONTROL AUTO
DRAM VOLTAGE CONTROL AUTO
NB VOLTAGE CONTROL AUTO
NB PCIE VOLTAGE CONTROL AUTO
CPU NB VID CONTROL AUTO

Thanks again for your help!

It's the 'CPU NB VID Control' if it's not giving you any voltage reading then set it to manual and increase it by the smallest amount and post the value.

Did you set the RAM frequency and timings as suggested in post #14?

 

[goosegas]

Dave-

The information I included in my last reply is all that I was capable of gathering.

I wasn't able to figure out exactly where I needed to be to change the RAM frequency and timings. Can you please help me to do that?

Also, in regard to the CPU NB VID Control, are you saying that when it is set on AUTO, there is a value assigned that I can actually see, so I know what the next setting upward would be? If I do set it on manual, what number should I use, if I can't see anything more than AUTO as the current setting?

Since we last talked, I reinstalled windows 7, to try to further eliminate the potential driver participation in the issue and provide more support to the RAM theory.

The computer went 24 hours without a BSOD, but in the last 2 hours I received 2. One said "Memory Management" and the event viewer info was exactly the same as in my original post. I wasn't able to read the second BSOD screen, as it stayed for only 2 seconds before the computer restarted itself.

Since I did reinstall the OS, I have included a new zip file, part of which is the new diagnostic file.

I noticed that once again, at the very top of the diagnostic file there is a warning of some kind, but also information stating that there is no detection of antivirus software. That statement is strange in that Avast was not detected before the reinstall and now McAfee is not detected, although running, after the reinstall.

Please advise and thanks again for all your help Dave.