BSOD BCCode:1e

[digbug]

I'm suffering from frequent nasty crushes.

Here is information my win7 give me after reboot:


Problem signature:
Problem Event Name: BlueScreen
OS Version:6.1.7600.2.0.0.256.1
Locale ID: 2052

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


and related files are attached to this post.

Please, somebody help me! I'm dying here.........Thanks in advance.

 

[wish]

Hi,
Your single dump file have 0x1e (KMODE_EXCEPTION_NOT_HANDLED) usual caused by drivers.

Start troubleshooting your problem by removing Avira and replace it with MSE.
You may go back to Avira after your Windows have stabled.
http://www.microsoft.com/security_essentials/

Uninstall your Acronis software because it's the outdate version.

And do you have idea what these 2 files belong to?
Better to uninstall that programs if you don't use it, because I see it load in your memory with unknown publisher and outdate timestamp.
C:\Windows\SysWOW64\Drivers\CMBProtector.dat
C:\Windows\SysWOW64\Drivers\CertClient.dat

Then these drivers need to be update:

wacommousefilter.sys Fri Feb 16 10:12:17 2007 --> [URL="http://www.wacom.com/downloads/drivers.php"]Wacom(tablet) Mouse Filter[/URL]
snapman.sys  Fri Oct 06 06:43:53 2006 --> [URL="http://www.acronis.com/"]Acronis True Image Snapshot[/URL]
LVUSBS64.sys Fri May 11 17:01:20 2007 --> [URL="http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en"]Logitech Camera driver[/URL]
lvuvc64.sys  Fri May 11 16:59:12 2007  --> [URL="http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en"]Logitech USB Video Class Driver[/URL]
lvpopf64.sys Fri Nov 10 19:08:05 2006 --> [URL="http://www.logitech.com/index.cfm/support_downloads/downloads/&cl=us,en"]also part your Logitech device[/URL]
CertClient.dat Wed Aug 27 00:23:55 2008  --> unknown 
CMBProtector.dat Tue Mar 11 19:41:13 2008 --> unknown

Do the suggestion above, if still get another BSOD then follow this instruction to collect new data:
Blue Screen of Death (BSOD) Posting Instructions

Log

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( amdppm!C1Halt+2 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+26b952f0115dfdc
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  d

EXCEPTION_RECORD:  fffff8800458c8c8 -- (.exr 0xfffff8800458c8c8)
ExceptionAddress: fffff80004ee43a8 (nt!KiSecondaryClockInterrupt+0x0000000000000138)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800458c970 -- (.trap 0xfffff8800458c970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ba664dddbd28ac00 rbx=0000000000000000 rcx=0101000200001f80
rdx=0000000000018bcc rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004ee43a8 rsp=fffff8800458cb00 rbp=fffff8800458cb80
 r8=000000000001d714  r9=0000000000000000 r10=0000000000004946
r11=fffffa8008402100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz ac pe cy
nt!KiSecondaryClockInterrupt+0x138:
fffff800`04ee43a8 1200            adc     al,byte ptr [rax] ds:b900:ba664ddd`bd28ac00=??
Resetting default scope

MISALIGNED_IP: 
nt!KiSecondaryClockInterrupt+138
fffff800`04ee43a8 1200            adc     al,byte ptr [rax]

LAST_CONTROL_TRANSFER:  from fffff80004ecf46e to fffff80004ed7710

STACK_TEXT:  
fffff880`0458b9b8 fffff800`04ecf46e : fffffa80`05353580 fffffa80`04f0b1a0 fffff880`0458c130 fffff800`04f04668 : nt!KeBugCheck
fffff880`0458b9c0 fffff800`04efd40d : fffff800`050e5edc fffff800`0501edac fffff800`04e67000 fffff880`0458c8c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0458b9f0 fffff800`04f04a90 : fffff800`05026b14 fffff880`0458ba68 fffff880`0458c8c8 fffff800`04e67000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0458ba20 fffff800`04f119ef : fffff880`0458c8c8 fffff880`0458c130 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff880`0458c100 fffff800`04ed6d82 : fffff880`0458c8c8 00000000`00000000 fffff880`0458c970 fffff880`04564180 : nt!KiDispatchException+0x16f
fffff880`0458c790 fffff800`04ed568a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0458c970 fffff800`04ee43a8 : 00000000`00000000 fffff880`0458cb80 fffff880`04564180 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`0458cb00 fffff880`04d757f2 : fffff800`04ee524a 00000000`0026bf51 fffffa80`050db9b8 fffff880`0456ef80 : nt!KiSecondaryClockInterrupt+0x138
fffff880`0458cc98 fffff800`04ee524a : 00000000`0026bf51 fffffa80`050db9b8 fffff880`0456ef80 00000000`00000001 : amdppm!C1Halt+0x2
fffff880`0458cca0 fffff800`04edfebc : fffff880`04564180 fffff880`00000000 00000000`00000000 fffff880`0422a4d0 : nt!PoIdle+0x53a
fffff880`0458cd80 00000000`00000000 : fffff880`0458d000 fffff880`04587000 fffff880`0458cd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
amdppm!C1Halt+2
fffff880`04d757f2 c3              ret

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  amdppm!C1Halt+2

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

 

[digbug]

About CertClient.dat CMBProtector.dat:
These two are issued by one of the major banks in P.R.China, There are at least 60 million copies are installed all over the country. If there really is something in those two file caused the crush, that will be huge! I think it's worthy of a much closer look on these two.

I'm working on the issues you pointed out right now. Thanks!

 

[digbug]

The devil strike again!

I'v created a new thread here.

Thanks in advance.