Minidump help =/

[connell_2k7]

I've been getting the error: Driver_IRQL_not_less_or_equal. Attached some minidumps.

Hope someone can help

 

[Matthew DeCarlo]

Minidump 040908-01:

BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : ntoskrnl.exe ( nt!NtQueryValueKey+2be )
---------------------------------------------------------------------------
Minidump 041008-01:

BugCheck 1000008E, {c0000005, 2, bafefc40, 0}
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
---------------------------------------------------------------------------
Minidump 041008-02:

BugCheck 1000008E, {c0000005, 2, b5c33c40, 0}
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
---------------------------------------------------------------------------
Minidump 041008-04:

BugCheck 1000008E, {c0000005, 2, b5bbb720, 0}
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
---------------------------------------------------------------------------
Minidump 041108-01:

BugCheck 1000008E, {c0000005, 2, b6384c40, 0}
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
---------------------------------------------------------------------------

Test your RAM with Memtest86 for a minimum of 7 passes and test your HDD with one of the utilities listed here.

 

[connell_2k7]

Zeno, any idea what the above minidumps meant? Im a bit of a dunce with computers

Both tests have came back clean as a whistle. 3 more minidumps....

 

[Matthew DeCarlo]

Minidump 041208-01:

BugCheck 1000008E, {c0000005, 8056b279, b5baec38, 0}
Probably caused by : ntoskrnl.exe ( nt!NtQueryValueKey+2c7 )
--------------------------------------------------------------------------------
Minidump 041208-02:

BugCheck 100000D1, {8d0618e4, ff, 0, 8d0618e4}
Probably caused by : ntoskrnl.exe ( nt!CmpLockRegistry+27 )
--------------------------------------------------------------------------------
Minidump 041208-03:

BugCheck 10000050, {e195e000, 1, bf90788b, 1}
Probably caused by : win32k.sys ( win32k!vTransparentCopyS24D32+77 )
--------------------------------------------------------------------------------

There is either interference or corruption with ntoskrnl.exe. Here is Wikipedia's description of the file:

ntoskrnl.exe (and ntkrnlpa.exe on systems with Physical Address Extension support) is the kernel image for the family of Microsoft Windows NT operating systems. It provides the Microkernel and Executive layers of the Windows NT kernel space, and is responsible for various system services such as hardware virtualisation, process and memory management, etc., thus making it a fundamental part of the system. It contains the Cache Manager, the Executive, the Kernel, the Security Reference Monitor, the Memory Manager, and the Scheduler, among other things.

Well, unless there is some hardware at fault (which is very possible) running a repair installation or reinstalling Windows all together might do the trick for a software related conflict.

 

[Route44]

With the 0x8E and especially 0x50 errors, plus the citing of core Window drivers, I would definitely suspect corrupted memory.

Run MemTest of your RAM for a minimum of 7 passes. But go with what Z has suggested as well.

 

[Matthew DeCarlo]

Aye, it'd seem that way to me as well, Route44, however:

Both tests have came back clean as a whistle. 3 more minidumps...

Any idea what it might be other than RAM? Think Memtest86 just missed the errors?

 

[Route44]

My question is how long the test ran. Though I think you are on to something with a Windows repair. But 8E and 50 errors are usually hardware issues especially the 8E.

Possible need for a harddrive diagnostics?

 

[Matthew DeCarlo]

My question is how long the test ran.

Something I had actually just begun to question myself, as there was only two hours and fourteen minutes between my post suggesting Memtest86 and connell_2k7's response about both the HDD/RAM tests coming back clean.

 

[connell_2k7]

How do you run a windows repair?

 

[Matthew DeCarlo]

Minidump 041808-01:

BugCheck 1000008E, {c0000005, bf907867, b7086400, 0}
Probably caused by : nv4_disp.dll ( nv4_disp+6b82 )
----------------------------------------------------------------------------------
That belongs to your video card. Reinstall the drivers if possible.

http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx