Windows Forum·65,795 discussions

Blue screen stop error 0x0000000A

Locked

I have a user who is running NT 4.0 Workstation with SP4. He last rebooted the machine two weeks ago. He says that he has not installed any devices/drivers during that time, but did install software (which provides money management for stock market investing). He also upgrade his Disk Keeper Lite to a new version. Today he rebooted the machine and the following BSOD results:
0x0000000A (0x00000008, 0x0000001C, 0x00000000, 0x80116018)
IRQL_NOT_LESS_OR_EQUAL Address 80116018 has a base at 80100000 – ntoskrnl.exe

The nearest error to this that I could find in Technet’s knowledge base refers to a particular brand of virus protection software. The user is in fact not using that brand, but is using McAfee, and says that he has not updated it recently.

The winnt folder is on a FAT partition and I have copied a new ntoskrnl (from SP4), but this did not make a difference.

My questions are as follows?
1) Any ideas how to find out which driver is causing the havoc? Is ntoskrnl trying to access another d

Topic

Blue screen stop error 0x0000000A

In reply to Blue screen stop error 0x0000000A

Well, I can give you what microsoft says:
“This is a windows nt executive character-mode STOP message. It indicates an IRQL expected to be less or equal, which was not. The 4th parameter in the message parameter list is the memory addfress at whichthe fault happened [0x80100000]. The 2nd parameter shows the IRQL. If the IRQL was not equal to 2 [yours is 1C], then the attempt most likely came from the driver. Compare the memory address in the 4th parameter with the base address of the drivers in the driver table on the STOP screen to find the driver that is the problem. Note the 3rd parameter encodes read/write access (0=read, 1=write).” So, you know it is a read error. Thus, the stop screen should provide you with the comparison information to isolate the bad driver. Hope this helps. E-mail me if need be: lvachon@consultant.com Good luck

Blue screen stop error 0x0000000A

In reply to Blue screen stop error 0x0000000A

I did say that I had consulted technet …

Blue screen stop error 0x0000000A

In reply to Blue screen stop error 0x0000000A

I agree with the reasoning in the previous answer but would add that if you don’t have the driver list from the BSOD handy, that same information should be written to a file called memory.dmp (or sometimes user.dmp) in the c:\winnt directory.

Youcan extract the relevant information from this file using dumpexam.exe, a utility from the NT Server Resource Kit. That should point you in the right direction.

My gut feeling would be a problem with the Disk Keeper Lite, not because I know of aproblem with it but I tend to look first at any software that performs functions close to the hardware so I look first at utilities and hardware drivers.

Best wishes!

paul
Paul M. Wright, Jr. MCSE, CNE
McKay Technologies

Blue screen stop error 0x0000000A

In reply to Blue screen stop error 0x0000000A

Blue screen stop error 0x0000000A

In reply to Blue screen stop error 0x0000000A

Two clues hear point to hardware problems STOP 0x0a can indicate a rogue TCP/IP packet, but more likely a buggy device driver, system service or BIOS.
Second clue the parameter ?0x00000008, This error is almost always caused by hardware problems.
The NTOSKRNL.exe is almost never the problem, it just gets the blame as its responsible for the overall Kernel. My guess is that when he upgraded the Disk-keeper lite, he could not resist running it, and that is what caused the problem.
You do have a chance of trying the Last Known Good, hit the space bar as it boots, and then press L. However it may not be getting that far. If you have a backup, I would be ruthless and reformat, and reinstall NT on the machine.

Blue screen stop error 0x0000000A

In reply to Blue screen stop error 0x0000000A

I installed a second NT and discovered that the software hive (of the original NT) was giving an I/O error. I expanded the copy in the repair folder and copied it to the config folder and could at least get into NT and fix things from there. And yes, I think disk-keeper may have had something to do with it.

[Author]

Replies