HELP! Computer crashes every 2 hours, out of options

[Shoal07]

HELP!

This is the third week now. Let me break down my major issue that I Cannot figure out. I have built systems for years and this is a first...

System:
Thermaltake VA3000 Dream Tower Black VA3400BWA ATX Case

OCZ OCZ520ADJ ATX 520W Power Supply 100-120V AC/200-240V AC TUV, UL, CSA, CE, CB, FCC ? Retail (ditched the 400w that came with the case, it?s a 20pin ATX and I needed a 24 pin)

NEC 16X Double Layer DVD±RW Drive, Black w/ Software, Model ND-3520A, OEM

3x Western Digital Raptor 74GB 10,000RPM SATA Hard Drive, Model WD740GD, OEM Drive Only, in RAID 5 setup

OCZ Dual Channel Platinum, 184-Pin 2GB(1GBx2) DDR PC-3200 -Retail

DFI "LANPARTY UT nF4 SLI-DR" NVIDIA nForce4 SLI Chipset Motherboard For AMD Socket 939 CPU

AMD Athlon 64 FX-55, 1MB L2 Cache, 64-bit Socket 939 Processor - OEM

Microsoft Windows XP Professional With Service Pack 2 -OEM

Creative Labs Sound Blaster Audigy2 ZS PCI Sound Card, Model "SB0350" OEM

2x XFX nVIDIA GeForce 6800 GT Video Card, 256MB GDDR3, 256-Bit, Dual DVI/TV-Out, PCI-E, Model "PVT45GUD" -RETAIL

ZALMAN Copper CPU Cooler for Socket 775/478/754/939/940, Model "CNPS7700-CU" ?RETAIL

Problem:
Every 1 1/2 to 2 1/2 hours the system crashes. Either it reboots, freezes, blue screens, you name it. The errors appear to either be related to some Nvidia driver or more recently also a disk error (as windows reports after the crash).

Tests run:
I have used Burn in test from Passmark and the computer always passes fine (trial only runs for 15 mins). I have also booted from a CD Memtest and run many tests on the memory. All pass fine. When the system is running, up until it crashes, I can find no issues, problems or other demons. It is not overclocked. I have tried different drivers from Nvidia and now use Guru3d?s latest.

My only conclusion:
I am stumped. The only conclusion I have is that the system is overheating. The CPU runs at around 40c even under load (god bless Zalman). However, the video cards (or card, only has one in right now, didn?t help or change anything from SLI) seems to be between 70c and 75c before the crash. I talked to an XFX engineer over the phone and he said that does seem high (duh!). Also, the south bridge has an el-cheapo fan on it and its right next to the video card. Using the hand heat check the air in this area does seem to be quite warm. I have sent all the info to the XFX engineer as requested and now it?s been 2 weeks and they haven?t responded. I can?t send these things back to Newegg without paying a restock fee unless XFX says they?re defective. And I personally can?t be positive it?s them. What if I replace them and this still happens (I cant swap them out I don?t have any extra PCIx cards).

What I am looking for:
What are your conclusions? Is this heat? Bad part somewhere that is doing this? Something I have overlooked? The Raid 5 setup? Any help is appreciated. Ask any questions, I?ll answer them.

Please, you guys are my last hope.

 

[Fern]

Hi Shoal07 and Welcome to the Forums!

IMHO, memtest needs to be run for 12-24hrs to adequately test ram.

I'd suspect heat or PSU. I'd use motherboard monitor and enable the "sys log" feature to record temps and voltages, but I don't know if the auto set-up will work on that newer mobo. MBM5 would then have to be manually configured.

Just for kicks, I'd put the cheapo 400watt psu in there (prolly have to use just one vid card though) and pull off the case side panel and point a box fan at it and see what happens.

Good luck with it,

Fern

EDIT: Have you got newest chipset/vid drivers in there?

 

[FlyingPenguin]

Process of elimination. Some suggestions:

