Windows XP Critical Error (mini.dmp)

[duritz]

I get this error from time to time when windows boots up.....

http://www.fbody.com/members/JpV63800/error.jpg

Does anyone know what it is? Why it happens?

It normally happens after I get a blue error screen from windows xp and have to turn off the power to reboot it.. When it reboots it gives that error

How can I fix this? It's the only problem I have with XP

 

[Ryan]

Clear out you temp directory and see what happens

 

[duritz]

Didn't think about that... Well I did it.. Lets see what happens next

Thanks rbloedow

 

[NogginBoink]

The driver instruction at address 0xF9D03DE3 accessed memory illegally.

I'd get pstat.txt from the resource kit and find the driver that contains this address (in the last section of the pstat report).

 

[duritz]

where do i find this pstat.txt and what's resource kit?

 

[yazz]

i thought i was the only one to see that error. i saw that error on a customer's system a few days ago. the person also had some other XP error messages as well. i cleared everything up except that specific error message. this error did not stop normal OS operation. but after doing some cross referencing with the registry and the filesystem it seems like this error is a registry error. there is a corrupted key/value in the registry. the error is so bad that one cannot even delete entry in the registry either in safemode or normal. when you try to delete it the OS gives you an invalid operation in trying to delete this specific key. if iremember correctly, the customer had an initial problem with ACPI during startup and shutdown--even though i cleared it up this error kept on returning. the only thing i could do was do a clean install of XP and press F7 during the first part of the installation process that says press F6 if you want to load additional drivers. after that do problems whatsoever. the customer's computer was not totally ACPI compliant.

 

[NogginBoink]

Yazz, you have no idea what you're talking about.

A STOP D1 happens when a driver attempts to access paged memory at an illegal processor IRQL. In duritz's case, the instruction at address 0xf9d03de3 tried to access memory location 0x0fbf9010.

To both of you: if you turn off autoreboot, the OS might display the name of the driver it thinks is causing the problem. Go to system control panel, advanced, startup and recovery. Uncheck "Automatically restart" and reboot for the setting to take effect. Next time it happens, see if the OS prints a driver file name on the blue screen.

Yazz, this message may not stop normal OS operation, but it means that this machine is being booted after blue screening.

While certain types of registry corruption will cause blue screens, it won't cause a STOP D1.