2 things to try:
A new more powerful PSU and a new more powerful HSF.
That might solve your problem.
Printable View
2 things to try:
A new more powerful PSU and a new more powerful HSF.
That might solve your problem.
Does your BIOS screen report voltages? Are you getting 12 and 5v at the motherboard ? (Or just 11.5 and 4.7 or something) - it Must be a power or heat problem... Is your graphics card adequately cooled? Not too much dust everywhere?
moog
JustWhitman:
Why don't you try backing off the FSB? Is your memory OC'd as well? Try 133/166 or 100/166 and see if it still fails. I have experienced the same symptoms when the VDIMM was too low for the OC.
Computer Idles at 31*C and under full load it peaks at 45*C, so I dont think it's heat related. But it's been almost 3 days and still no random reboot yet, and like I said, only thing I changed was the automtic reboot. Kind of odd if all turning that off does is prevent the comp from restarting when a failure occurs, unless tuck2040 is incorrect in his statement.Quote:
Originally posted by PfcJs
This makes it sound like a heat related issue. Do you have any motherboard monitoring software to monitor the fan speeds and CPU temperature? It could be things overheating due to a CPU fan not working as well as it should.
PCs are great until they go wrong. Diagnosing the problem can be a definate chore!
Good luck.
A more powerful PSU!?! so 430watts isnt enough? :eek: :p I dont think it has anything to do with my heatsink either, my temps are fine as I stated above.Quote:
Originally posted by richardginn
2 things to try:
A new more powerful PSU and a new more powerful HSF.
That might solve your problem.
My 12v rail stays at about 11.91v and my 5v stays at around 4.95v. As far as my video card, it's on stock cooling. Like I've said many times, everything has been running fine for around 6 months, thats why I dont think this is a cooling issue at all. I've actually backed off my oC some since I first got this PC, so it's cooler now that it used to be. And for dust, I clean out the dust bunnies about once a month.Quote:
Originally posted by moog
Does your BIOS screen report voltages? Are you getting 12 and 5v at the motherboard ? (Or just 11.5 and 4.7 or something) - it Must be a power or heat problem... Is your graphics card adequately cooled? Not too much dust everywhere?
moog
Well, I put everything back to default for a little while, and it still did it. I even tried raising the Vcore and Vdimm while at default settings just to make sure they were definitly getting enough juice (I did this after the inital random reboot with default settings) and even after that it rebooted again. For now I've put my comp back at 150MHz FSB, and everything is still running smoothly.Quote:
Originally posted by SCUMBAG
JustWhitman:
Why don't you try backing off the FSB? Is your memory OC'd as well? Try 133/166 or 100/166 and see if it still fails. I have experienced the same symptoms when the VDIMM was too low for the OC.
But still, the only thing I have changed is the "automatic reboot setting" its just really odd.
im having the same prob with one of my pc's, but it doesnt always reboot, most of the time it just shuts off but you can still hear the fans inside spinning and the reset button and power button dont do anything, the onlyway to get it to reboot is to unplug it. i was in the bios and you can read the temp and voltage and stuff there and where it reads the 12v at was only reading about 9 then all of a sudden it shut off while in the bios, guess im gonna try to replace the power supply and hope its that easy
Yea that definitly sounds like your PSU is having issues, 9v on your 12v rail is VERY low. When mine shuts off though it's just like it's rebooting w/o going through the shutdown process, or kind of like I hit the reset button or something. Luckily it's been smooth the past few days, but I'm just gonna have to wait it out and see if my luck keeps up :DQuote:
Originally posted by new guy
im having the same prob with one of my pc's, but it doesnt always reboot, most of the time it just shuts off but you can still hear the fans inside spinning and the reset button and power button dont do anything, the onlyway to get it to reboot is to unplug it. i was in the bios and you can read the temp and voltage and stuff there and where it reads the 12v at was only reading about 9 then all of a sudden it shut off while in the bios, guess im gonna try to replace the power supply and hope its that easy
thanks
Could it be you were experiencing some kind of power sag or surge on your electrical lines? Was there by chance any kind of electrical storm in your vicinity that could have caused that?Quote:
Originally posted by JustWhitman
When mine shuts off though it's just like it's rebooting w/o going through the shutdown process, or kind of like I hit the reset button or something. Luckily it's been smooth the past few days, but I'm just gonna have to wait it out and see if my luck keeps up :D
I used to suffer from spontaneous reboots when I moved out into a new subdivision. As it was new, our hydro company was messing around with the power in our area. In the end, I got fed up and bought a UPS. I never have had a reboot since.
Ok, Today i actually got a BSOD and I haven't had one since I've been running XP, so I'm guessing that this relates to my random reboots? The BSOD was a "DRIVER_IRQL_NOT_LESS_OR_EQUAL" atfer reading around I've found that this signifies that the system attempted to access pageable memory at a process IRQL that was too high. What that means though I dont know. Also from reading around I've seen people sugesting to check drivers, to also possilbe bad sticks of RAM.
http://www.tek-tips.com/gviewthread....779/qid/308429
Now, as far as drivers. All of the drivers in my system are WHQL certified (havent put the 40.41 detonators on my comp since i reinstalled XP), except for my monitor drivers. From reading that above thread though, I dont know where to start, heh. People were saying that their RAM, drivers, heat sink, were the cause of the problem. Any ideas?
I debugged the dump file that it gave me and heres what it comes up with.
Now, I'm a real newbie when it comes to debugging, so I dont understand what most/any of this means. But judging from some of stuff that comes up in there, am I simply having IRQ confilcts???Quote:
kd> !analyze -v
************************************************************ *******************
* *
* Bugcheck Analysis *
* *
************************************************************ *******************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pagable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000001, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 00000001, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000001
CURRENT_IRQL: 2
FAULTING_IP:
+1
00000001 ?? ???
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 804dce53 to 805266db
STACK_TEXT:
ba179864 804dce53 0000000a 00000001 00000002 nt!KeBugCheckEx+0x19
ba179880 815dd418 00000001 05ecc000 00000000 nt!KiTrap0E+0x2ad
WARNING: Frame IP not in any known module. Following frames may be wrong.
80ffe140 00000000 00000000 00000000 00000000 0x815dd418
FAILED_INSTRUCTION_ADDRESS:
+1
00000001 ?? ???
FOLLOWUP_IP:
nt!KiTrap0E+2ad
804dce53 ?? ???
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiTrap0E+2ad
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
STACK_COMMAND: kb
BUCKET_ID: 0xD1_BAD_IP_nt!KiTrap0E+2ad
Followup: MachineOwner
---------
You can check your IRQs by running System Information under Programs>Accessories>System Tools. Expand the Hardware Resources Tree and click on IRQs and see if you have any devices sharing the same interrupt.
Well, I guess thats not the problem then :( I think I'm gonna have to so start taking prats out one by one until it no longer happens. Only bad thing is it's not like it happend all the time.