Crashes when hibernating about 50% of the time

Hi,

Windows 7 started failing to hibernate properly a few months ago now and although I don't see a BSOD, a memory dump is produced and when I boot up again, Windows tells me it has recovered from a serious error. No crashes experienced during normal usage though!

Please see zip file attached and information below as requested.

Thanks in advance
Steven

- x86 (32-bit) or x64 ? x86 - the original installed OS on the system? It's installed on its own SSD. Windows XP still installed on separate HDD but no longer used. - an OEM or full retail version? Retail (upgrade) - What is the age of system (hardware)? Summer 2010 - What is the age of OS installation? October(?) 2010

CiaraJansonFan said:

Hi,

Windows 7 started failing to hibernate properly a few months ago now and although I don't see a BSOD, a memory dump is produced and when I boot up again, Windows tells me it has recovered from a serious error. No crashes experienced during normal usage though!

Please see zip file attached and information below as requested.

Thanks in advance
Steven

- x86 (32-bit) or x64 ? x86 - the original installed OS on the system? It's installed on its own SSD. Windows XP still installed on separate HDD but no longer used. - an OEM or full retail version? Retail (upgrade) - What is the age of system (hardware)? Summer 2010 - What is the age of OS installation? October(?) 2010

Virtually all of these related to NebAudio DigiTV PCI Audio/MPEG2 Driver. Yours is from 2006 Udate with a win 7 compatible or remove.


Other old drivers

Code:

nebaudio.sys    6/13/2006 12:49:41 AM        0x98239000    0x9823bf80    0x00002f80    0x448e51f5                        
nebvideo.sys    6/13/2006 1:12:30 AM        0x98233000    0x98238c00    0x00005c00    0x448e574e                        
PFC027.SYS    12/4/2006 10:34:41 PM        0x9fb44000    0x9fbbfd00    0x0007bd00    0x4574e8d1                        
lmimirr.sys    4/10/2007 5:32:11 PM        0x983ff000    0x983ffc80    0x00000c80    0x461c106b                        
RaInfo.sys    1/4/2008 1:57:12 PM        0xae74f000    0xae750800    0x00001800    0x477e8188                        
LMIRfsDriver.sys    7/14/2008 11:26:22 AM        0xae751000    0xae75b000    0x0000a000    0x487b7e2e                        
purendis.sys    6/5/2009 11:32:39 PM        0x8dbe2000    0x8dbec000    0x0000a000    0x4a29f167                        
pnarp.sys    6/6/2009 1:07:38 AM        0x8dbd8000    0x8dbe2000    0x0000a000    0x4a2a07aa

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Thanks for the quick reply!

Hmm, that's really strange - the only nebaudio.sys files I can find with a 2006 date are on my OLD Windows XP drive (now drive Z!). The ones on my drive C were only released in January 2010 and these were definitely advertised as being Windows 7 compatible!

Any ideas what's going on please?

Thanks again
Steven

CiaraJansonFan said:

Thanks for the quick reply!

Hmm, that's really strange - the only nebaudio.sys files I can find with a 2006 date are on my OLD Windows XP drive (now drive Z!). The ones on my drive C were only released in January 2010 and these were definitely advertised as being Windows 7 compatible!

Any ideas what's going on please?

Thanks again
Steven

The ones listed are being loaded wherever they are. They need to be removed or re-named.

Hi,

Very sorry to resurrect this old thread but I've been rather busy and I'm still having this problem despite (eventually) completely removing my Windows XP partition, so I'm just running Windows 7 Home Premium on its own now

I've produced another set of log files so please could someone have a look and let me know if it's still the same issue as before or whether another issue is causing this problem?

Thanks
Steven

Possible out of date drivers:

Code:

nebaudio	99d77000	99d79f80	Mon Jun 12 23:49:41 2006 (448e51f5)	00008254		nebaudio.sys
nebvideo	99d2f000	99d34c00	Tue Jun 13 00:12:30 2006 (448e574e)	00008722		nebvideo.sys
PFC027	a072e000	a07a9d00	Mon Dec 04 20:34:41 2006 (4574e8d1)	00083d26		PFC027.SYS
lmimirr	99d90000	99d90c80	Tue Apr 10 16:32:11 2007 (461c106b)	0000ea80		lmimirr.sys
RaInfo	af476000	af477800	Fri Jan 04 11:57:12 2008 (477e8188)	000035cd		RaInfo.sys
LMIRfsDriver	af478000	af482000	Mon Jul 14 10:26:22 2008 (487b7e2e)	00011b5c		LMIRfsDriver.sys
purendis	a42c9000	a42d3000	Fri Jun 05 22:32:39 2009 (4a29f167)	00013375		purendis.sys
pnarp	a42bf000	a42c9000	Sat Jun 06 00:07:38 2009 (4a2a07aa)	0000ce6e		pnarp.sys

nebaudio.sys
nebvideo.sys
PFC027.SYS
lmimirr.sys
RaInfo.sys
LMIRfsDriver.sys
purendis.sys
pnarp.sys
Do your best to update the above drivers... They could very well relate to your crashes.

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\CiaraJansonFan\Windows_NT6_BSOD_jcgriff2\030312-17425-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82e13000 PsLoadedModuleList = 0x82f5c4d0
Debug session time: Fri Mar  2 16:46:22.740 2012 (UTC - 7:00)
System Uptime: 3 days 4:34:52.301
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
...............
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 8784e030, Physical Device Object of the stack
Arg3: 82f3aae0, Functional Device Object of the stack
Arg4: 87975d98, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  87975d98

DEVICE_OBJECT: 00000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

CURRENT_IRQL:  0

STACK_TEXT:  
82f3aa94 82ed9f0f 0000009f 00000003 8784e030 nt!KeBugCheckEx+0x1e
82f3ab00 82ed9f88 82f3abac 00000000 82f47380 nt!PopCheckIrpWatchdog+0x1f5
82f3ab38 82e8d019 82f556e0 00000000 ac781c01 nt!PopCheckForIdleness+0x73
82f3ab7c 82e8cfbd 82f3dd20 82f3aca8 00000001 nt!KiProcessTimerDpcTable+0x50
82f3ac68 82e8ce7a 82f3dd20 82f3aca8 00000000 nt!KiProcessExpiredTimerList+0x101
82f3acdc 82e8b00e 010da916 d90026c8 82f47380 nt!KiTimerExpiration+0x25c
82f3ad20 82e8ae38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82f3ad24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x9F_3_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  0x9F_3_ANALYSIS_INCONCLUSIVE

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

This crash is due to the system sending a device driver the signal to turn itself off or turn itself on during a power cycle such as during sleep, hibernate, shut down, or startup. The device or device driver failed to respond to the signal and so the system crashed to force the power state. The most common components to cause this are network adapters or display card adapters. Could be caused by either the devices themselves or their drivers.

Unfortunately your crash analysis was inconclusive as to which driver caused the above behavior. Update all drivers possible and especially those that are possibly out of date. If you cannot update an out of date driver, remove the software using it from the system if possible, at least to test.