Another 0x0D1 Thread

[Guest]

I am completely stumped on this one . . .
My personal PC is acting like i have never seen a PC act before.

I will say now that the problem is a completely RANDOM occurrence and as
such I have no idea how to diagnose it.

Issue at hand:
PC, Win XP SP2, stops on boot up, blue screen with error code 0x000000D1
(Driver IRQL not less or equal). Upon examination of the minidump, The
exception code field does not exist. Heres the rest of the output:

MajorVersion 0000000f
MinorVersion 00000a28
Directorytablebase 073203c0
PfnDataBase 81800000
PsLoadedModuleList 8055c700
PsActiveProcessHead 80562818
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 100000d1
BugCheckParameter1 00000081
" "2 00000002
" "3 00000000
" "4 86ddb168
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff

Triage_dump 32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00003fff
DricerListOffset 00006c10
DriverCount 0000008b
StringPoolOffset 00009558
StringPoolSize 00001330
DrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack eb46f000
DebuggerDataOffset 00006980
DebuggerDataSize 00000290
DataBlocksOffset 0000a888
DataBlocksCount 00000004

Windows XP Kernel Verison 2600 (Service Pack 2) MP (2 Procs) Free x86
compatible

Kernel base = 0x804d7000 PsLoadedModuleList = 0x0855c700
Debug session time: Snu Oct 29 09:31:08 2006
System Uptime: 0 days 0:00:51

start end module name
804d7000 806e2000 nt Checksum: 001F534D Timestamp: Tue Apr
11 17:27:45 2006

Unloaded modules:
f1285000 f1290000 imapi.sys Timestamp: unavailable (00000000)
f12a5000 f12ae000 processor.sys Timestamp: unavailable (00000000)
f25c9000 f25cd000 kbdhid.sys Timestamp: unavailable (00000000)
f1566000 f156b000 Cdaudio.SYS Timestamp: unavailable (00000000)
f25cd000 f25d0000 Sfloppy.SYS Timestamp: unavailable (00000000)
f156e000 f1573000 Flpydisk.SYS Timestamp: unavailable (00000000)
f1576000 f157d000 Fdc.SYS Timestamp: unavailable (00000000)

Finished dump check


As far as i can tell, no specific file is provided or code to find such file
as faulty.

The reason i say this problem is random is that it mostly is. It occurs
ALMOST every startup and randomly while the computer is running (for long
periods of time). Sometimes, the computer can be started if I choose to
enable debugging mode or even if i just choose "enable boot logging" when
starting the computer. Nothing in particular seems to set it off while the
computer is running. Nothing stands out in the Event Viewer either. Like I
said, I'm Stumped. I have looked online for more resources about this error
but all of them apply to something else and have different bugcheckcodes 2 3
and 4.

Any help would be greatly appreciated.
-CHStech

 

[Gerry Cornell]

See here:
http://aumha.org/win5/kbestop.htm

Have you made any changes to RAM memory.

For the pagefile try setting no pagefile and then shutdown.
Reboot and recreate the pagefile.

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties. Hardware,
Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What drivers
are listed as unsigned? Disregard those which are not checked.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~