Oh, watch for accidental overclocking of the memory, by spd is the setting you want unless you know what the settings actually mean.

Make sure currently though that your CAS rating is the same as the mobo cas setting, and the others. Tweaking that stuff could definitely cause issues without any question.
Back to top

hmmm...i do hear audio artifacts, pops and crackles, when the reboots happen. I wonder if the first place i ever had this computer in fried it. but then again my roomtes computer never had any problems.

im interested in this route of thinking but also suspicous of it. I mean theres no tellign how much damage coudl have been done if bad power was the case. there arent any other signs.

confusing.

well ill digest this stuff.
Back to top

" watch for accidental overclocking of the memory, by spd is the setting you want unless you know what the settings actually mean.

Make sure currently though that your CAS rating is the same as the mobo cas setting, and the others. Tweaking that stuff could definitely cause issues without any question"

im definatley lost on this one. not familiar with makign any changes to the CPU or overclocking. all i knwo is - dotn do it.

how can i check/change these thigns?
Back to top

here are some more errors:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/12/2005
Time: 7:42:20 PM
User: N/A
Computer: DS2-B6289F04A3F
Description:
Error code 10000050, parameter1 80000004, parameter2 00000001, parameter3 8054ae34, parameter4 00000000.

For more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 38 30 eters 80
0030: 30 30 30 30 30 34 2c 20 000004,
0038: 30 30 30 30 30 30 30 31 00000001
0040: 2c 20 38 30 35 34 61 65 , 8054ae
0048: 33 34 2c 20 30 30 30 30 34, 0000
0050: 30 30 30 30 0000

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 10/12/2005
Time: 7:41:49 PM
User: N/A
Computer: DS2-B6289F04A3F
Description:
The Human Interface Device Access service terminated with the following error:
The specified module could not be found.

For more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 10/12/2005
Time: 7:41:49 PM
User: N/A
Computer: DS2-B6289F04A3F
Description:
The Koli2dvwapdp service failed to start due to the following error:
The filename, directory name, or volume label syntax is incorrect.

For more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp.






BCCode : 10000050 BCP1 : 80000004 BCP2 : 00000001 BCP3 : 8054AE34
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

C:\DOCUME~1\Blabula\LOCALS~1\Temp\WERe284.dir00\Mini101205-02.dmp
C:\DOCUME~1\Blabula\LOCALS~1\Temp\WERe284.dir00\sysdata.xml
Back to top

Great, now we know it's a driver or hardware error. That's literally what the translation for 1003, 7000 is. It's possible to figure out exactly what is failing, but it takes some time. Notice that it's EITHER a driver or a hardware error.

You have a driver or hardware error. These types of error codes can be maddening, they are incredibly vague sometimes, other times they pinpoint the issue virtually instantly.

If I were in your shoes, I'd download the latest drivers for all my hardware, including the motherboard drivers, uninstall all the drivers, one by one, and reinstall them with fresh versions, uptodate, not off the cds that came with the mobo or pci or video cards.

But even that's not guaranteed, if it's something physically wrong with one of these components, that wouldn't solve the issue.

No wonder this has never gotten resolved correctly, it's an extremely difficult case.
Back to top

Download all the latest drivers- wouldnt I then just install them over the old ones rather than uninstalling old, installign new? Is that what you mean?

Should I keep postign error codes and warning codes here hoping for something more specific?
Back to top

Yes, sorry, that is fine, update all the drivers, I think realistically what you need to do now is start whittling away at the possible sources.

After installing all the upgraded drivers, we can eliminate bad or corrupted drivers from the mix.

Once you've updated your mobo drivers, your printer scanner drivers, all your pci/video card drivers, we can see what's happening. Post any new error codes.

And by all means go get the UPS unit, we need to eliminate bad or faulty power from the equation too.

If the problems persist, I'd also reflash the motherboard bios, without a floppy drive however that's tricky, unless the mobo manufacturer has a cd rom version. You might want to borrow a floppy drive from someone for that step, just open the box up and attache it somewhere you can access it.

Although you may have a feature that supports flashing the bios through windows, but have your tech friend do that, if the bios is flashed incorrectly the mobo is toast, complete toast, it's not fixable in most cases.

If none of these steps work, you're going to need to pull out all the pci cards, borrow a known good video card, unplug the scanners/printers, then start running the machine with only the video card, see if it's stable, if it is, add each piece of hardware, one by one, until you locate the real problem hardware. If it still fails with only a new video card installed, either windows is corrupted, or the mobo is bad.
Back to top

Ah- the BIOS gives very bizzare readings for the power supply. Grossly below or above the norm. After replacing the power supply (for the third time) if these readigns are still present I speculate that the motherboard is indeed defective.
Back to top

Yes indeed, or you are having very large voltage/current fluctuations.

Have you tried resetting the bios to failsafe defaults, that makes sure nothing is overclocked, it will run quite slowly, but you can turn back up the FSB front side bus speed once you try booting to see if you got stability.

However, if you are seeing these voltage fluctuations live in the bios, that's obviously a very big problem, and would lead to serious system instability.

Again, it's very unfortunate that guy took your antec, he should give it back to you, that's not very nice, and it's not very ethical, but the computer gods will make him suffer for that somehow, some way.

Get the UPS unit before anything else too, even if you end up replacing that mobo, the last thing you want is to fry the next one with the same power issues.
Back to top