Random Windows STOP ERROR (Blue screen of death)

[Brickster]

Please help if you can.

I recently finished building my new ultimate gaming machine. Check out my Sig, and you can see my set up includes the Gigabyte 939 mobo, an AMD-64 3500+, BFG 6800GT, and Corsair XMS 3200 XL RAM, etc.

Thing runs great, but ever since I built the thing, I was able to install Windows, Office 2K3, games, etc., and have been getting a random Windows STOP Error.

The error is as follows:

STOP: 0x0000007E (0xC0000005, 0x805B3072, 0xEDFC7AFC, 0xEDFC77FC)

I have been on MS Tech support site, and have determined the following:

0x0000007E = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0xC0000005 = STATUS_ACCESS_VIOLATION - A memory access violation occurred.

I have been unable to determine what the other 3 parameters are in the error message.

Nature of System Error
Typically happens about once every two or three days. Doesn't appear to be associated with any one program or activity - happens with general usage.
The system error generates a blue screen with the above stop error, then performs a physcial memory dump (minidump .dmp file) and the I must manually restart.
I am unable to gather any information from the DMP files.

Other than this, the system works wonderful. System benchmarks are outstanding.

So, needless to say, it is VERY frustrating to have such an unstable system.

My questions are:

1) Is this a RAM issue?
2) How can I further troubleshoot this?
3) Has anyone seen this before?

Things I am going to try -
> Memory Test (know any good ones?)
> Installation of Windows SP2
> Rollback nForce 3 Ultra driver - (anyone know how to do this?)

Thanks!

 

[Jeff7]

Memtest86+ for a RAM test. Run it through several loops. Some settings first:
1-2-2-3-3-2
I think that's the menu sequence once in Memtest86
Under the first menu, enable all cache.
Under the other menus (don't remember them exactly), enable Test All RAM, and enable All Tests. Then let it go through the loops. Any errors is a sign either of bad RAM, too little voltage, or quicker timings than the RAM can handle.

I figure a timing problem (or maybe voltage), since the errors are random. I set some cheap PC133 RAM to the motherboard's Turbo settings - over the next several reboots I got treated to a wide variety of BSOD's.

 

[Brickster]

Thanks Jeff7! I will try that when I get home.

 

[dclive]

Originally posted by: Brickster
Please help if you can.

I recently finished building my new ultimate gaming machine. Check out my Sig, and you can see my set up includes the Gigabyte 939 mobo, an AMD-64 3500+, BFG 6800GT, and Corsair XMS 3200 XL RAM, etc.

Thing runs great, but ever since I built the thing, I was able to install Windows, Office 2K3, games, etc., and have been getting a random Windows STOP Error.

The error is as follows:

STOP: 0x0000007E (0xC0000005, 0x805B3072, 0xEDFC7AFC, 0xEDFC77FC)

I have been on MS Tech support site, and have determined the following:

0x0000007E = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0xC0000005 = STATUS_ACCESS_VIOLATION - A memory access violation occurred.

I have been unable to determine what the other 3 parameters are in the error message.

Nature of System Error
Typically happens about once every two or three days. Doesn't appear to be associated with any one program or activity - happens with general usage.
The system error generates a blue screen with the above stop error, then performs a physcial memory dump (minidump .dmp file) and the I must manually restart.
I am unable to gather any information from the DMP files.

Other than this, the system works wonderful. System benchmarks are outstanding.

So, needless to say, it is VERY frustrating to have such an unstable system.

My questions are:

1) Is this a RAM issue?
2) How can I further troubleshoot this?
3) Has anyone seen this before?

Things I am going to try -
> Memory Test (know any good ones?)
> Installation of Windows SP2
> Rollback nForce 3 Ultra driver - (anyone know how to do this?)

Thanks!

Please check out my sig, do those steps, and send me the MPS Reports and dump files you've got.

<snip - I see you don't yet have SP2 on there; stick it on there....>

When I mean do all updates, I mean do ALL updates. Including sound, NIC, motherboard, BIOS, etc. Do *everything*. Then try to repro the problem. If you can, *then* run MPS Reports, and send me *that* dump, which was generated *after* you did all the driver updates.

Thanks.

 

[mechBgon]

The Corsair XL has a target voltage of 2.75V, so I hope you're making sure it gets something in the 2.7-2.8V range? Also, what power supply is towing the boat here?

I see from your System Rig specs that you also have an Audigy 2. Once I'm back on my own system, I'll see if Gigabyte's manual for your board includes an IRQ-sharing chart, since that sometimes ends up being a fly in the ointment with A2's. In the meantime, disable the motherboard's MIDI, Gameport, Firewire and audio in the motherboard BIOS since those functions are duplicated by the A2.

 

[Brickster]

Originally posted by: mechBgon
The Corsair XL has a target voltage of 2.75V, so I hope you're making sure it gets something in the 2.7-2.8V range? Also, what power supply is towing the boat here?

