Computer just randomly turns off and reboots

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

---

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?

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.

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
---------

---

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???

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.

Don't give up yet. When I was trying to optimize my system on my motherboard change, I had enabled every option in the bios to get every bit of speed possible for those benchmarks. Everything seemed to work fine for a week but then I started getting those random reboots every now and then. I then disabled the use turbo mode settings for my ram. After that, I've had no lockups. In all honesty, I could not see the difference in my computer. The only thing that noticed was some of the benchmarks.

I would try lowering some of your bios settings to something that is less aggressive to see if it clears up your problems on your current config.

Good luck.

Very good thread JustWhitman. I just saw that you responded in my thread about the EXACT same issue. System just shuts down on its own and reboots. Lets see here. What do we have in common with our systems? Looks like we both have a liteon burner. And my system has shutdown a couple of times while I was running nero just before i began to burn. Who knows:confused: :confused:

I have been having the same problem the past few days also. I recently put together my system and have had random reboots. I switched the setting in windows and now i get the BSOD. Sometimes it is the IRQL error, other times it is just a memory dump referencing ntsokrnl.exe or ntfs.sys. I have formatted at least 4 times trying different things in the bios to not have any of my devices share the same irq. I can't manage to get the video card to be on it's own irq, but everything else is. The video card shares irq 11 with the usb bus controller. I think it might have to do with the VIA chipset, but that is just a guess. I usually get the error when i am trying to play a game or run 3dmark. I don't think the problem is hardware related because everything in my system is brand new. I am running win2k bytheway.

I think it is hardware related though, because I reformatted as well, and you said you did. And if that didnt fix anything...then it has to more than likely be a piece of hardware. I've been doing some testing with my RAM and mobo, and I think I have a bad stick of RAM, plus the DIMM socket the bad RAM was in appears to be bad as well :(

All of my hardware is on diffrent IRQ's, and I still get the IRQL not less or equal to error, so I don't think it's really an IRQ issuse. The error relates more to the area of "the computer is trying to access something in the pagefile, the either isnt there or is too high". I've also gotten a few other errors, one of them being an 0x50 stop code, but when I go to debug it says "Unknown bugcheck code (10000050)
Unknown bugcheck description" So I did a search on MS's support site, and this one says the following:

Quote:

---

These errors may be caused by one or more of the following:
Hardware failure (memory, processor, or motherboard).
Anti-virus software that is running on your computer.
Drivers installed by third-party software.

---

I've already E-Mailed EpoX and Samsung, but I'm waiting on them to get back to me. I've read quite a few articles on the error now, and it seems almost everyone getting the error either had bad RAM or a bad DIMM(or RIMM, SIMM whatever the case may be) socket. I know for sure my RAM will get replaced, lets just hope EPoX lets me RMA my mobo. Whatever the case I'll keep you all filled in and let you know if the new mobo and RAM will fix my problem ;)

Quote:

---

Originally posted by JustWhitman

All of my hardware is on diffrent IRQ's, and I still get the IRQL not less or equal to error, so I don't think it's really an IRQ issuse. The error relates more to the area of "the computer is trying to access something in the pagefile, the either isnt there or is too high". I've also gotten a few other errors, one of them being an 0x50 stop code, but when I go to debug it says "Unknown bugcheck code (10000050)

---

I usually find the IRQL error to be a driver issue. But recently I was getting crashes on a computer I've been setting up. Running memtest86 I found out one of the RIMM slots is bad. Neither chip gives me errors in one slot. Both give tons of errors in the other slot. Running with the single chip in the last day I've yet to have a blue screen or reboot. I just have to wait for Newegg to do the RMA.

Eric