BSOD on load after hibernate/stand by

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

koutsiog

Thread Starter
Joined
Oct 27, 2009
Messages
22
helo guys.I have a problem here.ALLWAYS when I load from standby/hibernate I get a BSOD with weired characters(may be because my xp is in greek).
If I go to event veiwer it has a red X in system.It says:
in english(translated):
Code:
error code 1000008e, parameter1 80000004, parameter 2 806eeae1, parameter 3 a99f265c, parameter 4 00000000.
in greek(as it apears):
Code:
Κωδ. σφάλματος 1000008e, παράμετρος1 80000004, παράμετρος 2 806eeae1, παράμετρος 3 a99f265c, παράμετρος 4 00000000.
if I click the hyperlink it says the problem is in faultrep.dll

I'm using latest win xp(sp3) in fujitsu m2010(nothing changed)
 
Joined
Dec 9, 2000
Messages
45,855
When did the problem begin? And have you tried doing a "System Restore" to a date prior to the problems?


I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to c:\windows\minidump and copy the last few minidump files to that folder. *this assumes 'c' is your boot drive, if it is not, subsitute accordingly
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder.
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.


If you do not see any minidumps, be sure you are not using any cache cleaner such as CCleaner. Also run sysdm.cpl and select Advanced > Startup and Recovery. Make sure "small memory dump" is the one chosen under "write debugging information" and the location should be %systemroot%\minidump
 
Joined
Dec 9, 2000
Messages
45,855
This is a bit difficult to call and more minidumps may be needed.

The first bugcheck faults your Audio driver; the second appears related to a PCI card installation and so may be hardware.

BugCheck 1000008E, {c0000005, aa34c59b, a870870c, 0}

Probably caused by : RtkHDAud.sys ( RtkHDAud+7359b )

BugCheck 1000008E, {80000004, 806eeae1, a99f265c, 0}

Unable to load image igxpmp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
I would run some memory diagnostics, also run chkdsk on the drive.

And remove FolderLock (seen as windrvNT.sys
in your loaded modules) which is a loose canon wherever it is found.

Esset Firewall may be a complicating factor in combination with Folder Lock and the Daemon Tools clone ware you also have installed.

You may also wish to try "clean boot" testing:

CLEAN BOOT TROUBLESHOOTING technique

First, restart in Safe Mode if necessary -- (tap the f8 key promptly on startup and choose the Safe Mode option from the boot menu) or Normal mode

Then:

Run msconfig and select the "Services" tab. Check "Hide Microsoft Services" and then disable the rest. Also uncheck "load startup items" on the general page.


Now restart and test the issue at hand

If no problems, run msconfig and recheck half the disabled items on the Services tab. Test again. If the problem recurs, UNcheck half the items you just checked to narrow down the culprit.

If the problem didn't occur, check the other half, so all the Services are enabled -- proceed to do this on the startup tab as well.

Get the idea? You want to isolate the problem to a specific startup if possible.

Note: if you already have items unchecked under msconfig > startups and are in “selective” startup mode – you should note what these are before beginning. They will need to be de-selected again.


http://support.microsoft.com/kb/929135/en-us

-----------------------------------------------

Since almost all bugchecks can be caused by faulty ram, I would recommend you perform memory tests.


Beginners Guides: Diagnosing Bad Memory

Memtest86 - A Stand-alone Memory Diagnostic
 

Attachments

Joined
Dec 9, 2000
Messages
45,855
A number of them are throwing errors pointing at your Intel Chipset, such as this:

BugCheck 1000008E, {c0000005, bf05a2c6, a8ace81c, 0}

Probably caused by : igxpdv32.DLL ( igxpdv32+b2c6 )
http://www.google.com/search?hl=en&...32.DLL+intel+bsod&aq=f&aqi=&aql=&oq=&gs_rfai=

You may have had more than one cause here, so I would update and or reinstall these using Intel's support >>

http://www.intel.com/support/detect.htm

If this does not resolve it I would uninstall Daemon Tools which may be a contributing factor here.
 
Joined
Dec 9, 2000
Messages
45,855
How did you reinstall the chipset drivers?

You may need to download them manually, and go through the Device Manager options to uninstall the current ones and to update drivers from the file you have downloaded.

Post any new minidumps after the reinstall.
 

koutsiog

Thread Starter
Joined
Oct 27, 2009
Messages
22
I did as you told me and it now works again.Here are the new minidumps you requested.if there is no other problem tell me to mark it as solved.Also,can I reinstall daemon tools and folder lock?
 

Attachments

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Members online

Top