DRIVER_IRQL_NOT_LESS_OR_EQUAL hdd problem

G

Guest

My system -XP Pro, totally updated, has been experiencing stability problems
and has been locking up, especially when doing CPU intensive activities like
DVD rendering. I believe that the problem is due to the CPU overheating,
causing the system to shut down.

While attempting to fix this problem with a new CPU cooler, I started up the
DVD rendering procedure that caused the system to shut down in order to see
if that hardware helped.

Unfortunately my hardware fix did not work and the system froze up again.
But this time it would not come back up and I can not fix it. When I power
up, I get the XP splash screen followed by the BSOD, then back to POST. I
never get to the desktop. I tried using the XP Pro CD and chose the repair
option but it too went to the same BSOD.

The error I am getting is:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Stop: 0x00000D1

viamraid.sys
address F75BA000
base at F75BA000
Date stamp 4063e384

I am certain that the disk is corrupted - viamraid.sys is my disk driver and
I was doing disk writes at the time of the freeze up. Google searches seem to
point me in that direction and I believe it.

Is there any way I can uncorrupt my disk now? I am willing to do ANYTHING to
resolve this. Should I buy another disk, install XP Pro and fix it that way,
somehow? Should I go to a disk recovery company? Should I call Microsoft's
phone help? The cost is not important now. I want my data back. HELP!!!
 
B

Bob Day

linybob said:
My system -XP Pro, totally updated, has been experiencing stability problems
and has been locking up, especially when doing CPU intensive activities like
DVD rendering. I believe that the problem is due to the CPU overheating,
causing the system to shut down.

While attempting to fix this problem with a new CPU cooler, I started up the
DVD rendering procedure that caused the system to shut down in order to see
if that hardware helped.

Unfortunately my hardware fix did not work and the system froze up again.
But this time it would not come back up and I can not fix it. When I power
up, I get the XP splash screen followed by the BSOD, then back to POST. I
never get to the desktop. I tried using the XP Pro CD and chose the repair
option but it too went to the same BSOD.

The error I am getting is:

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Stop: 0x00000D1

viamraid.sys
address F75BA000
base at F75BA000
Date stamp 4063e384

I am certain that the disk is corrupted - viamraid.sys is my disk driver and
I was doing disk writes at the time of the freeze up. Google searches seem to
point me in that direction and I believe it.

Is there any way I can uncorrupt my disk now? I am willing to do ANYTHING to
resolve this. Should I buy another disk, install XP Pro and fix it that way,
somehow? Should I go to a disk recovery company? Should I call Microsoft's
phone help? The cost is not important now. I want my data back. HELP!!!

1. Download "Memtest86" from http://www.memtest86.com and run
it for a few passes to check out your memory. Zero errors is the only
acceptable result.

2. Try a repair install of Windows XP. See:
http://michaelstevenstech.com/XPrepairinstall.htm

-- Bob Day
http://bobday.vze.com
 
A

Anna

Bob Day said:
1. Download "Memtest86" from http://www.memtest86.com and run
it for a few passes to check out your memory. Zero errors is the only
acceptable result.

2. Try a repair install of Windows XP. See:
http://michaelstevenstech.com/XPrepairinstall.htm

-- Bob Day
http://bobday.vze.com


linybob:
Bob Day's advice is fine, however, before undertaking a Repair install it
would be desirable if you could first connect your corrupted drive as a
second drive in a functioning system so as to access whatever data files you
need from that drive and copy same. I would guess that you don't have
available another booting drive containing the XP OS or have access to
another computer where you could install your defective drive so what I
suggest may not be feasible.

Hopefully the Repair install will work in that you'll have a bootable,
functioning hard drive once again. Our experience with that install has been
very positive in that it "works" in many situations. But when it doesn't, no
lasting damage is done to the drive in terms of further corruption or the
inability to access data files along the lines I described above. Usually.
But I must add that we have come across situations (rare as they might be)
where the Repair install process failed catastrophically in that the drive
became further corrupted and made it more difficult to subsequently retrieve
data. I emphasize that (in our experience) it has been such a *rare*
occurrence (maybe happened twice out of scores of Repair installs we've
made) so it's something I don't wish to unduly stress.

I don't suppose there's any need to give you a sermon on the crucial
importance of maintaining systematic backups, is there?

Anyway, good luck.
Anna
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top