Lots Of BSOD's and game crashes HELP!!

[ratus06]

Hey guys i recently got a new pc, and for the past 2 weeks have been trying to get it working. I got this new pc mainly for gaming, and its rather frustrating when i cant get the performance out of it.
Pc Specs -
Processor: intel core2 duo e6850
Motherboard: gigabyte n650SLI-DS4
Ram: GEIL 2 x ddr2-800
GFX card: Albatron GTS8800 640mb
PSU: Thermaltake 450w
Operating system: Windows XP

My problem is I'm getting a alot of BSOD's sometimes i can be just in IE or something simple, but most are during games (Counter Strike: Source, counterstrike 1.6, WC3). I've reinstalled windows, ran memtest(9hrs with no errors),tried running with one stick in one stick out, i dont really want to +mess with bios settings cause im not that advanced with pc's but can if needed. I thought it was overheating causing crashes, cause i could get stress tests to make both cores go up to 65C (core temp 0.95.4), this could possibly still be a problem. But i had a crash whilst on the desktop, and the temps were 47-50 at the time. Next i thought psu, so im currently in the process of borrowing a 600w just to test. But one thing i dont understand is in speedfan readings, the voltages are as follow:
Vcore1 : 1.06V
Vcore2 : 1.94V
+3.3V : 4.30V
+5V : 4.87V
+12V : 0.32V (surely that isnt right??)
-12V : -16.97V (too high?)
-5V : -5.66V
+5V : 5.21V
Vbat : 3.14V

If someone can help me understand these voltage readings that would be good. I have posted some of my error logs i have received. This is only some of them i had saved early, for some unknown reason after a crash all my system reports in event veiwer were erased.. I can post minidumps of the first 3 errors if needed, they are the latest and some minidumps i had uploaded previously.


The computer has rebooted from a bugcheck. The bugcheck was: 0x100000e (0xc0000005, 0x805144f8, 0xa6bf03d8, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini102707-01.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000000, 0x00000002, 0x00000000, 0xb246ce7f). A dump was saved in: C:\WINDOWS\Minidump\Mini102707-02.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000f (0x00000008, 0x80042000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini102607-02.dmp.

Save Dump Event Id: 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc000001d, 0xa9cedd9c, 0xba967b60, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini101307-01.dmp.

Save Dump Eventid: 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x00000099, 0x00000000, 0x00000001, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini101207-02.dmp.

Save Dump event id: 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xc0000005, 0xe7d132e6, 0xbad77c6c, 0xbad77968). A dump was saved in: C:\WINDOWS\Minidump\Mini101207-01.dmp.

Save Dump : event id : 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x00003451, 0xc05419b8, 0x88b94478, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini101107-03.dmp.

Save Dump : Event id: 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000093 (0x00000dc8, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini101107-02.dmp.

Error : system error : Event id : 1003
Error code 100000be, parameter1 30000000, parameter2 7f3f2025, parameter3 bacc7ab4, parameter4 0000000a.

Save Dump: event id 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000be (0x30000000, 0x7f3f2025, 0xbacc7ab4, 0x0000000a). A dump was saved in: C:\WINDOWS\Minidump\Mini101107-01.dmp

Error: System Error: event id: 1003
Error code 100000d1, parameter1 00000000, parameter2 00000002, parameter3 00000001, parameter4 b14e5300.

Save dump : event id 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000000, 0x00000002, 0x00000001, 0xb14e5300). A dump was saved in: C:\WINDOWS\Minidump\Mini100907-03.dmp.

Faulting application hl2.exe, version 0.0.0.0, faulting module datacache.dll, version 0.0.0.0, fault address 0x0000b423.

Fault bucket 496034840.

Faulting application ventrilo 2.3.0.exe, version 2.3.0.0, faulting module ventrilo 2.3.0.exe, version 2.3.0.0, fault address 0x00089cde.

If anyone can help me with this problem it will be greatly appreciated, as ive searched so many forums and read alot about it, with no solution.

 

[SNGX1275]

Yep your voltages are too far off. It 'could' be your monitoring program is wrong. I'd run memtest86 on your ram too. Although I'm not sure I'd trust memtest if your psu is bad, but then on the otherhand if your ram tests fine those voltages are terrible.

 

[ratus06]

I ran memtest86 for 9hrs both sticks in no errors. And yeah possibly speedfan readings are wrong. But im willing to try anything? Any suggestions?

 

[peterdiva]

Speedfan isn't reliable. Install the monitoring program that came with your motherboard (Easy Tune 5). This should also tell you the RAM voltage. If the voltages are ok then you can try raising the RAM voltage, but you'll need to find out what it's currently set at first (1.8v?).

 

[ratus06]

It seems the voltages are fine if im looking at it right. Under pchealth > Hardware Monitor the voltages are VCoreA - 1.130, +3.3V - 3.290, +12V - 12.300, CPU Vid - 1.270. So theyre fine but the fans column it has cpu at 630 and pwr1 and system at 0 and all 3 of them have a caution symbol flashing, not sure wat that means. Temp is system 51C and cpu 38C.
Memory voltage is set to 1.80. In bios the ddr2 voltages, are at increments of like 0.2, 0.25, does that mean like 2.0V 2.5V???? or do i change the voltages through this easy tune 5 program??

 

[peterdiva]

The manual says "+0.025V~+0.775V Increase the DDR2 voltage by 0.025V to 0.775V". So I would take that to mean if you set it to 0.025V it would increase the voltage to 1.825V. I would set it to 0.025 first and then check that it is set at 1.825V. You can play safe and only increase it a notch at a time if you want, checking to see if things stabilise after each one. Don't go above 2.1V, and change it in the BIOS.