- Have you run MEMTEST all night? Running it for just 1 pass tells you nothing. If it runs all night stable then your RAM is okay.

- Has it always done this, or is this something recent? If recent, did it start after making ANY changes to the system? Try doing a system restore back to a WEEK before the problem occured.

- Try UNDER clocking the CPU (lower your FSB clock by 33Mhz) and see if it's stable. If so, you know you probably have a hardware stability issue and not software.

- Set your BIOS to load "Safe" default settings instead of the optimized settings. If it behaves then tweak your BIOS one thing at a time until you find out what's making it unstable.

- Leave the cover off the computer, point a desk fan at the area of the CPU, GPU & mobo chipset. BTW: I don't like Northbridge fans. I usually replace them with Zalman heatsinks.

- Bad capacitors. Not likely if this is a new mobo though, but check for bulging large capacitors on the mobo in the area of the CPU and regulators as shown in these photos: http://www.pcstats.com/articleview.cfm?articleID=195

- Real stretch, but could be a hair-line crack on the mobo or a memory stick. I've seen it often enough. With the computer running LIGHTLY tab the tops of your memory sticks with the PLASTIC or RUBBER handle of a screw driver. Also tap the backs of all the cards and areas of the mobo (top of all the large mobo chips, large capacitors near the CPU, etc). If the computer freezes or reboots when while you're tapping you have possible hairline crack, or maybe a poorly seated card or memory stick. Sometimes they can BARELY make contact and as the case heats up and parts expand, the contact is broken. More careful tapping will localize the specific area/part.

Hope this helps...

 

[Shoal07]

Originally posted by: Fern
Hi Shoal07 and Welcome to the Forums!

IMHO, memtest needs to be run for 12-24hrs to adequately test ram.

So do you think it's the ram? Should I test it longer?

I'd suspect heat or PSU. I'd use motherboard monitor and enable the "sys log" feature to record temps and voltages, but I don't know if the auto set-up will work on that newer mobo. MBM5 would then have to be manually configured.

Just for kicks, I'd put the cheapo 400watt psu in there (prolly have to use just one vid card though) and pull off the case side panel and point a box fan at it and see what happens.

Yeah, I've had the case off, even pulled the dirves out and set aside to reduce heat. It's a cool basement too. I can't use the 400w because it's 20 pin not 24 pin. And I am only using 1 vid card ATM.

Good luck with it,

Fern

EDIT: Have you got newest chipset/vid drivers in there? Yes

 

[Shoal07]

Originally posted by: FlyingPenguin
Process of elimination. Some suggestions:

- Have you run MEMTEST all night? Running it for just 1 pass tells you nothing. If it runs all night stable then your RAM is okay.

I did 5+ passes (like 1 1/2 hours with 2 gigs) But we can try a 24 hour run (unless it crashes)

- Has it always done this, or is this something recent? If recent, did it start after making ANY changes to the system? Try doing a system restore back to a WEEK before the problem occured.

Always did it, new system

- Try UNDER clocking the CPU (lower your FSB clock by 33Mhz) and see if it's stable. If so, you know you probably have a hardware stability issue and not software.

I'll have to try this (friend has the computer, I built it for him)

- Set your BIOS to load "Safe" default settings instead of the optimized settings. If it behaves then tweak your BIOS one thing at a time until you find out what's making it unstable.

- Leave the cover off the computer, point a desk fan at the area of the CPU, GPU & mobo chipset. BTW: I don't like Northbridge fans. I usually replace them with Zalman heatsinks.

