Repeated Crashes

[Guest]

Hello:

I'm having an issue with my computer in which it keeps restarting. It
started a few days ago and so as a precaution I backed up all my files and
folders, and used the restore CDs to set it at factory settings. I figured
once everything was erased that whatever the problem was would be fixed
and/or gone. I ran Norton to make sure it wasn't a virus, I ran Windows
Update and redownloaded all the updates including SP1 and SP2, and updated
all my drives. It still crashes. SP2 took quite a few times to get it to
totally installed because the computer kept crashing.

This is what happens:
I'm on the computer.
It blinks and begins to restart.
Welcome screen.
I sign in.
It blinks and restarts again.
Welcome screen.
I sign in.
It tells me that I just recovered from a serious error, a log has been
created, and a report being sent.
I check to see what's in the error log. Something about a minidump.
Different minidump file every time.
It's fine, and then we do the dance again.

One time I got a blue screen that said IRQL_NOT_LESS_OR_MORE and told me to
restart

Another time I got the screen that gave me the options of starting in safe
mode and all that. I did the "Last Good Configuration" one. Crashed right
after.

I thought it might be the software, but it's all software I have been using.
Actually, since I used the restore CDs...I've only installed SBC YAHOO! DSL
with the wireless hub thing. I tried installing the other software I had
before, but I couldn't because it kept crashing.

The computer will be fine for a while and then it crashes again. I'm using
my laptop right now because the computer will probably crash before I hit
"post."

I don't know what to do...I've read through some other posts and some are
like mine, but the methods suggested didn't really work.

Thanks for your help in advance,
Kim.

 

[David Candy]

Note you specified a non existent message. Not More is very rare and it's IRQL_NOT_MORE_OR_EQUAL.

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
Parameters
The following parameters are displayed on the blue screen.
ParameterDescription
1Memory referenced
2IRQL at time of reference
30: Read
1: Write
4Address which referenced memory


Cause
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Microsoft® Windows®, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Resolving the Problem
If a kernel debugger is available, obtain a stack trace.
To resolve an error caused by a faulty device driver, system service, or BIOS
Restart your computer.
Press F8 at the character-based menu that displays the operating system choices.
Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool
Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
Try disabling memory caching of the BIOS.
Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner’s manual for your computer.
Make sure the latest Service Pack is installed.
If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/slave/stand-alone setting. Try removing all IDE devices except for hard disks.
If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed on the Microsoft Windows Hardware Compatibility List (HCL).
Here is a debugging example:
kd> .bugcheck [Lists bugcheck data.]
Bugcheck code 0000000a
Arguments 00000000 0000001c 00000000 00000000

kd> kb [Lists the stack trace.]
ChildEBP RetAddr Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> kv [Lists the trap frames.]
ChildEBP RetAddr Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint (FPO: [0,0,0])
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256 (FPO: [0,0] TrapFrame @ 8013eee8)
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> .trap 8013eee8 [Gets the registers for the trap frame at the time of the fault.]
eax=dec80201 ebx=ffdff420 ecx=8013c71c edx=000003f8 esi=00000000 edi=87038e10
eip=00000000 esp=8013ef5c ebp=8013ef64 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ErrCode = 00000000
00000000 ??????????????? [The current instruction pointer is NULL.]

kd> kb [Gives the stack trace before the fault.]
ChildEBP RetAddr Args to Child
8013ef68 fe551aa1 ff690268 00000002 fe5620d2 NT!_DbgBreakPoint
8013ef74 fe5620d2 fe5620da ff690268 80404690
NDIS!_EthFilterIndicateReceiveComplete+0x31
8013ef64 00000246 fe551aa1 ff690268 00000002 elnkii!_ElnkiiRcvInterruptDpc+0x1d0

Comments
Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.

 

[Jack C.]

On Sat, 11 Jun 2005 10:26:04 -0700, Kim <[email protected]>
wrote:

Kim:

Sounds like a simple heat problem to me. Could be the CPU fan is dead or
dying. Open up the left side of your computer and look inside to be sure
that all the fans you see are turning normally. Also, if you see a lot
of dust and dirt it may just need a good cleaning - canned air works
well to blow out the dust. You could try running it with the side open
and even have a fan blowing air into the case to help with the cooling.
Other than that it could be just about anything including (in order of
most likely to least likely) something loose, a bad motherboard, power
supply, memory, CPU, video or modem. If you're not mechanically inclined
you may have to take it to a pro for service. Good luck.

Jack C.