I see from your System Rig specs that you also have an Audigy 2. Once I'm back on my own system, I'll see if Gigabyte's manual for your board includes an IRQ-sharing chart, since that sometimes ends up being a fly in the ointment with A2's. In the meantime, disable the motherboard's MIDI, Gameport, Firewire and audio in the motherboard BIOS since those functions are duplicated by the A2.

Antec True 550W is the PSU.

I will disable the MIDI, Gameport, and Audio...but not the Firewire...I'm using Front panel Firewire/USB 2.0 which connects to the mobo.

Thanks for the help...I look forward to the IRQ-sharing chart.

BTW - I am scare to install SP2...heard bad stuff in the news today (15% of people trying having system error issues)

Thanks guys,

 

[Brickster]

Update:

New STOP error...

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

 

[dclive]

Originally posted by: Brickster
Update:

New STOP error...

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

Same story - check the URL in my sig, update all drivers, mail me...etc...etc....

 

[dclive]

Originally posted by: mechBgon
The Corsair XL has a target voltage of 2.75V, so I hope you're making sure it gets something in the 2.7-2.8V range? Also, what power supply is towing the boat here?

I see from your System Rig specs that you also have an Audigy 2. Once I'm back on my own system, I'll see if Gigabyte's manual for your board includes an IRQ-sharing chart, since that sometimes ends up being a fly in the ointment with A2's. In the meantime, disable the motherboard's MIDI, Gameport, Firewire and audio in the motherboard BIOS since those functions are duplicated by the A2.

