[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

 

[whodat]

greetings
you seem to be underpowered
get an idea of your requirements here [ add 25% to the load ]
nexus is a cheapo unit, can you borrow a trial psu?
post back

 

[Kokovartalo]

This is what i get from the inside of the latest minidump file....

*******************************************************************************
* *
* 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)

 

[whodat]

will it stay on long enough to check your device manager or to get into safe mode for a disk check and virus scan? try 1 stick of ram only....
i still am suspect of your psu.

 

[oshwyn5]

http://aumha.org/win5/kbestop.php

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile


0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).


The common denominator between these is a bad driver or incompatible hardware.
So the first thing to do is try a different driver for your video card since nv4_mini.sys and similar should be refering to nvidia driver files.

You could always check the memory addresses referenced and see if they are one of the ranges assigned your video card, but it is almost certainly a problem with it.

 

[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?

 

[whodat]

Would it help if I tried Win XP SP1?

dont you have pro with service pack 2

 

[Kokovartalo]

Yes I do!

 

[whodat]

did you try just 1 stick of ram? [ if there is 2? ] and a different slot also
also can you try a sfc check -

Go to the Run box on the Start Menu and type in:

sfc /scannow ( sfc if not reconized)

This command will immediately initiate the Windows File Protection service to scan all protected files and verify their integrity, replacing any files with which it finds a problem. You will need your Windows cd.
post back

 

[Kokovartalo]

thx. i´ll do that.

 

[whodat]

i am still concerned with the psu, the nexus is rated as low quality and 300 watts is borderline for any system, it would be nice if you could borrow a different supply just for a test before purchasing one... a spastic psu will give all types of strange error reports.

 

[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.

 

[VolvoNut]

Agh. Me too. Can't imagine what's going on, just got a new PSU (PC Power & Cooling 470W) and it's been working fine. This only really started happening after I got a new X800 XL. Here are the specs:

AMD 64 3200
ASUS K8V SE Deluxe
1 GB OCZ Dual Channel DDR400
2 80 GB Seagate SATA in RAID 0
Audigy 2 ZS
ATI X800 XL 256 MB

Here is the Everest sensor scan report:
Sensor Properties:
Sensor Type Winbond W83697HF (ISA 290h)
GPU Sensor Type National LM63 (ATI-I2C 4Ch)
Motherboard Name Asus K8V Series

Temperatures:
Motherboard 32 °C (90 °F)
CPU 51 °C (124 °F)
GPU 46 °C (115 °F)
GPU Ambient 40 °C (104 °F)
Seagate ST380013AS 49 °C (120 °F)

Voltage Values:
CPU Core 1.55 V
+3.3 V 3.23 V
+5 V 5.03 V
+12 V 11.25 V
+5 V Standby 4.97 V
Debug Info F FF FF FF
Debug Info T 32 51 255
Debug Info V 61 00 CA BB B9 D1 FF (01)

I know the 12V rail seems really low, but it's been that way forever and otherwise hasn't been causing a prob.


Cheers,
Al

 

[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-

 

[whodat]

good luck with your new system