System failure in Win XP Pro with SP2: Driver IRQL not less or equal

[Kokovartalo]

Hey.

I have this annoying problem concerning system failure. I have had system crashes before and then it took about seven times to boot my system before it got stable. Then I had these failure messages: "page fault in non paged area" and "driver irql not less or equal". Now I have installed a clean version of Win XP Pro and I have Service Pack 2. All I have installed with it are Firefox, Norton Internet Security 2005 and Forceware 78.01 driver for my Geforce 6600GT.

I have cleaned my case and tried to switch my memorysticks and nothing works. My system won´t stay up at all now. These are the error messages:

Driver irql not less or equal

Stop: 0x000000D1 (0x85FFFFE4, 0x00000002, 0x00000000, 0x85FFFFE4)
and
Stop: 0x0000000A (0x006018C8, 0x00000002, 0x00000000, 0x804D9092)
and
Stop: 0x0000008E (0xC0000005, 0x00000045, 0xF894CB9C, 0x00000000)

Please, if someone could help me with this problem I would appreciate it a lot.
There is an attachment from the recent crashes (when I got the access to the files because now my OS won´t load at all even in safe mode) in minidump.zip. Thank You. (Feel free to ask any additional information)

My computer specs are:

AMD Athlon XP 1800+
Epox 8KHA+
Geforce 6600GT
Seagate Barracuda 80 GB & Maxtor Diamond Plus9 80 GB
Creative SoundBlaster PCI128
Codegen case with Nexus Silent 300W Power supply

 

[cpc2004]

Hi,

There have one confirmed case in this forum, Norton Internet Security Version 8.0.5.14 crash windows with blue screen.

 

[Kokovartalo]

Thanks for replying to my problem.

I´ll check out if it´s the Norton Internet Security and check my RAMs with MemTest86. I´ll get back if nothing works.

 

[Kokovartalo]

This is what I get from inside the latest minidump...


Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\admin\Desktop\Minidump\Mini101805-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Oct 18 21:51:40.613 2005 (GMT+3)
System Uptime: 0 days 0:00:30.243
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
..
Loading User Symbols
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {6018c8, 2, 0, 804d9092}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 006018c8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804d9092, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

READ_ADDRESS: The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
006018c8

CURRENT_IRQL: 2

FAULTING_IP:
nt+2092
804d9092 8a02 mov al,[edx]

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 82089ac8 to 804d9092

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
820f1830 82089ac8 00000002 00000001 00000000 nt+0x2092
00000000 00000000 00000000 00000000 00000000 0x82089ac8


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

 

[Kokovartalo]

Sorry about that...

Actually this is the right one....

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 006018c8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804d9092, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.

READ_ADDRESS: The call to LoadLibrary(exts) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
006018c8

CURRENT_IRQL: 2

FAULTING_IP:
nt!READ_REGISTER_UCHAR+4
804d9092 8a02 mov al,[edx]

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from f80126e8 to 804d9092

STACK_TEXT:
80550100 f80126e8 006018c8 820f1830 f802f520 nt!READ_REGISTER_UCHAR+0x4
WARNING: Stack unwind information not available. Following frames may be wrong.
820f1830 82089ac8 00000002 00000001 00000000 nv4_mini+0x4a6e8
00000000 00000000 00000000 00000000 00000000 0x82089ac8


FOLLOWUP_IP:
nv4_mini+4a6e8
f80126e8 ?? ???

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_mini+4a6e8

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42b0d148

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xA_nv4_mini+4a6e8

BUCKET_ID: 0xA_nv4_mini+4a6e8

Followup: MachineOwner
---------

