machine dies with no minidump or log, 2 minidumps after running verifier

c7c4c7 · Oct 19, 2012

Started finding the machine powered off, no minidumps and nothing in the event log. There were no recent hardware additions. Machine runs Windows 7 pro all updates applied. I ran the verifier and the machine died twice. I'm hoping that there is something in the dumps that might indicate the problem that I don't see.

I'm not sure what all information you might need please post any questions and I'll reply

Thanks for your help

View attachment Windows7_Vista_jcgriff2.zip

jcgriff2 · Oct 19, 2012

Hi -

There were two very nice VERIFIER_ENABLED mini kernel dumps to work with.

Both named Acronis -

Code:

snapman.sys               Tue Feb 21 03:10:08 2012 (4F435160)

http://www.sysnative.com/drivers/driver.php?id=snapman.sys

Update or Remove Acronis.

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:


Debug session time: Thu Oct 18 03:15:20.227 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101812-82477-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 13:13:16.396
BugCheck C4, {f6, c, fffffa80088df060, fffff88001a61346}
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+d346 )
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 

Arg1: 00000000000000f6, Referencing user handle as KernelMode.

Arg2: 000000000000000c, Handle value being referenced.

Arg3: fffffa80088df060, Address of the current process.

Arg4: fffff88001a61346, Address inside the driver that is performing the incorrect reference.


BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_snapman+d346
BiosVersion = 5.07 
BiosReleaseDate = 04/04/2007
SystemManufacturer = HP-Pavilion
SystemProductName = GC671AA-ABA a6130n

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Oct 17 03:13:54.420 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101712-91260-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 2:42:34.574
BugCheck C4, {f6, c, fffffa80088f3060, fffff88001a0d346}
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+d346 )
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 

Arg1: 00000000000000f6, Referencing user handle as KernelMode.

Arg2: 000000000000000c, Handle value being referenced.

Arg3: fffffa80088f3060, Address of the current process.

Arg4: fffff88001a0d346, Address inside the driver that is performing the incorrect reference.


BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_snapman+d346
BiosVersion = 5.07 
BiosReleaseDate = 04/04/2007
SystemManufacturer = HP-Pavilion
SystemProductName = GC671AA-ABA a6130n

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


         
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           https://mvp.support.microsoft.com/profile/Griffith   

           jcgriff2 - Sysnative Forums
             
           [url]www.jcgriff2.com[/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

c7c4c7 · Oct 19, 2012

jcgriff2 said:

Hi -

There were two very nice VERIFIER_ENABLED mini kernel dumps to work with.

Both named Acronis -

Code:

snapman.sys               Tue Feb 21 03:10:08 2012 (4F435160)

http://www.sysnative.com/drivers/driver.php?id=snapman.sys

Update or Remove Acronis.

Regards. . .

jcgriff2

`

BSOD SUMMARY

Code:


Debug session time: Thu Oct 18 03:15:20.227 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101812-82477-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 13:13:16.396
BugCheck C4, {f6, c, fffffa80088df060, fffff88001a61346}
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+d346 )
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 

Arg1: 00000000000000f6, Referencing user handle as KernelMode.

Arg2: 000000000000000c, Handle value being referenced.

Arg3: fffffa80088df060, Address of the current process.

Arg4: fffff88001a61346, Address inside the driver that is performing the incorrect reference.


BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_snapman+d346
BiosVersion = 5.07 
BiosReleaseDate = 04/04/2007
SystemManufacturer = HP-Pavilion
SystemProductName = GC671AA-ABA a6130n

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Oct 17 03:13:54.420 2012 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101712-91260-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 2:42:34.574
BugCheck C4, {f6, c, fffffa80088f3060, fffff88001a0d346}
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+d346 )
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 

Arg1: 00000000000000f6, Referencing user handle as KernelMode.

Arg2: 000000000000000c, Handle value being referenced.

Arg3: fffffa80088f3060, Address of the current process.

Arg4: fffff88001a0d346, Address inside the driver that is performing the incorrect reference.


BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_snapman+d346
BiosVersion = 5.07 
BiosReleaseDate = 04/04/2007
SystemManufacturer = HP-Pavilion
SystemProductName = GC671AA-ABA a6130n

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


         
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           https://mvp.support.microsoft.com/profile/Griffith   

           jcgriff2 - Sysnative Forums
             
           http://jcgriff2.comwww.jcgriff2.com 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

c7c4c7 · Oct 19, 2012

That was quick, thanks for the help. I'll look for an update for acronis

Vir Gnarus · Oct 19, 2012

While Acronis is certainly to blame for those two Driver Verifier crashes, one thing that concerns me is your description of the symptoms. You said your system is turning off, not restarting? If so, you either have a overheating CPU and your mobo is triggering a failsafe, or you have some other hardware issue like a short circuit or a bad PSU.

Search

Search

machine dies with no minidump or log, 2 minidumps after running verifier

c7c4c7

BSOD Enthusiast

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

c7c4c7

BSOD Enthusiast

c7c4c7

BSOD Enthusiast

Vir Gnarus

BSOD Kernel Dump Expert

machine dies with no minidump or log, 2 minidumps after running verifier

c7c4c7

BSOD Enthusiast

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

c7c4c7

BSOD Enthusiast

c7c4c7

BSOD Enthusiast

Vir Gnarus

BSOD Kernel Dump Expert

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)