Windows XP Crashes. Another BSOD error

These errors:

Are looping errors. And the only thing I know of that does this sort of looping is Nvidia drivers.

Do a Google search on "nvidia looping error" and you will see what I mean.
I do not think there is a solution for it.

 

Most of the "nvidia looping error" I've read so far is that they have a problem on the nv4_disp driver and I can't see it on the dump file as well.

 

f7d99000 f8160000 nv4_mini nv4_mini.sys unavailable (FFFFFFFE)

No looping error condition?

Best wishes.
I hope someone else can provide you with more assistance than I was able to .

 

You've done quite a lot of help on trying to determine the culprint on my problem and I appreciate it. I am a little bit curious on your previous post that it was caused by "nvidia looping error" and where did you find this sir?

 

Hi Henry,

You have 100 memory error and this is the sign of bad paging space. Run chkdsk /r for the paging space hard disk at recovery console. Re-allocate the paging space.

cpc2004

 

You can easily de-allocate and re-allocate paging space:

Enter Safe Mode.
Set virtual memory to user managed size.
Set minimum and maximum to zero.
Start, Run, CMD

attrib -s -h -r C:\pagefile.sys
del c:\pagefile.sys
exit

Restore your Virtual memory settings and reboot to normal mode.

===================

Having said that, there is the possibility (still focused on the USBPORT.SYS driver) that KB890859 is to blame.

1. Remove the Hotfix -- it should appear in Control Panel, Add/Remove programs. If not, find its directory under \Windows and run the spuninst.exe file found there.

2. Download the Hotfix manually.

3. Run the Hotfix with an "/o" switch.

 

Sorry for the late feedback. I'll just give a small recap on my problem.

1. DRIVER_IRQL_NOT_LESS_OR_EQUAL which was Caused by USBPORT.SYS.
I've got this twice on the same day. Below is the summary

=== Occurence 1 ===
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000002, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f7d33433, address which referenced memory

=== Occurence 2 ===
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000002, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f7d3b433, address which referenced memory

2. Disabled other USB port via the device manager and got this bsod

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000002, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f7d3a433, address which referenced memory


3. Had applied the KB916595 patch as posted by bill. After 6 hours of usage, another bsod appears:

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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804f0d61, address which referenced memory

4. I've updated my bios to the latest version (1545). According to its release note that there's
an IRQ fix for USB Interrupts that conflict with other devices. I've thought that might help.
However it didn't solve the problem, instead it give me a flooded GetContextState failed, 0x80004002 message
on the dumpfile and indicating that it is partially corrupt. Still the stop error was:

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: 00000054, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804faac3, address which referenced memory

5. Tried the chkdsk /r and full scanned my hard disk using seagate's diagnostic tool. Now here's something new:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: abe4f0e1, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: abe4f0e1, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Haven't tried to re creating the paging space. I'll try that and see what happens.

Diagnostic tools that I've used so far as follows:
- memtest86+ 1.65 (via ultrabootcd)
- prime95 24.14 for windows
- intel desktop utilities
- everest home
- hot cpu test pro
- Seagate Seatools Desktop

Unfortunately, none of them shows any errors. But here's what I've noticed upon using these tools:

- I've booted the ultra boot cd, sometimes I've got stock on the ISOLINUX text message screen
but sometimes it works. Stange..
- Booted up the Seagate Seatools and when I use my USB mouse the program will halted
and displays "Abnormal Program Termination ". I still able to conduct a full surface scan
without using the mouse to avoid that program behavior.

So far, these are the headache causing me right now. And the strangest thing I experience is when
I stress test my PC, these BSOD wont show up not until I use it for normal use

 

Crash at timer IRQL

Hi,

One of your minidumps is crashed at IRQL 1c which is timer IRQL. This is the sign of hardware error. There have 25 confirmed root causes of this problem. 6 cases are CPU and 11 cases are RAM.

Overheat 1
CPU 6
RAM 11
M/B 3
Software 1
PSU 2
VIC 1
Total 25

Refer the following problem
http://www.windowsbbs.com/showthread.php?t=51149
http://www.windowsbbs.com/showthread.php?p=287065#post287065
http://www.techspot.com/vb/showthread.php?p=144841#post144841
http://www.techspot.com/vb/showthread.php?p=126919#post126919
http://www.techspot.com/vb/showthread.php?p=172009#post172009
http://www.techspot.com/vb/showthread.php?p=185777#post185777



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: 00000054, memory referenced
Arg2: 0000001c, IRQL <-- Clock Level IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804faac3, address which referenced memory


PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: abe4f0e1, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation. <<-- ?? 8 is invalid and probably it is caused by hardware error
Arg3: abe4f0e1, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

 

Thanks for the link cpc2004. I've already read some of them and most of them are caused by RAM. Just an update, I've down clocked my RAM from 667 to 533 & changed its timing. I'll observe what would happen.

 

Take the /PAE switch out of boot.ini and test for a few days.

I should mention that I have seen virtually identical debugger results from users who had Nero InCD installed.

 

So far my pc is stable after I've downclocked my RAM from 667 (5-5-5-15, auto detect) to 533 ( 4-4-4-12, manual). I don't know if this is a sign of a faulty RAM but according to my board's manual it can support DDR2 800 @ 1.8V. Anyway, I'll still observe my system's stability. I'll give you updates on this matter. Thanks.

 

Hi,

Downclock the ram and the blue screen problem is resolved. For detail refer here

 

I've just replaced my RAM with a new one and my system is stable now for 2 days. Now that random bsod is another case of faulty RAM. A big thanks for the help you had given me guys on solving my problem, really appreciate it. Thanks.

 

Hi,

Random BSOD is not always related to faulty ram and sometimes it is device driver. One of your minidumps is crashed with at IRQL x'1c' (ie clock level IRQL) and it is usually related to faulty ram. Thanks for your reply and my confirmed case of faulty ram relating to IRQL x'1c' is 12.