What kind? I'd like to do this but don't know how (haven't done it yet)

- Bad capacitors. Not likely if this is a new mobo though, but check for bulging large capacitors on the mobo in the area of the CPU and regulators as shown in these photos: http://www.pcstats.com/articleview.cfm?articleID=195

- Real stretch, but could be a hair-line crack on the mobo or a memory stick. I've seen it often enough. With the computer running LIGHTLY tab the tops of your memory sticks with the PLASTIC or RUBBER handle of a screw driver. Also tap the backs of all the cards and areas of the mobo (top of all the large mobo chips, large capacitors near the CPU, etc). If the computer freezes or reboots when while you're tapping you have possible hairline crack, or maybe a poorly seated card or memory stick. Sometimes they can BARELY make contact and as the case heats up and parts expand, the contact is broken. More careful tapping will localize the specific area/part.

When I get to try your other options I'll try this.

Hope this helps...

 

[Fern]

You'll need more time with memtest to tell if your ram is OK.

See if you can try another PSU. Since it's crashing at 2 hrs, I'm wondering if the PSU is overheating. Confirm the psu fan is turning too.

 

[Necrolezbeast]

Is that OCZ PSU the modstream or the powerstream? I have the modstream and it runs fine but from what I have heard, some people have low 12v rails with it and with that much stuff being powered by the 12v line I would imagine if it was running low it would cause the system to be really flaky when under load.

 

[Shoal07]

To those that suggested loading the bios safe defaults instead of optimized... There are no safe load options, only optimized. Well, that's a first for me. Going to update the bios now. Hope that helps.

 

[Shoal07]

Ok, let me break this down:

1. It crashes right at about the 1 1/2 hour mark when at full load. It crashes pretty close to the same time (1 1/2 - 2hrs) if it's just sitting at the desktop.

2. For those that said load the bios Fail-Safe defaults... There aren't any. Only "Load" option is optimized...??? New technology, bleh

3. When the system does crash the vid card is at about 75c. The ONLY other component hot enough to feel the heat coming off with your hand is the mobo chip with a fan in the lower right part of the board (I guess it's the northbridge) and that sucker is really hot as well.

4. The blue screen I get does not give much info, just a string of code that I can't decipher (not like if it said nvsys.dll or something)

5. I am pretty sure I removed the NV SW Driver. What I did was uninstall all nvidia drivers. Then I booted into safe mode. I used Detonator Destroyer to clean up the rest of the nvidia files. rebooted. Installed the mobo files from Nvidia's site (dated May 17th) for Nforce4 Standalone. I installed all drivers (including the IDE drivers, but I'm supposed to right?) but NOT the SW driver. Then installed the display driver.

6. The computer runs like a dream up till it crashes. Until then not a sound crackle, video stutter, lag, reduced performance, nada. Even with only one 6800GT it's running WoW with all options on high, no problems. Runs EQ2 like a dream as well.

My only conclusion, again:
Has to be heat. I mean, doesn?t it? What else could run these high end MMOs which use all the system memory, tax the CPU and GPU, run advance sound, and even page to the HDs without fail for almost 2 hours? I can't figure this out for the life of me. I know people say the 6800 GPUs should handle 75c but what about that Northbridge chip? Is it failing due to heat? How can I cool it since the stock POS fan on there now just barely allows clearance for the vid card. Also, why does it crash at about the same time at full load as when just sitting at desktop. Shouldn't it crash faster at full load if it's heat vs the desktop. I have had comps with heat issues before and they exhibit this pattern (maybe 30 mins at full load but will run forever sitting at the desktop).

The only other thing I can imagine is the memory timings may be too aggressive. I mean, they're running at the rated speeds (2-2-2-5 @ 1T) which the mobo set up as default. I have had other memory in the past (mainly Mushkin cause I like Mushkin) that would run at the rated max speed for a limited time, then fail. Only when I dropped it down to something like 3-3-3-7 from a rated 2-2-2-5 would it stop crashing. But this mobo's memory timing options are so complicated (there are like 12 options for timings) that I don't want to mess with it. But, if this is possible the issue maybe you guys can tell me what to do.
And what about the 1T timing. I had heard mobos have issues with 1T and to run at 2T. But this is the first system I have built that even tells me the T timing and I don't know if I should mess with it or not.

 

[stevty2889]

Well nvsys.dll is part of your video drivers. Have you tried using an older driver for the video card? 75c is a bit warm for the graphics card, but shouldn't be causing it to crash. Mine gets close to that temp under load as well. What votlage do you have your memory at? It should be 2.7 or 2.8v, if it's not, trying upping the memory voltage, especialy since you said it stopped crashing when you loosened the timings You could also go to 2.9v to see if that helps. Have you tried running prime95 torture test at all? This will stress your CPU to help eliminate that as the problem(it's unlikely the be the cpu, but doesn't hurt to check). If that doesn't cause it to crash, the SuperPI 32m test will stress both the CPU and the memory. If that still doesn't do it, run prime95, while looping 3dmark01, that will stress the CPU and video card together.

 

[Shoal07]

Originally posted by: stevty2889
Well nvsys.dll is part of your video drivers. Yes, but I said it ws not something I could tell, like nvsys, but jarbled code Have you tried using an older driver for the video card? 75c is a bit warm for the graphics card, but shouldn't be causing it to crash. Mine gets close to that temp under load as well. What votlage do you have your memory at? It should be 2.7 or 2.8v, if it's not, trying upping the memory voltage, especialy since you said it stopped crashing when you loosened the timings You could also go to 2.9v to see if that helps. The memory example was not for this board, but others I have had issues with in the past Have you tried running prime95 torture test at all? Not prime, but others, heck, it's worth a shot. Does prime tell you what went wrong if the system crashes? This will stress your CPU to help eliminate that as the problem(it's unlikely the be the cpu, but doesn't hurt to check). If that doesn't cause it to crash, the SuperPI 32m test will stress both the CPU and the memory. If that still doesn't do it, run prime95, while looping 3dmark01, that will stress the CPU and video card together.

Good stress test tips. I'll try em and see what I can get to fail.

 

[Shoal07]

So Nvidia IDE, SW, and audio drivers removed, still have the same issue.

Some have suggested it may be a RAID 5 issue with the OS and the paging file. Any comments on this? Gonna try one HD and no raid tonight. I have a suspicious feeling it?s got to be a software issue. Either driver or OS. I have removed the Nvidia IDE and SW drivers but still have the same issue. 5 tech boards and all my geek friends and we?re all still perplexed. It sucks to have an uncommon issue?

 

[Shoal07]

Ok, I know it's not heat. I had a fan blowing into the system. When the computer crashed (at 1 1/2 hour) the Vid card was at 64C, Northbridge at 48C, CPU 42C. Memory was cool to the touch. Heck, I was two feet away and freezing.

I am currently (like, right at the moment) running prime95's extreme test or whatever it's called to stress the CPU, Cache and Memory. The CPU is up to 52C (highest it's ever been), the memory is warm, and I can feel the heat of the air comming out of the case. Again, it can't be a heat issue or it would of crashed by now (this is probably the hottest it's ever been).

A techie I work with said he had regular issues when the bios would drop his HDs into power save mode. It would happen if they weren't accessed for 20 mins then if they came back on the system was unstable and would crash. I have all the power save options in the bios disabled and in windows they're all on "never". Even the screen saver is off. He also said since it is religiously every 1 1/2hours then there has to be some program that kicks on at 1 1/2 hours and creates a memory/disk paging or allocation/conflict error (hence, BSOD). What the hell could that be? I have norton and windows auto updates off, and anything else I can think of off. Is there somewhere I can go and post all the stuff that's running so you guys can look it over (msconfig maybe?)

Prime said if your power supply was inefficent the voltages should drop when you start the test. Needless to say, they are rock solid. Let me give you what Hmonitor shows as the voltages:

+12v = +12.03v
+5v = +4.89v
Core = +1.46v
I/O = +3.31v (this is the 3.3v rail)
Aux (what is this?) = +1.17v

Just keeping everyone up to date so we can figure this out.

And FYI, Prime has been going for 30 some odd minutes and has passed Self Test: Test 1-4, 1024k; Test 1-5 8k; Test 1-5, 10k; and is currently running test 2 of the 896k.

 

[Shoal07]

Error Log
Date - Time Source Description
Tuesday, April 26, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dd06e8, parameter3 87dd085c, parameter4 805c7478.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, April 27, 2005 Cdrom The device, \Device\CdRom0, has a bad block.
Wednesday, May 04, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dd06e8, parameter3 87dd085c, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 0000007a, parameter1 e2689c08, parameter2 c000009d, parameter3 bf978da6, parameter4 0db04860.
Thursday, May 05, 2005 System Error Error code 0000007a, parameter1 e2844918, parameter2 c000009d, parameter3 bf91a736, parameter4 50547860.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89983458, parameter3 899835cc, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d606e8, parameter3 87d6085c, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d296e8, parameter3 87d2985c, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 0000007a, parameter1 c05d3260, parameter2 c000009d, parameter3 ba64c7c8, parameter4 306ed860.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8999d520, parameter3 8999d694, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d8f6e8, parameter3 87d8f85c, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 00000077, parameter1 c000009d, parameter2 c000009d, parameter3 00000000, parameter4 00a9a000.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8996c810, parameter3 8996c984, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 00000077, parameter1 c000009d, parameter2 c000009d, parameter3 00000000, parameter4 00aa1000.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dea6e8, parameter3 87dea85c, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 0000007a, parameter1 e212fc08, parameter2 c000009d, parameter3 bf978da6, parameter4 764a8860.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 896c0da0, parameter3 896c0f14, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8995fda0, parameter3 8995ff14, parameter4 805c7478.
Thursday, May 05, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89816738, parameter3 898168ac, parameter4 805c7478.
Saturday, May 07, 2005 System Error Error code 00000077, parameter1 c000009d, parameter2 c000009d, parameter3 00000000, parameter4 009e1000.
Saturday, May 07, 2005 Dhcp Your computer has lost the lease to its IP address 192.168.100.10 on the Network Card with network address 000129F587A2.
Sunday, May 08, 2005 System Error Error code 00000077, parameter1 c000009d, parameter2 c000009d, parameter3 00000000, parameter4 00a43000.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89708020, parameter3 89708194, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8982cc60, parameter3 8982cdd4, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 00000077, parameter1 c000009d, parameter2 c000009d, parameter3 00000000, parameter4 00bf4000.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87cb4cf8, parameter3 87cb4e6c, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 899c8d78, parameter3 899c8eec, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87cec6e8, parameter3 87cec85c, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 00000077, parameter1 c000009d, parameter2 c000009d, parameter3 00000000, parameter4 00ac9000.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d176e8, parameter3 87d1785c, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 898126d0, parameter3 89812844, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89688408, parameter3 8968857c, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dcb6e8, parameter3 87dcb85c, parameter4 805c7478.
Sunday, May 08, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89663980, parameter3 89663af4, parameter4 805c7478.
Tuesday, May 10, 2005 Dhcp Your computer has lost the lease to its IP address 192.168.100.10 on the Network Card with network address 000129F587A2.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89976578, parameter3 899766ec, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dfe6e8, parameter3 87dfe85c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87e726e8, parameter3 87e7285c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87e116e8, parameter3 87e1185c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87cbe020, parameter3 87cbe194, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d656e8, parameter3 87d6585c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 88078638, parameter3 880787ac, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dbc6e8, parameter3 87dbc85c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87e526e8, parameter3 87e5285c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dc36e8, parameter3 87dc385c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 899b3610, parameter3 899b3784, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dcf6e8, parameter3 87dcf85c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d9e6e8, parameter3 87d9e85c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 899a5c78, parameter3 899a5dec, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87de06e8, parameter3 87de085c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 872cdda0, parameter3 872cdf14, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87e3f6e8, parameter3 87e3f85c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89977428, parameter3 8997759c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d8b6e8, parameter3 87d8b85c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89812140, parameter3 898122b4, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dbc6e8, parameter3 87dbc85c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 896bd620, parameter3 896bd794, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 0000007a, parameter1 e21048c8, parameter2 c000009d, parameter3 bf9109df, parameter4 6a475860.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87cd16e8, parameter3 87cd185c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87da06e8, parameter3 87da085c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 897e7da0, parameter3 897e7f14, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 0000007a, parameter1 e20fac08, parameter2 c000009d, parameter3 bf978da6, parameter4 1c7f7860.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 885c2548, parameter3 885c26bc, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8983b138, parameter3 8983b2ac, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 88109638, parameter3 881097ac, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87de26e8, parameter3 87de285c, parameter4 805c7478.
Friday, May 13, 2005 System Error Error code 0000007a, parameter1 c05d3260, parameter2 c000009d, parameter3 ba64c7c8, parameter4 60d6d860.
Saturday, May 14, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dbe6e8, parameter3 87dbe85c, parameter4 805c7478.
Saturday, May 14, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d9e6e8, parameter3 87d9e85c, parameter4 805c7478.
Saturday, May 14, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d9e6e8, parameter3 87d9e85c, parameter4 805c7478.
Saturday, May 14, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89961da0, parameter3 89961f14, parameter4 805c7478.
Saturday, May 14, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87ca8c00, parameter3 87ca8d74, parameter4 805c7478.
Saturday, May 14, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 897541c0, parameter3 89754334, parameter4 805c7478.
Tuesday, May 17, 2005 Dhcp The IP address lease 24.255.119.42 for the Network Card with network address 000129F587A2 has been denied by the DHCP server 192.168.1.1 (The DHCP Server sent a DHCPNACK message).
Tuesday, May 17, 2005 DCOM DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B 726-00C04FB926AF}
Tuesday, May 17, 2005 DCOM DCOM got error "%1084" attempting to start the service netman with arguments "" in order to run the server: {BA126AE5-2166-11D1-B 1D0-00805FC1270E}
Tuesday, May 17, 2005 Service Control Manager The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error: A device attached to the system is not functioning.
Tuesday, May 17, 2005 Service Control Manager The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error: A device attached to the system is not functioning.
Tuesday, May 17, 2005 Service Control Manager The TCP/IP NetBIOS Helper service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning.
Tuesday, May 17, 2005 Service Control Manager The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error: A device attached to the system is not functioning.
Tuesday, May 17, 2005 Service Control Manager The following boot-start or system-start driver(s) failed to load: AFD Fips IPSec MRxSmb Ne tBIOS NetBT Processor RasAc d Rdbss SAVRT SAVRTPEL SYM TDI Tcpip
Tuesday, May 17, 2005 DCOM DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B 726-00C04FB926AF}
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89747378, parameter3 897474ec, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 896fbda0, parameter3 896fbf14, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87e076e8, parameter3 87e0785c, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87e306e8, parameter3 87e3085c, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89943368, parameter3 899434dc, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8972f0c0, parameter3 8972f234, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d6a6e8, parameter3 87d6a85c, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8981b7f0, parameter3 8981b964, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87dbc6e8, parameter3 87dbc85c, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d086e8, parameter3 87d0885c, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 872b1020, parameter3 872b1194, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 880d6790, parameter3 880d6904, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87da56e8, parameter3 87da585c, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87cfe6e8, parameter3 87cfe85c, parameter4 805c7478.
Tuesday, May 17, 2005 System Error Error code 0000007a, parameter1 e20d3c08, parameter2 c000009d, parameter3 bf978da6, parameter4 7fcca860.
Tuesday, May 17, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 8980b020, parameter3 8980b194, parameter4 805c7478.
Wednesday, May 18, 2005 DCOM DCOM got error "%1084" attempting to start the service netman with arguments "" in order to run the server: {BA126AE5-2166-11D1-B 1D0-00805FC1270E}
Wednesday, May 18, 2005 DCOM DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B 726-00C04FB926AF}
Wednesday, May 18, 2005 Service Control Manager The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error: A device attached to the system is not functioning.
Wednesday, May 18, 2005 Service Control Manager The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error: A device attached to the system is not functioning.
Wednesday, May 18, 2005 Service Control Manager The TCP/IP NetBIOS Helper service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning.
Wednesday, May 18, 2005 Service Control Manager The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error: A device attached to the system is not functioning.
Wednesday, May 18, 2005 Service Control Manager The following boot-start or system-start driver(s) failed to load: AFD Fips IPSec MRxSmb Ne tBIOS NetBT Processor RasAc d Rdbss SAVRT SAVRTPEL SYM TDI Tcpip
Wednesday, May 18, 2005 DCOM DCOM got error "%1084" attempting to start the service netman with arguments "" in order to run the server: {BA126AE5-2166-11D1-B 1D0-00805FC1270E}
Wednesday, May 18, 2005 DCOM DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B 726-00C04FB926AF}
Wednesday, May 18, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d5d6e8, parameter3 87d5d85c, parameter4 805c7478.
Wednesday, May 18, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 89868210, parameter3 89868384, parameter4 805c7478.
Wednesday, May 18, 2005 System Error Error code 0000007a, parameter1 e223e8f8, parameter2 c000009d, parameter3 bf91640e, parameter4 20f25860.
Thursday, May 19, 2005 System Error Error code 00000077, parameter1 c000009d, parameter2 c000009d, parameter3 00000000, parameter4 0096d000.
Thursday, May 19, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87df56e8, parameter3 87df585c, parameter4 805c7478.
Thursday, May 19, 2005 System Error Error code 000000f4, parameter1 00000003, parameter2 87d5c6e8, parameter3 87d5c85c, parameter4 805c7478.

