Windows recovering from a serious error?

Status
Not open for further replies.
Can anyone please help me figure out what is causing this error? My computer/Windows are not restarting, but the error still makes me nervous that my OS is going to slowly get worse if I don't fix it.

Here's the log from the Event Viewer, it's the same error for all of them:

Type Date Time Source Category Event User Computer
Error 2/14/2008 9:55:04 AM System Error (102) 1003 N/A JONS
Error 2/13/2008 1:51:14 PM System Error (102) 1003 N/A JONS
Error 2/12/2008 8:12:00 AM System Error (102) 1003 N/A JONS
Error 2/11/2008 1:34:24 AM System Error (102) 1003 N/A JONS
Error 2/9/2008 7:15:18 AM System Error (102) 1003 N/A JONS
Error 2/6/2008 10:51:27 AM System Error (102) 1003 N/A JONS


Error code 100000d1, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 ba6bc04b.
Error code 100000d1, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 ba6bc04b.
Error code 100000d1, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 ba6bc04b.
Error code 100000d1, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 ba6bc04b.
Error code 100000d1, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 ba6bc04b.
Error code 100000d1, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 ba6bc04b.

Thanks,

- Pomp

P.S. - I've seen how folks are able to interpret the findings above and boil it down to a device driver or other software issue, and this amazes me. If anyone knows of a technical resource where I can learn how to do this, I'd be happy to learn. :)
 
Are you getting Blue Screens of Death where it tells you that a fatal error has occurred and Windows needs to shut down, blah, blah, blah? And then it gives you numbers and it begins dumping memory?
 
The details you posted are not helpful in giving you the answer you requested.
You could have a driver error, or a software error that requires an upgrade, or you could have a minor memory error. .. usually it is a startup error of some software installed on your computer.
I assume you got this information from the Event viewer.
What you might want to do is check it frequently enough to relate the error notice to the time, so you can tell what you were doing at the time.
Give us your computer brand and model, and we can perhaps give you better clues.
 
Route44 - I don't get BSODs, and I don't need to restart. It simply gives me the error box, and I click OK, and life goes on.

raybay - It generally happens after starting my computer and logging in. My computer is a custom built one I made early last year. The errors didn't start until 2/6.
 
All six minidumps are 0xD1 errors 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.

In all six the driver cited is nvata.sys which is an Nvidia chipset driver, particularly a sata/raid driver. Many people have had issues with this driver. The recommended recourse to correct it is to update.

How is that for mojo? :cool: :)
 
Status
Not open for further replies.
Back