System recovered from serious error 2

[piratefan]

Today, my system froze on me. Only happened once before. I hit the reset, but no error message appeared. Then later, the screen just "rolls" and it reboots on its own. When it came back up, the shortcuts would not work. Sort of frozen again. I did a shutdown and then when it rebooted, the error message that the system had recovered from a serious error. Now I have had 2 of these messages in the past.
Somebody had instructed me before to do this and I did. System...shutoff system restore. Reboot. Turn on system restore. Reboot.
Is there anything else I can do?
Thanks.

 

[bcastner]

1.5 times the physical RAM installed.

 

[piratefan]

Thanks again.

 

[piratefan]

Is there a Plan B? I have done the above and had it happen again today. Biggest puzzle to me is this. It hardly ever did it before. I have had this XP Pro for about 10 months now. Took it a long time before it happened. It just seems to be occurring more often now, which scares moi.
Thanks.

 

[bcastner]

right-click My Computer, Properties, Advanced, Startup and Recover - Settings, uncheck in the bottom box to automaticly restart the computer, and check to write to the Event log.

We need to see the real error message.

 

[piratefan]

The event log was checked. When I unchecked the auto restart, I got something like this :
If the pagefile on volume C: has an initial size of less than 0 megabytes, then the system may not be able to create a debugging information file if a STOP error occurs.

So I was unsure and didn't continue.

 

[piratefan]

When I go to event viewer, Type = Error, Source = System Error, Category = (102), Event = 1003.
If that helps at all.

 

[bcastner]

http://www.eventid.net/display.asp?eventid=1003&source=system

 

[piratefan]

Two questions sir. Where can I find the error codes I see mentioned here? I mean for my particular error?

I noticed one respondent saying this :

From the net, someone mentioned setting the Virtual memory to 0 and then reboot, delete the pagefile.sys file. Then set the virtual memory back to normal. It worked for me.

Should I maybe try that? Is it a simple matter of putting min and max values to 0? The pagefile.sys deleted and vm set back to normal. What would normal be?

Thanks very much.

 

[piratefan]

I got adventurous and found error code. 000000d1.

 

[piratefan]

Error code, 000000d1.
Parameter 1 is 00000004.
P2 is 00000002.
P3 is 00000000.
P4 is f75acbe5.

I tried searching for exact matches and came up with nothing. But I am guessing there is a hardware problem from the other 000000d1 error codes I see?

 

[bcastner]

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. See:

http://www.microsoft.com/technet/tr...prodtechnol/winxppro/reskit/prmd_stp_ottj.asp

Also:

http://support.microsoft.com/?kbid=810093

http://support.microsoft.com/?kbid=316208

 

[piratefan]

I looked at this. My windows gets updated about once a month. Is there something I can do to find if there is a bad driver? Those monthly updates never show anything critical.
Thanks.

 

[piratefan]

DRIVER_IRQL_NOT_LESS_OR_EQUAL

By the way, I don't remember seeing the above message anywhere when I get the problem. Just "system has recovered from a serious error".

 

[bcastner]

That is what an 0xd1 error code represents.

 

[piratefan]

Well, I'm getting an education with this anyway.

 

[bcastner]

Enable DrWatson, and next time post the detailed error response from the logs. Start, Run, drwatson -i

For Windows XP, these files are stored in the \Documents and Settings\All Users\ApplicationData\Microsoft\Dr Watson folder. The DrWtsn32.log file is appended each time a program error occurs; the User.dmp file is overwritten each time.

 

[piratefan]

Let me make sure my dumb butt understands. I should wait until the next time it gives the error to run DrWatson? Or I can run it now?
Also, that is drwatson -i? A space prior to the -i?
Excuse my ignorance. You guys amaze me with your knowledge of this stuff. I am green with envy.

 

[bcastner]

Now. You want DrWatson active prior to the error.

drwatson<space>-i

 

[piratefan]

It opens a window saying &quot;No faults detected&quot;. I assume I just let this window alone. Now if I shut down tonight and have had no error, I assume I enable the good doctor in the morning upon start. Until I get another error.
Thanks for all the help, bcastner.

 

[fishfan]

I stopped having this error after I updated to the latest version of activesync for my Ipaq 2215, in addition, I stopped having it connected on a continuous basis via the USB port, and am syncing via wireless.