Did not See BSOD, but received a Recover PC Message Instead.

Jhealy03 · 09 Jan 2015

I didn't see the BSOD, but received a Recover PC Message Instead, and then after repair a message that It could not recover. Fortunately that was False so there is some issue with that process itself but I found two Critical Errors in the System Event Log.

- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 2
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- TimeCreated
[ SystemTime] 2015-01-10T00:21:51.806823400Z
EventRecordID 1702352
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer JOHNS-HP-WIN7
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 159
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa801bffd050
BugcheckParameter3 0xfffff8000211a3d8
BugcheckParameter4 0xfffffa801bfb9010
SleepInProgress false
PowerButtonTimestamp 0

Jhealy03 · 09 Jan 2015

I saw the thread about this error, but this Laptop has been in the same place for a while without issue and saw the two anti-virus program collision but again this has been running this way for a while so would like further investigation since it happened twice yesterday, but I only saw it once, most likely after the first recover succeeded, but the second would not.

I checked things and rebooted anyway and the system came up without issue and continued printing jobs from a few days ago so I am wondering if that is when this started and not today. I have been getting a port missing error for the printer but it prints anyway, but this occurs on two different computers Laptop and Desktop, so don't think so.

I also rarely reboot anything as I have too much open to save all of my work and keep track of what I am working on, but this has rarely been an issue and it rebooted on its own twice today.

Hopefully there is something you find that is not one of the items mentioned above.

Thanks,

John

Golden · 10 Jan 2015

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa801bffd050, fffff8000211a3d8, fffffa801bfb9010}

*** WARNING: Unable to verify timestamp for ndasscsi.sys
*** ERROR: Module load completed but symbols could not be loaded for ndasscsi.sys
Probably caused by : ndasscsi.sys

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

0: kd> !irp fffffa801bfb9010
Irp is active with 4 stacks 2 is current (= 0xfffffa801bfb9128)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa801bffd050 00000000 fffff88000e4ff50-00000000 Success Error Cancel pending
	       \Driver\ndasscsi	partmgr!PmPowerCompletion
			Args: 00000000 00000001 00000004 00000000
 [ 16, 2]   0 e1 fffffa801bdf5b90 00000000 00000000-00000000    pending
	       \Driver\partmgr
			Args: 00000000 00000001 00000004 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa801be23820    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm ndasscsi
start             end                 module name
fffff880`09045000 fffff880`090c0000   ndasscsi T (no symbols)           
    Loaded symbol image file: ndasscsi.sys
    Image path: \SystemRoot\system32\DRIVERS\ndasscsi.sys
    Image name: ndasscsi.sys
    Timestamp:        Wed Jan 13 05:00:23 2010 (4B4CBFBF)
    CheckSum:         0007D801
    ImageSize:        0007B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

NDAS Device Management	c:\program files\ndas\system\ndasmgmt.exe /startup	Public	Common Startup

The outdated NDAS SCSI driver seems to be the problem. Unfortunately the manufacturer's website appears to be non-operational.

ximeta

Try find a contact number for them, and see if they have an updated driver - if not the only choice you have to fix the issue is to uninstall the software and device.