New Build, Random Crash

P

Pyke

n00b
Joined
Dec 22, 2004
Messages
52
Built my new system a few weeks ago, and it has been very good to me. It crashed once about three days after I got it up and running, showing a BSOD for half a second then rebooting. It happened again today, two weeks after the first crash. No high demand programs were running, just Foobar and Firefox.
System is as follows:
AMD Athlon64 3500+ at stock clocking
MSI K8N Neo2 Platinum
Corsair XMS 4000Pro
XFX GeForce 6600GT AGP
Vantec 400W PSU
Running Windows XP SP2
Any ideas on what could be happening?
This is what the Computer Management/Event Log says about it:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf8113c3, 0xf64eb200, 0x00000000). A dump was saved in: F:\WINDOWS\Minidump\Mini021105-01.dmp.
Click to expand...
 
Many things came up and the new PC took a back seat. Ran Memtest 86 for three hours with no errors. Managed to get a pic of the BSOD for the one second it was on the screen this time.

Help!
 
You got some IRQ issues. Have you enabled Plug and Pray and the mobo BIOS?


What exactly is your configuration?
 
My life took another shit, sorry about the delay.
Just noticed that when I am browsing/using/deleting files on my secondary HDD (a 160GB WD Caviar) the screen will either dim or shut off for a second. Is this thing possessed or what?
Also the same BSOD's are occuring more frequently, sometimes only when I am browsing the web, no other programs running. Help!
 
Could be driver issues. Try uninstalling your video drivers and installing new ones. Also, if you have any memory shadowing options set in BIOS, disable them.
 
not sure if ur psu is capable of producing a constant flow is it a atx 2.0 if not check whether that card needs one.
 
you only have the dimming screen when accessing the seconday hard drive? check your jumpers, and make sure the ribbon cables are in securely, if you have sata drives, make sure that the sata cable is in properly. I'm leaning towards the jumpers though. If the slave is set for master as well as the master set for master, that could explain the issues while accessing the drive.

as for the blue screen, i would try reseating everything including the CPU, update all the drives and makre sure you have all the windows updates. also, check temperatures. if the room you are in is abnormally hot, that may cause randam failure. Maybe try taking the case panel off.

hope that helps. good luck
 
Tiny said:
Could be driver issues. Try uninstalling your video drivers and installing new ones. Also, if you have any memory shadowing options set in BIOS, disable them.
Click to expand...
Running the new NVidia 71.84 drivers, still have the same problem.
visualeyes said:
not sure if ur psu is capable of producing a constant flow is it a atx 2.0 if not check whether that card needs one.
Click to expand...
PSU is brand new. It's fine.
S[H]ady said:
check your jumpers, and make sure the ribbon cables are in securely, if you have sata drives, make sure that the sata cable is in properly. I'm leaning towards the jumpers though
Click to expand...
My boot disk is a WD Raptor SATA running as a Master, configured on the jumpers. I have a WD Caviar IDE as slave, no jumpers, configured throught the IDE cable placement.
S[H]ady said:
also, check temperatures. if the room you are in is abnormally hot, that may cause randam failure. Maybe try taking the case panel off.
Click to expand...
Case temps are fine. Proc. idles at 37, case temps are around 24-27.
 
You must log in or register to reply here.
Back
Top