Still freezing...

Associate
Joined
4 Dec 2008
Posts
1,812
Never before have I had so many problems putting together one build.

Well I've sorted nearly everything now, but a few days afterwards, it's started freezing again. The screensaver freezes, but the system is still responsive, Ctrl+Alt+Del made the mouse appear over it and alt+f4 made the system attempt to shutdown (but failed with the "you still have **** open that needs saving noise).

Hard reset it, and got "The system has recovered from a serious error." though the comp never actually bluescreened (maybe the screensaver was hard locked and I couldn't see it afterwards?), clicked see info, brings up BCCode: ea, thought oh great minidump/something to work with, but there's nothing there.

Originally the problems were narrowed down to: faulty wifi card, RAM slot needed cleaning, and damaged XP files RAMDiskXP.sys, mup.sys.

I'm suspecting something to do with PAVP lite mode since I enabled it not long ago but currently have no access to the comp.

Any ideas? As you can probably tell I'm at wits' end with this.

Cheers

~edit, system spec:

Intel E2140 1.6GHz
2x1GB PNY PC6400 5-5-5-18
GA-G41M-ES2L
GMA X4500 / G41 Express
WD1600AAJS
Antec Basiq 350W
Clean XP Pro install
 
So it goes into screensaver mode and dies? Looks like something is not happy powering down and powering back up again. On that assumption...

..., changing the screen saver to none would be the first thing I'd do.

If you hard reset windows, it will bark at you for not properly shutting down.

Also, I've seen that problem before, on my laptop. The weird thing is that if I leave it to wake up for a minute or two, it comes back to life.

Haven't worked it out, it doesn't happen anymore after a few recent win 7 updates (not win XP, sorry).

So I don't know, disable hibernation / sleep mode see if the computer locks up. Change the power saving profiles, ect... But that's where I'd look.

Also, logged windows events (administrative tools -> event logs) can give a clue.
 
So it goes into screensaver mode and dies? Looks like something is not happy powering down and powering back up again. On that assumption...

..., changing the screen saver to none would be the first thing I'd do.

If you hard reset windows, it will bark at you for not properly shutting down.

Also, I've seen that problem before, on my laptop. The weird thing is that if I leave it to wake up for a minute or two, it comes back to life.

Haven't worked it out, it doesn't happen anymore after a few recent win 7 updates (not win XP, sorry).

So I don't know, disable hibernation / sleep mode see if the computer locks up. Change the power saving profiles, ect... But that's where I'd look.

Also, logged windows events (administrative tools -> event logs) can give a clue.

That's the problem, if there's no screensaver it'll end up with burn-in. Monitor standby has the same outcome.

And indeed, but not usually the Serious Error thing with a BCCode, not with this comp usually at least.

Turning off the WiFi power saving mode fixed it a while back, I'll have a look to see if it's re-enabled somehow.

No events are shown, apart from the improper shutdown ones from when I've reset.
 
More troubles :(

Code:
Loading Dump File [G:\Mini060711-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jun  7 20:01:22.484 2011 (UTC + 1:00)
System Uptime: 0 days 0:07:36.016
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {8a1f1020, 8a5b6ec0, b9cf3cbc, 1}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Unable to load image \SystemRoot\System32\watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 8a1f1020, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 8a5b6ec0, Pointer to a DEFERRED_WATCHDOG object.
Arg3: b9cf3cbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------


FAULTING_THREAD:  8a1f1020

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  2

BUGCHECK_STR:  0xEA

LAST_CONTROL_TRANSFER:  from 00000000 to 806e7a08

STACK_TEXT:  
a79c0618 00000000 00000000 00000000 00000000 hal!KeAcquireInStackQueuedSpinLock+0x18


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  ZEROED_STACK

Followup: MachineOwner
---------

1: kd> lol
       ^ Syntax error in 'lol'
1: kd> .thread 8alf1020
Syntax error at '8alf1020'
1: kd> .thread kb
*** WARNING: Unable to verify timestamp for HTTP.sys
*** ERROR: Module load completed but symbols could not be loaded for HTTP.sys
*** WARNING: Unable to verify timestamp for srv.sys
*** ERROR: Module load completed but symbols could not be loaded for srv.sys
*** WARNING: Unable to verify timestamp for wdmaud.sys
*** ERROR: Module load completed but symbols could not be loaded for wdmaud.sys
*** WARNING: Unable to verify timestamp for mrxdav.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxdav.sys
*** WARNING: Unable to verify timestamp for wudfrd.sys
*** ERROR: Module load completed but symbols could not be loaded for wudfrd.sys
*** WARNING: Unable to verify timestamp for ndisuio.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisuio.sys
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
*** WARNING: Unable to verify timestamp for dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
*** WARNING: Unable to verify timestamp for Fastfat.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fastfat.SYS
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*** WARNING: Unable to verify timestamp for rdbss.sys
*** ERROR: Module load completed but symbols could not be loaded for rdbss.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** WARNING: Unable to verify timestamp for ipnat.sys
*** ERROR: Module load completed but symbols could not be loaded for ipnat.sys
*** WARNING: Unable to verify timestamp for netbt.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for ipsec.sys
*** ERROR: Module load completed but symbols could not be loaded for ipsec.sys
*** WARNING: Unable to verify timestamp for Dxapi.sys
*** ERROR: Module load completed but symbols could not be loaded for Dxapi.sys
*** WARNING: Unable to verify timestamp for usbscan.sys
*** ERROR: Module load completed but symbols could not be loaded for usbscan.sys
*** WARNING: Unable to verify timestamp for mouhid.sys
*** ERROR: Module load completed but symbols could not be loaded for mouhid.sys
*** WARNING: Unable to verify timestamp for hidusb.sys
*** ERROR: Module load completed but symbols could not be loaded for hidusb.sys
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
*** WARNING: Unable to verify timestamp for wpdusb.sys
*** ERROR: Module load completed but symbols could not be loaded for wpdusb.sys
*** WARNING: Unable to verify timestamp for sysaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
*** WARNING: Unable to verify timestamp for update.sys
*** ERROR: Module load completed but symbols could not be loaded for update.sys
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
*** WARNING: Unable to verify timestamp for rdpdr.sys
*** ERROR: Module load completed but symbols could not be loaded for rdpdr.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for ndiswan.sys
*** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
*** WARNING: Unable to verify timestamp for MRV8335XP.sys
*** ERROR: Module load completed but symbols could not be loaded for MRV8335XP.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*** WARNING: Unable to verify timestamp for HDAudBus.sys
*** ERROR: Module load completed but symbols could not be loaded for HDAudBus.sys
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
*** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
*** WARNING: Unable to verify timestamp for WudfPf.sys
*** ERROR: Module load completed but symbols could not be loaded for WudfPf.sys
*** WARNING: Unable to verify timestamp for isapnp.sys
*** ERROR: Module load completed but symbols could not be loaded for isapnp.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for wanarp.sys
*** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
*** WARNING: Unable to verify timestamp for netbios.sys
*** ERROR: Module load completed but symbols could not be loaded for netbios.sys
*** WARNING: Unable to verify timestamp for Fips.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fips.SYS
*** WARNING: Unable to verify timestamp for Cdfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Cdfs.SYS
*** WARNING: Unable to verify timestamp for KMWDFILTER.sys
*** ERROR: Module load completed but symbols could not be loaded for KMWDFILTER.sys
*** WARNING: Unable to verify timestamp for HIDCLASS.SYS
*** ERROR: Module load completed but symbols could not be loaded for HIDCLASS.SYS
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
*** WARNING: Unable to verify timestamp for i8042prt.sys
*** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys
*** WARNING: Unable to verify timestamp for imapi.sys
*** ERROR: Module load completed but symbols could not be loaded for imapi.sys
*** WARNING: Unable to verify timestamp for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
*** WARNING: Unable to verify timestamp for rasl2tp.sys
*** ERROR: Module load completed but symbols could not be loaded for rasl2tp.sys
*** WARNING: Unable to verify timestamp for raspppoe.sys
*** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
*** WARNING: Unable to verify timestamp for raspptp.sys
*** ERROR: Module load completed but symbols could not be loaded for raspptp.sys
*** WARNING: Unable to verify timestamp for msgpc.sys
*** ERROR: Module load completed but symbols could not be loaded for msgpc.sys
*** WARNING: Unable to verify timestamp for termdd.sys
*** ERROR: Module load completed but symbols could not be loaded for termdd.sys
*** WARNING: Unable to verify timestamp for NDProxy.SYS
*** ERROR: Module load completed but symbols could not be loaded for NDProxy.SYS
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for usbuhci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbuhci.sys
*** WARNING: Unable to verify timestamp for usbehci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbehci.sys
*** WARNING: Unable to verify timestamp for kbdclass.sys
*** ERROR: Module load completed but symbols could not be loaded for kbdclass.sys
*** WARNING: Unable to verify timestamp for TDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for TDI.SYS
*** WARNING: Unable to verify timestamp for ptilink.sys
*** ERROR: Module load completed but symbols could not be loaded for ptilink.sys
*** WARNING: Unable to verify timestamp for raspti.sys
*** ERROR: Module load completed but symbols could not be loaded for raspti.sys
*** WARNING: Unable to verify timestamp for mouclass.sys
*** ERROR: Module load completed but symbols could not be loaded for mouclass.sys
*** WARNING: Unable to verify timestamp for HIDPARSE.SYS
*** ERROR: Module load completed but symbols could not be loaded for HIDPARSE.SYS
*** WARNING: Unable to verify timestamp for vga.sys
*** ERROR: Module load completed but symbols could not be loaded for vga.sys
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
*** WARNING: Unable to verify timestamp for Npfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
*** WARNING: Unable to verify timestamp for ssmdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssmdrv.sys
*** WARNING: Unable to verify timestamp for usbccgp.sys
*** ERROR: Module load completed but symbols could not be loaded for usbccgp.sys
*** WARNING: Unable to verify timestamp for usbprint.sys
*** ERROR: Module load completed but symbols could not be loaded for usbprint.sys
*** WARNING: Unable to verify timestamp for USBSTOR.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBSTOR.SYS
*** WARNING: Unable to verify timestamp for speedfan.sys
*** ERROR: Module load completed but symbols could not be loaded for speedfan.sys
*** WARNING: Unable to verify timestamp for rramdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for rramdisk.sys
*** WARNING: Unable to verify timestamp for rasacd.sys
*** ERROR: Module load completed but symbols could not be loaded for rasacd.sys
*** WARNING: Unable to verify timestamp for ndistapi.sys
*** ERROR: Module load completed but symbols could not be loaded for ndistapi.sys
*** WARNING: Unable to verify timestamp for swenum.sys
*** ERROR: Module load completed but symbols could not be loaded for swenum.sys
*** WARNING: Unable to verify timestamp for USBD.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBD.SYS
*** WARNING: Unable to verify timestamp for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
*** WARNING: Unable to verify timestamp for Beep.SYS
*** ERROR: Module load completed but symbols could not be loaded for Beep.SYS
*** WARNING: Unable to verify timestamp for mnmdd.SYS
*** ERROR: Module load completed but symbols could not be loaded for mnmdd.SYS
*** WARNING: Unable to verify timestamp for RDPCDD.sys
*** ERROR: Module load completed but symbols could not be loaded for RDPCDD.sys
*** WARNING: Unable to verify timestamp for avgio.sys
*** ERROR: Module load completed but symbols could not be loaded for avgio.sys

Keep getting these, I'll get like 3 in a row with the screen colours going mashed up then the comp'll be fine for days.

Have put the dimms into single channel to see if it'll make any difference, it's doing a similar thing to faulty VRAM but it's an onboard GPU. The RAM memtests fine however.

Might just end up getting a cheapy PCI-E card and replacing the WiFi since I think that's still playing a part too.
 
This has come up before. From Microsoft (a bit long winded):
This issue occurs if the graphics adapter is caught in an infinite loop while it waits for the video hardware to become idle. This can indicate that there is a problem with the video hardware, or that the graphics adapter cannot program the hardware correctly.

The Stop error message may also occur in video adapter drivers that do not represent a physical device. For example, this Stop error message may occur in the virtual video adapter driver that is used by Symantec PCAnywhere. If PCAnywhere is installed on a computer where this error message occurs, visit the Symantec Web site to determine whether there are any available fixes for your version of PCAnywhere.

Resolution:
To correct this issue, follow the methods that are described in this section in the order in which they are presented until the issue is resolved.

The first four methods described in this article are for beginning to intermediate users. The final two methods deal with advanced troubleshooting and are designed for advanced users.

You may find it easier to follow the steps if you print this article first.
Method 1: Use the Windows Error Reporting tool
Use the Windows Error Reporting Tool to send the error to Microsoft and determine of a fix or workaround is available. To do this, follow these steps:
Click Send Error Report when you are prompted to send the error report to Microsoft.
If a fix or a workaround is available, click More Information. This helps you obtain the fix or information about how to work around the issue.
If this method worked, you are finished. If you continue to receive the stop error message, go to method 2.
Method 2: Install the latest driver for your video adapter
To detect and to install the latest driver for your video adapter in Windows XP, visit the following Microsoft Web site:
http://update.microsoft.com
If this method worked, you are finished. If you continue to receive the stop error message, go to method 3.
Method 3: Contact the video card manufacturer to obtain and install the latest driver
The driver is software that enables videos to be viewed on your computer. See the documentation that was included with your computer to determine the manufacturer for your video card. Then, use the links in the following list to find the contact information for your video card manufacturer in order to obtain and install the latest driver. For more information about hardware and software vendor contact information, visit the following Microsoft Web site:
http://support.microsoft.com/gp/vendors
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

If this method worked, you are finished. If you continue to receive the stop error message, go to method 4.
Method 4: Replace your video card
For information about how to replace your video card, please see the documentation that was included with your computer.

If this method worked, you are finished. If you continue to receive the stop error message, and you are comfortable trying advanced troubleshooting steps, go to the "Advanced troubleshooting" section.

If you are not comfortable with advanced troubleshooting, you might want to go to the “Next Steps” section for additional resources that may be able to help.
Back to the top
Advanced troubleshooting
These methods are intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help or contact Support. For information about how to contact Support, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/
Method 1: Disable or update device drivers
View the Microsoft Hardware Compatibility List (HCL) to determine whether the PCI devices in the computer are compatible with Windows XP. For information about the hardware compatibility list, visit the following Microsoft Web site:
http://www.microsoft.com/whdc/hcl/default.mspx
Update the video adapter drivers to the latest versions.
If a driver is listed by name in the Stop error message, disable or remove that driver.
Disable or remove any drivers or services that you recently added.
Note If the error occurs during the startup sequence, and the system partition is using the NTFS file system, you may be able to use safe mode to rename or to delete the faulty driver. If the driver is used as part of the system startup process in safe mode, you must start the computer by using the Recovery Console to use the file. For more information about video adapter drivers in safe mode, click the following article number to view the article in the Microsoft Knowledge Base:
292460 How to troubleshoot the video adapter driver in safe mode in Windows XP
Note If the problem is associated with the Win32k.sys file, the problem may be caused by a third-party remote control program. To remove the service, use the Recovery Console to start the computer, and then delete the specified system service file.

If this method worked, you are finished. If you continue to receive the stop error message, go to method 2.
Method 2: Adjust the Hardware Acceleration
Click Start, click Control Panel, and then double-click Display.
On the Settings tab, click Advanced, and then click the Troubleshoot tab.
Move the Hardware Acceleration slider to None, and then click to clear the Enable write combining check box.
Click OK, and then click OK.
Note This procedure prevents the graphics adapter from programming the hardware incorrectly, but you may lose some display functionality and performance. Although you can increase the hardware acceleration settings higher than None to regain functionality and performance, these settings increase the possibility that the issue will occur again. For maximum stability, leave hardware acceleration off.
Info taken from http://support.microsoft.com/default.aspx?scid=kb;EN-US;q293078

Google is your friend
 
Last edited:
Back
Top Bottom