Alright, I just finished building and testing my new system. I thought I had it stable with these configurations, but when I tried to install the v1.10 patch for Battlefield 2142, my system went to a blue screen that said something like
"A critical error has occured, Windows is now shutting down your computer to prevent damage from occuring"
Here is my computer:
Processor: Core2Duo E6300
Motherboard: Gigabyte GA-965-S3
Ram: GeIL 1GB (2 x 512MB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) 5-5-5-15 1.8V
PSU: FSP Group (Fortron Source) AX450-PN, 12cm FAN, version 2.0
Video Card: eVGA 256-P2-N624-AR GeForce 7900GS 256MB 256-bit GDDR3 PCI Express x16 KO
HD: Maxtor 7200 RPM EIDE 300GB
DVD: Some kinda BENQ EIDE DVD Burner
Case Fans: 2 Antex Tricools 120mm (intake and side exhause) and 1 generic 120mm (rear exhaust)
CPU Fan: Stock Intel fan with a rice sized dab of Arctic Silver 5
OS: Windows XP Pro SP2 with full updates
And my BIOS settings, and yes I flashed them to the latest revision (F6 I think it is?):
Advanced BIOS Features
- Disabled CPUID Max to 3
- Disabled No-Execute Memory Protection
- Disabled C1E
- Disabled TM2
- Disabled EIST
- Disabled Virtualization Technology
PC Health Status
- Disabled Smart Fan Control Method
Motherboard Intelligent Tweaker (M.I.T.)
- CPU Clock Ratio (CPU Multiplier) at 7x
- CPU Host Frequency (FSB) at 400MHz
- PCI Express Frequency at 100MHz
- Disabled CIA2
- System Memory Multiplier at 2.00 (1:1 Ratio)
- DRAM Timing at 5-5-5-15
- FSB OverVoltage +0.2V (1.4V)
- (G)MCH Voltage +0.1V (1.55V)
- CPU Voltage at 1.300V
I ran Orthos, CoreTemp, CPU-Z and Speed-Fan. Everything looked stable. Idle temps were around 43-45 C and loaded temps were around 55-58C. I ran Orthos for 10 and a half hours without any errors.
I didn't run Memtest86+ because Orthos was stable and it seems difficult to run. All the downloads for Memtest86+ want to run it through a bootable floppy, is there no way to run it from inside Windows XP?
So there you have it, any idea what would make it unstable?
Edit: Allright, so I toned everything down to defaults and everything ran fine for a while, then I got the same error while running Battlefield. I'm pretty sure it's a software bug and I've clocked everything back up and things are perfectly stable. So false alarm.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.