• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Comp Randomly Rebooting

Y

(yaenvros

n00b
Joined
Sep 29, 2003
Messages
19
Notes:
Comp stats:
Gigabyte GA-965P-DS3 LGA 775 Intel P965 Express ATX
Intel Core 2 Duo 6400
2x1024mb RAM
nVidia GF800 GTS
Western Digital 160gb SATA
Lite-on DVD-RW

Random crashes seem to occur more often when I am:
1. Watching a video, either online or on my harddrive
2. Playing World of Warcraft (may be any game, but that's the one I play)
3. Downloading something from the internet
4. Transferring files over the network
5. Installing software
6. Listening to a music file

However, the computer does crash at other times. It crashes during the boot process itself, and it sometimes crashes overnight while idling. Last night however I did a disk defrag and the computer didn't crash for 12 hours.

I turned off automatic restart in System->Advanced, but no BSOD appears.

After most crashes, the computer attempts to restart again. Sometimes it doesn't, and I have to wait about 1-2min before the power button works.

I have tried running the computer with only 1 stick of ram. With only either stick however, the computer still restarts randomly.

With a single stick of ram in the dimm slot closest to the CPU, I hear one long beep and one short beep. According to my mobo manual, that means there is either a memory or mobo problem.

With a single stick of ram in the 3rd dimm slot from the CPU, I hear a series of long beeps, which means there is a memory problem.

This problem is giving me a headache, and I can't even pinpoint the problematic part (it may even be software related for all I know). Any suggestions?
 
First, check your event viewer (right click My computer -> Manage -> event viewer)
and see if there are any warnings or errors being logged (either on the application end or system) at the time it crashes.

Second, have you tried running some memory tests? Such as memtest86?
If not, try that.

Also, what PSU are you using.
Might be a power supply related issue.
 
PSU: XClio Goodpower 500W

This is the only red X I find in the event viewer: Faulting application explorer.exe, version 6.0.2900.2180, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00018fea.
 
last time something like this happened to me it was my PSU. It's one of the easiest and one of the cheaper components to replace, so I'd start there.
 
XP Media Edition. That error comes up when I log back in into Windows after a crash. It forces me to end the explorer.exe process and restart it. However, the error doesn't always happen. Sometimes all I get is Active Desktop Recovery, or sometimes no error on the screen at all.

I'll try memtest86 and replacing my PSU; will update.
 
(yaenvros said:
PSU: XClio Goodpower 500W

This is the only red X I find in the event viewer: Faulting application explorer.exe, version 6.0.2900.2180, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00018fea.
Click to expand...



umm .. ya .. get a new PSU .. right away ... NOW!
 
o_O

Blocatan, we're not even 100% sure if it is indeed the PSU's fault.
No use replacing any parts until we figure out the exact location of the problem.

Well, try the memtest, and also if you can borrow a spare psu or something - you can try that out as well.
 
enyceexdanny said:
o_O

Blocatan, we're not even 100% sure if it is indeed the PSU's fault.
No use replacing any parts until we figure out the exact location of the problem.

Well, try the memtest, and also if you can borrow a spare psu or something - you can try that out as well.
Click to expand...

Well .. that is true .. But the comment i made was based on the Brand and model of PSU .. that thing (IMO) needs to go whether or not it is the cause of this particualr issue ..
 
You must log in or register to reply here.
Back
Top