Overclocking causing XP blue screen of death?
On my new Athlon 2100+ system (oc'ed to about 2.1g) I occassionaly get a
blue screen with a bunch of white letter on XP that automatically reboots my system. This usually happens when I'm using a program (a game, a CD burner, etc.) The code is something like 0x0000000D1. I went to the event log and it said it was a TrueVector problem. TrueVector being Zonealarm, I unistalled it. The same problem happened again, only this time it was blamed on Volume Shadow Copy. I ran memtest86 for like 10 hours (watching the playoff games) and it reported no errors. Is the overclocking causing this? Should I back off a little bit? Or has anyone else had this problem and solved it? Thanks. |
GlueGum wrote:
On my new Athlon 2100+ system (oc'ed to about 2.1g) I occassionaly get a blue screen with a bunch of white letter on XP that automatically reboots my system. This usually happens when I'm using a program (a game, a CD burner, etc.) The code is something like 0x0000000D1. I went to the event log and it said it was a TrueVector problem. TrueVector being Zonealarm, I unistalled it. The same problem happened again, only this time it was blamed on Volume Shadow Copy. I ran memtest86 for like 10 hours (watching the playoff games) and it reported no errors. Is the overclocking causing this? Should I back off a little bit? Or has anyone else had this problem and solved it? Thanks. Yes, overclocking is very likely causing it. Back it down (or increase the core voltage a bit) and run Prime95 to check for stability. Prime95 actually stresses the whole system, so it's an excellent program to test stability. It should run for hours without any error. http://www.mersenne.org/freesoft.htm -- "I love deadlines. I love the whooshing noise they make as they go by." Douglas Adams |
GlueGum wrote: On my new Athlon 2100+ system (oc'ed to about 2.1g) I occassionaly get a blue screen with a bunch of white letter on XP that automatically reboots my system. This usually happens when I'm using a program (a game, a CD burner, etc.) The code is something like 0x0000000D1. I went to the event log and it said it was a TrueVector problem. TrueVector being Zonealarm, I unistalled it. The same problem happened again, only this time it was blamed on Volume Shadow Copy. I ran memtest86 for like 10 hours (watching the playoff games) and it reported no errors. Is the overclocking causing this? Should I back off a little bit? Or has anyone else had this problem and solved it? Thanks. I've had that happen a few times when pushing up the speed hard. Increasing the voltage to the processor stops it on my machine. I've run my Barton as high as 2400 but have to set the vcore to 2.0V to do it. If I don't set the voltage up that high it blue screens before it finishes booting and usually corrupts a couple of startup files. Roger |
This could be due to a number of things...
Possibly a poor power supply, or not enough voltage to the cpu. Check the 12v rail, make sure it's getting what it needs IE: 12 volts. Or possibly your cpu/motherboard combo just can't handle it. - Jordon "GlueGum" wrote in message . .. On my new Athlon 2100+ system (oc'ed to about 2.1g) I occassionaly get a blue screen with a bunch of white letter on XP that automatically reboots my system. This usually happens when I'm using a program (a game, a CD burner, etc.) The code is something like 0x0000000D1. I went to the event log and it said it was a TrueVector problem. TrueVector being Zonealarm, I unistalled it. The same problem happened again, only this time it was blamed on Volume Shadow Copy. I ran memtest86 for like 10 hours (watching the playoff games) and it reported no errors. Is the overclocking causing this? Should I back off a little bit? Or has anyone else had this problem and solved it? Thanks. |
All times are GMT +1. The time now is 02:06 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
HardwareBanter.com