It looks like the 000000f4 error seems to be the most occuring. Although, there are a few others...

 

[dclive]

Does this happen in safe mode?

 

[aGreenAgent]

The 0xf4 error occurs when a system process gets terminated.

From what that log appears to say, it could be 3 things.

You may have a dead network card. Take it out and see if it crashes after 2 hours still.

Your IDE port or the software for it is bad.

Your DVD drive is bad. If the network card doesn't fix it, try putting in a different CD ROM drive.

 

[daveybrat]

Please set your ram to 2T timing instead of 1T and see how it runs.

 

[Chosonman]

You haven't done to very first tip any trouble shooting expert will tell you... sTArt fRoM thE BeginniNG..

You have so much stufff loaded on that computer if you try every test people mention you'll be doin this for years.
Start from the beginning.
Use 1 graphics card 1 Hard Drive and full memory and go from there.
Then start adding pieces one at a time.

Your problem seems more logical than random. (judging by your statements)
Random problems are can be heat related or memory related. A logical problem is related to operation such as incorrect bios settings, faulty drivers etc...

And you might want to reinstall windows if you can't find anything else. That's almost guarranteed to eliminate any logical errors that might result from the operating system not being configured correctly.

My first intuition tells me it's related to either the hard drive configuration or the SLI that's causing the problem

 

[Shoal07]

UPDATE

So, I decided to remove the Raid 5 (3 drives) and try 1 drive, take the system back down to basics. Well, the first drive I tried to format to NTFS to get ready to install windows would not pass 46% formatted, 3x in a row. I am now on the second drive and it made it all the way through.

The jury is still out, I still have to get windows up and running and get it past two hours, but it appears that my issues were due to a bad HD.

Also, thanks to all the great people racking their brains on the forums at Guru3d, Anandtech, PCQandA, Bleedinedge (OCZ) and DFI-Street!

Thoughts?