FYI.... assuming the machine is an ACPI machine and Windows XP is installed using ACPI (ie he didn't hit F5 right around the F6-to-select-your-disk-controller prompt), IRQ settings in the motherboard will be ignored by Windows XP, and XP will PnP and change IRQs to suit itself. I'd be interested, too, to see what Gigabyte has written on the subject. Microsoft is pretty clear: http://support.microsoft.com/default.aspx?scid=kb;en-us;314068&amp;Product=winxp

 

[mechBgon]

Originally posted by: dclive

Originally posted by: mechBgon
The Corsair XL has a target voltage of 2.75V, so I hope you're making sure it gets something in the 2.7-2.8V range? Also, what power supply is towing the boat here?

I see from your System Rig specs that you also have an Audigy 2. Once I'm back on my own system, I'll see if Gigabyte's manual for your board includes an IRQ-sharing chart, since that sometimes ends up being a fly in the ointment with A2's. In the meantime, disable the motherboard's MIDI, Gameport, Firewire and audio in the motherboard BIOS since those functions are duplicated by the A2.

FYI.... assuming the machine is an ACPI machine and Windows XP is installed using ACPI (ie he didn't hit F5 right around the F6-to-select-your-disk-controller prompt), IRQ settings in the motherboard will be ignored by Windows XP, and XP will PnP and change IRQs to suit itself. I'd be interested, too, to see what Gigabyte has written on the subject. Microsoft is pretty clear: http://support.microsoft.com/default.aspx?scid=kb;en-us;314068&amp;Product=winxp

All true, but it doesn't change the hardware-level IRQ stuff a bit. The three desktop-board makers who habitually cover the interrupt routing are Intel, Abit and Asus. Read one or two hundred mobo manuals and you start to notice this stuff

To ask again, what memory voltage we got going to those memory modules? 2.7 to 2.8 volts, I hope?

BTW - I am scare to install SP2...heard bad stuff in the news today (15% of people trying having system error issues)

You can uninstall SP2 if it really works that badly. I just built a new 'puter for my middle sister and SP2'ed it and it's working fine (AthlonXP, nForce2, GeForce2 GTS, Corsair XMS, Seagate ATA100, DVD-ROM/CD-RW drive, USB card reader, VirusScan 8.0 Pro, Works Suite 2004, and dial-up, woohooo! ). Anyway, it has SP2 and no issues so far

 

[Brickster]

Originally posted by: mechBgon
To ask again, what memory voltage we got going to those memory modules? 2.7 to 2.8 volts, I hope?

I am not sure how to check this. I went to the DDR Voltage Control in the BIOS, and there were only 3 options: Default, +0.1v, and +0.2v. Didn't say what the default is. Shall I use a software OC package to determine this???

BTW - you guys are awesome. Consider me your hardware slave: you say, I do. As opposed to many people who encounter problems, and BSOD's, I consider this kinda fun...a challenge.

I figure it's to be expected when you buy cutting edge.

Thanks,

 

[Brickster]

Originally posted by: dclive
is an ACPI machine and Windows XP is installed using ACPI (ie he didn't hit F5 right around the F6-to-select-your-disk-controller prompt), IRQ settings in the motherboard will be ignored by Windows XP, and XP will PnP and change IRQs to suit itself. I'd be interested, too, to see what Gigabyte has written on the subject. Microsoft is pretty clear: http://support.microsoft.com/default.aspx?scid=kb;en-us;314068&amp;Product=winxp

All I can tell you is that under Device Manager, under Computer is says: "ACPI Uniprocessor PC"

 

[Jeff7]

Originally posted by: Brickster

Originally posted by: mechBgon
To ask again, what memory voltage we got going to those memory modules? 2.7 to 2.8 volts, I hope?

I am not sure how to check this. I went to the DDR Voltage Control in the BIOS, and there were only 3 options: Default, +0.1v, and +0.2v. Didn't say what the default is. Shall I use a software OC package to determine this???

BTW - you guys are awesome. Consider me your hardware slave: you say, I do. As opposed to many people who encounter problems, and BSOD's, I consider this kinda fun...a challenge.

I figure it's to be expected when you buy cutting edge.

Thanks,

Does your BIOS have a section that says "PC Health" or something like that? If not, look through your menus for temp and voltage readouts. Hopefully something there will show the voltages.
As far as I know, default voltage for DDR is 2.5V, so +0.2 should give you 2.7v. But I'd say to check what it's running at already. Some boards run voltages higher than what they're set to. I've got a system with a cheap Amptron board in it; it's supposed to give the CPU 1.7V. The hardware monitoring in BIOS reports 1.82v, and there's no voltage controls to reduce it - and I can't get BIOS updates at Amptron's site; doubtful they'd add voltage tweaking anyway.

 

[Brickster]

Okay,

I did have a "PC Health" in the BIOS, and it said:

VCORE OK
DDR25V OK
+3.3V OK
+12V OK

Based on that, and the EasyTune4 OCing program that came with my Gigabyte Mobo CD, I have determined that my default is 2.5V for the RAM.

What I did: Went into the BIOS, and selected +0.2V, giving me 2.7V for my DRAM. This has been verified in EasyTune, as the default setting for the RAM voltage now shows as 2.7V vs. 2.5V.

**EDIT**: Oops, looks like test voltage is 2.75, and not 2.7 as posted by mechBgon (sorry I didn't pay close enough attention) Since BIOS will only go up to 2.7, looks like I may have to use EasyTune to up it 0.05V to 2.75V. Sound correct?

I am going to hold off on installing XP SP2 since I want to try fixes one at a time, so I have to wait to see if I continue with BSOD's first. Should happen today or tomorrow for verification.

I will keep you guys updated.

Any other voltage recommendations for the rest of my system? CPU is at 1.525V.

Thanks dudes!

 

[dclive]

Originally posted by: Brickster

Originally posted by: dclive
is an ACPI machine and Windows XP is installed using ACPI (ie he didn't hit F5 right around the F6-to-select-your-disk-controller prompt), IRQ settings in the motherboard will be ignored by Windows XP, and XP will PnP and change IRQs to suit itself. I'd be interested, too, to see what Gigabyte has written on the subject. Microsoft is pretty clear: http://support.microsoft.com/default.aspx?scid=kb;en-us;314068&amp;Product=winxp

All I can tell you is that under Device Manager, under Computer is says: "ACPI Uniprocessor PC"

OK, so per Microsoft:

Manually assigning IRQs to PCI slots in the system BIOS as a troubleshooting method may work on some non-ACPI systems that use a standard PC hardware abstraction layer (HAL), but these settings are ignored by Plug and Play in Windows if ACPI support is enabled. If you must manually assign IRQ addresses through the BIOS to a device on an ACPI motherboard, you must reinstall Windows to force the installation to use a Standard PC HAL.

changing IRQs in the motherboard shouldn't make a difference. In fact, Microsoft says *don't* do this if you want to stick with ACPI systems. I think the motherboard advice/information is for other, older, non-ACPI OSs.

But I'd welcome links with other information, talking about XP and ACPI systems!

 

[Brickster]

Also,

Ran MemTest....NO ERRORS! yay!

 

[Brickster]

I am unable to increase my memory voltage by +0.05V. IT only does increments of 0.1V. Therefore, I can only do 2.7V or 2.8V, and not the 2.75V.

Would you say it's better to be on the low side or the high side of tested/recommended voltage?

Should I maybe use another program to up the voltage?

 

[mechBgon]

I'd try 2.7V and then 2.8V if needed.

changing IRQs in the motherboard shouldn't make a difference. In fact, Microsoft says *don't* do this if you want to stick with ACPI systems. I think the motherboard advice/information is for other, older, non-ACPI OSs.

I think we're talking about two different types of IRQ lines. Scope out this. (an example, not the actual board in question here)

 

[Brickster]

Saturday night, er, make that Sunday morning: 12:21AM

Played FarCry for about 4 hours.

System has been BSOD free for two days now - a welcomed improvement

<fingers crossed>