eax=00000000 ebx=00000000 ecx=820f184c edx=006018c8 esi=006018c8 edi=820f4818
eip=804d9092 esp=80550104 ebp=820f1830 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!READ_REGISTER_UCHAR+0x4:
804d9092 8a02 mov al,[edx] ds:0023:006018c8=??
ChildEBP RetAddr Args to Child
80550100 f80126e8 006018c8 820f1830 f802f520 nt!READ_REGISTER_UCHAR+0x4 (FPO: [1,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
820f1830 82089ac8 00000002 00000001 00000000 nv4_mini+0x4a6e8
00000000 00000000 00000000 00000000 00000000 0x82089ac8
start end module name
804d7000 806eb100 nt ntoskrnl.exe Wed Mar 02 02:59:37 2005 (42250FF9)
806ec000 806ffd80 hal halacpi.dll Wed Aug 04 08:59:04 2004 (41107B28)
ba265000 ba288000 Fastfat Fastfat.SYS Wed Aug 04 09:14:15 2004 (41107EB7)
baf18000 baf1b280 ndisuio ndisuio.sys Wed Aug 04 09:03:10 2004 (41107C1E)
bf800000 bf9c0500 win32k win32k.sys Wed Mar 02 03:06:42 2005 (422511A2)
bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 09:00:51 2004 (41107B93)
bf9d3000 bfd8a400 nv4_disp nv4_disp.dll Thu Jun 16 04:04:44 2005 (42B0D02C)
f4fc9000 f4fe0480 dump_atapi dump_atapi.sys Wed Aug 04 08:59:41 2004 (41107B4D)
f4fe1000 f504f400 mrxsmb mrxsmb.sys Wed Jan 19 06:26:50 2005 (41EDE18A)
f5050000 f507aa00 rdbss rdbss.sys Thu Oct 28 04:13:57 2004 (418047D5)
f507b000 f508e000 SAVRTPEL SAVRTPEL.SYS Tue Mar 08 00:49:43 2005 (422CDA87)
f508e000 f50e0000 SPBBCDrv SPBBCDrv.sys Thu Jul 22 02:08:26 2004 (40FEF76A)
f50e0000 f5101d00 afd afd.sys Wed Aug 04 09:14:13 2004 (41107EB5)
f5102000 f5129c00 netbt netbt.sys Wed Aug 04 09:14:36 2004 (41107ECC)
f512a000 f5159420 symidsco symidsco.sys Mon Sep 19 04:04:01 2005 (432E0E81)
f515a000 f5182dc0 SYMFW SYMFW.SYS Tue Apr 05 21:11:07 2005 (4252D4BB)
f5183000 f51a3f00 ipnat ipnat.sys Thu Sep 30 01:28:36 2004 (415B3714)
f51cc000 f51e8cc0 SYMEVENT SYMEVENT.SYS Wed Jul 20 05:10:15 2005 (42DDB287)
f51e9000 f5228ce0 SYMTDI SYMTDI.SYS Tue Apr 05 21:10:52 2005 (4252D4AC)

 

[Kokovartalo]

Now I have tried the newest nvidia drivers and third party omega drivers. Nothing helps. It helps for a while when I chkdsk/r from the recovery console. But what is odd it started to do this suddenly. Would it help if I tried Win XP SP1?

 

[cpc2004]

Hi,

From the stack trace it crashes at READ_REGISTER_UCHAR+0x4 (read a byte of data from I/O port). Probably this is hardware error at your video card.


STACK_TEXT:
80550100 f80136e8 006018c8 81fe91a8 f8030520 nt!READ_REGISTER_UCHAR+0x4
WARNING: Stack unwind information not available. Following frames may be wrong.
81fe91a8 820f8228 00000002 00000001 00000000 nv4_mini+0x4a6e8
00000000 00000000 00000000 00000000 00000000 0x820f8228

 

[Kokovartalo]

Now i have formatted the whole drive and when I tried to install a new version of Windows I got BSOD saying "0x0000001D.......". Now I am going to try only with one stick of RAM (Kingston) and leave the other one a side. I´m also plugging out my second optical drive and a case fan if it helps. It can very possibly be the PSU. The man at the computer shop conviced me to buy it (Nexus) and told it would run all my hardware. I´ll get back when I get the OS up and running.

 

[Tedster]

http://support.microsoft.com/default.aspx?scid=kb;en-us;818326

ensure you have the latest service packs

 

[Kokovartalo]

Thank you all for helping me. Sorry I haven´t replied sooner but i just bought new MB and memory. It was the MB that caused all the problems. It was defected and actually pretty old. Nevertheless i have to buy new PSU because even the 6600GT package says "preferred using minimum of 350W PSU". -THX-

 

[cpc2004]

Hi,

Did you use on-board video for your old motherboard?

 

[Kokovartalo]

No my Epox 8KHA+ didn´t have an integrated card. The main cause was propably this: I had geforce ti4200 and the GPU FAN broke down, then the old PSU said goodbye to the world. It probably send somekind of a voltage peak to the MB and broke some component. What kinf of PSU should I get for my system????...I have Nexus Silent 300W and the voltage levels are pretty low. System is same but the new MB is ASUS-A7V600-X and I bought Kingston 512 MB 400 MHz.

 

[denvertechjay]

Has anyone gotten this with a Chaintech 7kjd motherboard? I'm also getting this errors repeatedly and I have tried getting a new memory stick (512mb pc2100 non-ecc)

PAGE FAULT IN NONPAGED AREA
DRIVER IRQL NOT LESS OR EQUAL
BAD POOL HEADER

And At least a few times I get just a basic BSOD with it referring to win32k.sys.

I have tried:

Flashing BIOS
Updating my video card (XFX Nvidia GeForce FX 5200 256mb Onboard RAM) drivers
Updating sound card drivers
Updating service packs
Modifying Bios settings (tried fail-safe settings and optimal)

I'm at my wits ends with these errors, and I'm about ready to chuck the whole computer out the window and start from scratch by building another one. That would be a PITA to do, but at this point I'm frustrated as hell.

Any tips or advice would be helpful and appreciated!

~Jeffrey