Navigation section

Windows 7 Frequent BSOD

D

DashWave

New Member
Joined
Jan 18, 2011
Messages
34
Hi... I keep on having BSOD..its random but causes are consistent. I ran Windbg but some causes are very hard to figure out. I already fixed the BSOD from audio problem but I still get the " ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) " and other dumps. I also updated my bios to the latest firmware.


Memtest results are good so far so not sure where to go to next. Attached are info that might help.. Thanks

Link RemovedLink RemovedLink Removed
 


Solution
D
Hey Cyber.. Thanks so much for your help. I got a brand new HDD. I returned my HDD hoping that it was the issue. They said that it'll take 3 weeks for me to get a replacement so while waiting, I bought a new WD HDD. I installed OS and everything seems to working fine. Will keep you posted but I hope I wont get another crash. Seems like it was a faulty HDD from the start :D
Sort by date Sort by votes
Attach RamMon report as txt, and would be also great if you could give a link to the makers's description page for Kingston 99U5471-002.A00LF. The sticks are identical but they are not from the same batch.


1. Disable Driver Verifier, it has detected nothing:


BugCheck C4, {91, a, fffff88002f6efc0, 0}
PROCESS_NAME: System
EXCEPTION_RECORD: fffff88002f6cbf8 -- (.exr 0xfffff88002f6cbf8)
ExceptionAddress: 0000f800038c9504
ExceptionCode: c0000005 (Access violation)
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4944 )
Click to expand...





2. Update Intel Management Engine Interface
Link Removed




3. It looks like the cause of your crashes is unclear,

- command prompt > sfc /scannow
- HDD test HD Tune website HDDScan
- up to you to test RAM per stick and per slot. But before that give me your RamMon report.















DMPS

Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\022511-17550-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\windbgsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03849000 PsLoadedModuleList = 0xfffff800`03a86e50
Debug session time: Fri Feb 25 19:15:33.169 2011 (UTC - 5:00)
System Uptime: 0 days 0:21:24.355
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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) -                           .

FAULTING_IP: 
+3839343061303633
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88002f8ca58 -- (.exr 0xfffff88002f8ca58)
ExceptionAddress: 0000f88003a75c61
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f8cb00 -- (.trap 0xfffff88002f8cb00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000020 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000f88003a75c61 rsp=fffff88002f8cc98 rbp=0000000000000000
 r8=fffffa80054e87a0  r9=fffff88003a792a4 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
0000f880`03a75c61 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800038b2c2e to fffff800038baed0

STACK_TEXT:  
fffff880`02f8bb38 fffff800`038b2c2e : 00000000`00000000 fffff880`0ff2e9e9 fffff880`02f8c2b0 fffff800`038e7e28 : nt!KeBugCheck
fffff880`02f8bb40 fffff800`038e0bed : fffff800`03ac7f78 fffff800`03a061d0 fffff800`03849000 fffff880`02f8ca58 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8bb70 fffff800`038e8250 : fffff800`03a08b5c fffff880`02f8bbe8 fffff880`02f8ca58 fffff800`03849000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8bba0 fffff800`038f51b5 : fffff880`02f8ca58 fffff880`02f8c2b0 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff880`02f8c280 fffff800`038ba542 : fffff880`02f8ca58 00000000`00000002 fffff880`02f8cb00 fffff880`02f64180 : nt!KiDispatchException+0x135
fffff880`02f8c920 fffff800`038b8e4a : 00000000`00000000 fffff880`02f8cb80 00000000`00000001 fffffa80`05515ee0 : nt!KiExceptionDispatch+0xc2
fffff880`02f8cb00 0000f880`03a75c61 : fffff800`038c8a3a 00000000`002b9a1c fffffa80`05515c68 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8cc98 fffff800`038c8a3a : 00000000`002b9a1c fffffa80`05515c68 00000000`00000000 00000001`00000001 : 0xf880`03a75c61
fffff880`02f8cca0 fffff800`038c36cc : fffff880`02f64180 fffff880`00000002 00000000`00000002 fffff880`00000000 : nt!PoIdle+0x53a
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`038b2c2e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

































Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\022611-20155-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\windbgsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03867000 PsLoadedModuleList = 0xfffff800`03aa4e50
Debug session time: Sat Feb 26 15:52:45.332 2011 (UTC - 5:00)
System Uptime: 0 days 0:35:05.519
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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) -                           .

FAULTING_IP: 
+3839343061303633
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88002f8ca58 -- (.exr 0xfffff88002f8ca58)
ExceptionAddress: 0000f88003de9c61
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f8cb00 -- (.trap 0xfffff88002f8cb00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000020 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000f88003de9c61 rsp=fffff88002f8cc98 rbp=0000000000000000
 r8=fffffa800471d8d0  r9=fffff88003ded2a4 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
0000f880`03de9c61 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800038d0c2e to fffff800038d8ed0

STACK_TEXT:  
fffff880`02f8bb38 fffff800`038d0c2e : 00000000`0000003c 00000000`00000001 fffff880`02f8c2b0 fffff800`03905e28 : nt!KeBugCheck
fffff880`02f8bb40 fffff800`038febed : fffff800`03ae5f78 fffff800`03a241d0 fffff800`03867000 fffff880`02f8ca58 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8bb70 fffff800`03906250 : fffff800`03a26b5c fffff880`02f8bbe8 fffff880`02f8ca58 fffff800`03867000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8bba0 fffff800`039131b5 : fffff880`02f8ca58 fffff880`02f8c2b0 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff880`02f8c280 fffff800`038d8542 : fffff880`02f8ca58 00000000`00000002 fffff880`02f8cb00 fffff880`02f64180 : nt!KiDispatchException+0x135
fffff880`02f8c920 fffff800`038d6e4a : fffffa80`050a7002 00000001`25da50c6 fffff880`02f8cb70 fffff880`02f8cb20 : nt!KiExceptionDispatch+0xc2
fffff880`02f8cb00 0000f880`03de9c61 : fffff800`038e6a3a 00000000`002b99f4 fffffa80`0545c8e8 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8cc98 fffff800`038e6a3a : 00000000`002b99f4 fffffa80`0545c8e8 00000000`00000000 00000000`00000000 : 0xf880`03de9c61
fffff880`02f8cca0 fffff800`038e16cc : fffff880`02f64180 fffff880`00000002 00000000`00000002 fffff880`00000000 : nt!PoIdle+0x53a
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`038d0c2e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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






























Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\022811-15865-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\windbgsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03859000 PsLoadedModuleList = 0xfffff800`03a96e50
Debug session time: Mon Feb 28 19:02:12.669 2011 (UTC - 5:00)
System Uptime: 0 days 0:57:53.245
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, a, fffff88002f6efc0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4944 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
	the operating system. The only supported way to extend a kernel
	mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 000000000000000a
Arg3: fffff88002f6efc0
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  a

EXCEPTION_RECORD:  fffff88002f6cbf8 -- (.exr 0xfffff88002f6cbf8)
ExceptionAddress: 0000f800038c9504
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

TRAP_FRAME:  fffff88002f6cca0 -- (.trap 0xfffff88002f6cca0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000002f64000 rbx=0000000000000000 rcx=00000000c0000101
rdx=00000000fffff880 rsi=0000000000000000 rdi=0000000000000000
rip=0000f800038c9504 rsp=fffff88002f6ce30 rbp=fffff88002f6ceb0
 r8=0000f800038c8e3e  r9=0000000000000000 r10=0000000000000000
r11=fffff88002f8b4a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
0000f800`038c9504 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800039218fa to fffff800038caf00

STACK_TEXT:  
fffff880`02f6b1c8 fffff800`039218fa : 00000000`000000c4 00000000`00000091 00000000`0000000a fffff880`02f6efc0 : nt!KeBugCheckEx
fffff880`02f6b1d0 fffff800`038f7e73 : 00000000`00000000 00000000`00000000 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4944
fffff880`02f6b210 fffff800`039051b5 : fffff880`02f6c0c8 fffff880`02f6be20 fffff880`02f6c170 fffff880`02f6c3b0 : nt!RtlDispatchException+0x33
fffff880`02f6b8f0 fffff800`038ca542 : fffff880`02f6c0c8 00000000`00000000 fffff880`02f6c170 00000000`00000001 : nt!KiDispatchException+0x135
fffff880`02f6bf90 fffff800`038c8e4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f6c170 fffff800`038c1e63 : fffff800`038a0210 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f6c308 fffff800`038a0210 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0x223
fffff880`02f6c310 fffff800`0389ff88 : fffff880`02f6c3b0 00000000`00000001 fffff880`02f6c3b0 fffff880`02f6cc00 : nt!KiOpFetchBytes+0x30
fffff880`02f6c340 fffff800`03905573 : fffff880`02f6cbf8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiOpDecode+0x68
fffff880`02f6c390 fffff800`03905170 : fffff880`02f6cbf8 fffff880`02f6cca0 fffff880`02f6cca0 00000000`00000000 : nt!KiPreprocessFault+0x53
fffff880`02f6c420 fffff800`038ca542 : fffff880`02f6cbf8 fffff880`02f8c318 fffff880`02f6cca0 fffff880`02f8c3c0 : nt!KiDispatchException+0xf0
fffff880`02f6cac0 fffff800`038c8e4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f6cca0 0000f800`038c9504 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f6ce30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xf800`038c9504


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4944
fffff800`039218fa cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4944

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4944

BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4944

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




DRIVERS

Code: 
start             end                 module name
fffff880`00ebe000 fffff880`00f15000   ACPI     ACPI.sys     Tue Jul 14 03:19:34 2009 (4A5BC106)
fffff880`02c46000 fffff880`02cd0000   afd      afd.sys      Tue Jul 14 03:21:40 2009 (4A5BC184)
fffff880`03e10000 fffff880`03e26000   AgileVpn AgileVpn.sys Tue Jul 14 04:10:24 2009 (4A5BCCF0)
fffff880`00e00000 fffff880`00e0b000   amdxata  amdxata.sys  Tue May 19 21:56:59 2009 (4A12F2EB)
fffff880`00ff5000 fffff880`00ffe000   atapi    atapi.sys    Tue Jul 14 03:19:47 2009 (4A5BC113)
fffff880`00c2a000 fffff880`00c54000   ataport  ataport.SYS  Tue Jul 14 03:19:52 2009 (4A5BC118)
fffff880`01934000 fffff880`0193b000   Beep     Beep.SYS     Tue Jul 14 04:00:13 2009 (4A5BCA8D)
fffff880`03ee6000 fffff880`03ef7000   blbdrive blbdrive.sys Tue Jul 14 03:35:59 2009 (4A5BC4DF)
fffff880`04d18000 fffff880`04d36000   bowser   bowser.sys   Tue Jul 14 03:23:50 2009 (4A5BC206)
fffff960`006b0000 fffff960`006d7000   cdd      cdd.dll      unavailable (00000000)
fffff880`01901000 fffff880`0192b000   cdrom    cdrom.sys    Tue Jul 14 03:19:54 2009 (4A5BC11A)
fffff880`00d3e000 fffff880`00dfe000   CI       CI.dll       Tue Jul 14 05:32:13 2009 (4A5BE01D)
fffff880`0189b000 fffff880`018cb000   CLASSPNP CLASSPNP.SYS Tue Jul 14 03:19:58 2009 (4A5BC11E)
fffff880`00ce0000 fffff880`00d3e000   CLFS     CLFS.SYS     Tue Jul 14 03:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01073000   cng      cng.sys      Tue Jul 14 03:49:40 2009 (4A5BC814)
fffff880`03e00000 fffff880`03e10000   CompositeBus CompositeBus.sys Tue Jul 14 04:00:33 2009 (4A5BCAA1)
fffff880`04dec000 fffff880`04df5000   cpuz135_x64 cpuz135_x64.sys Tue Nov 09 16:33:36 2010 (4CD94DB0)
fffff880`04b12000 fffff880`04b20000   crashdmp crashdmp.sys Tue Jul 14 04:01:01 2009 (4A5BCABD)
fffff880`03e45000 fffff880`03ec8000   csc      csc.sys      Tue Jul 14 03:24:26 2009 (4A5BC22A)
fffff880`03ec8000 fffff880`03ee6000   dfsc     dfsc.sys     Tue Jul 14 03:23:44 2009 (4A5BC200)
fffff880`02c17000 fffff880`02c26000   discache discache.sys Tue Jul 14 03:37:18 2009 (4A5BC52E)
fffff880`01885000 fffff880`0189b000   disk     disk.sys     Tue Jul 14 03:19:57 2009 (4A5BC11D)
fffff880`04ade000 fffff880`04b00000   drmk     drmk.sys     Tue Jul 14 05:01:25 2009 (4A5BD8E5)
fffff880`04b2c000 fffff880`04b35000   dump_atapi dump_atapi.sys Tue Jul 14 03:19:47 2009 (4A5BC113)
fffff880`04b20000 fffff880`04b2c000   dump_dumpata dump_dumpata.sys Tue Jul 14 03:19:47 2009 (4A5BC113)
fffff880`04b35000 fffff880`04b48000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 03:21:51 2009 (4A5BC18F)
fffff880`04b06000 fffff880`04b12000   Dxapi    Dxapi.sys    Tue Jul 14 03:38:28 2009 (4A5BC574)
fffff880`10abc000 fffff880`10bb0000   dxgkrnl  dxgkrnl.sys  Fri Oct 02 05:00:14 2009 (4AC5509E)
fffff880`10bb0000 fffff880`10bf6000   dxgmms1  dxgmms1.sys  Tue Jul 14 03:38:32 2009 (4A5BC578)
fffff880`03f1d000 fffff880`03f6c000   e1k62x64 e1k62x64.sys Thu Sep 30 00:02:28 2010 (4CA39B54)
fffff880`03a5c000 fffff880`03b35000   eamonm   eamonm.sys   Thu Dec 09 08:29:20 2010 (4D006930)
fffff880`0193b000 fffff880`01960000   ehdrv    ehdrv.sys    Thu Dec 09 08:29:58 2010 (4D006956)
fffff880`04c00000 fffff880`04c21000   epfwwfpr epfwwfpr.sys Thu Dec 09 08:26:09 2010 (4D006871)
fffff880`01125000 fffff880`01139000   fileinfo fileinfo.sys Tue Jul 14 03:34:25 2009 (4A5BC481)
fffff880`010d9000 fffff880`01125000   fltmgr   fltmgr.sys   Tue Jul 14 03:19:59 2009 (4A5BC11F)
fffff880`013d0000 fffff880`013da000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 03:19:45 2009 (4A5BC111)
fffff880`0184b000 fffff880`01885000   fvevol   fvevol.sys   Sat Sep 26 06:34:26 2009 (4ABD7DB2)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Tue Jul 14 03:21:08 2009 (4A5BC164)
fffff800`03810000 fffff800`03859000   hal      hal.dll      Tue Jul 14 05:27:36 2009 (4A5BDF08)
fffff880`0fe2e000 fffff880`0fe52000   HDAudBus HDAudBus.sys Tue Jul 14 04:06:13 2009 (4A5BCBF5)
fffff880`0fe00000 fffff880`0fe11000   HECIx64  HECIx64.sys  Thu Sep 17 23:54:16 2009 (4AB293E8)
fffff880`04b83000 fffff880`04b9c000   HIDCLASS HIDCLASS.SYS Tue Jul 14 04:06:21 2009 (4A5BCBFD)
fffff880`04b9c000 fffff880`04ba4080   HIDPARSE HIDPARSE.SYS Tue Jul 14 04:06:17 2009 (4A5BCBF9)
fffff880`04b75000 fffff880`04b83000   hidusb   hidusb.sys   Tue Jul 14 04:06:22 2009 (4A5BCBFE)
fffff880`04c50000 fffff880`04d18000   HTTP     HTTP.sys     Tue Jul 14 03:22:16 2009 (4A5BC1A8)
fffff880`014ed000 fffff880`014f6000   hwpolicy hwpolicy.sys Tue Jul 14 03:19:22 2009 (4A5BC0FA)
fffff880`03fdf000 fffff880`03ff5000   intelppm intelppm.sys Tue Jul 14 03:19:25 2009 (4A5BC0FD)
fffff880`01831000 fffff880`01840000   kbdclass kbdclass.sys Tue Jul 14 03:19:50 2009 (4A5BC116)
fffff880`04ba5000 fffff880`04bb3000   kbdhid   kbdhid.sys   Tue Jul 14 04:00:20 2009 (4A5BCA94)
fffff800`00bd4000 fffff800`00bde000   kdcom    kdcom.dll    Tue Jul 14 05:31:07 2009 (4A5BDFDB)
fffff880`040b5000 fffff880`040f8000   ks       ks.sys       Thu Mar 04 07:32:25 2010 (4B8F37D9)
fffff880`013a5000 fffff880`013bf000   ksecdd   ksecdd.sys   Tue Jul 14 03:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 09:03:32 2009 (4B21E0B4)
fffff880`04b00000 fffff880`04b05200   ksthunk  ksthunk.sys  Tue Jul 14 04:00:19 2009 (4A5BCA93)
fffff880`03b56000 fffff880`03b6b000   lltdio   lltdio.sys   Tue Jul 14 04:08:50 2009 (4A5BCC92)
fffff880`04bc0000 fffff880`04be3000   luafv    luafv.sys    Tue Jul 14 03:26:13 2009 (4A5BC295)
fffff880`00c88000 fffff880`00ccc000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 05:29:10 2009 (4A5BDF66)
fffff880`04b48000 fffff880`04b56000   monitor  monitor.sys  Tue Jul 14 03:38:52 2009 (4A5BC58C)
fffff880`010bf000 fffff880`010ce000   mouclass mouclass.sys Tue Jul 14 03:19:50 2009 (4A5BC116)
fffff880`04bb3000 fffff880`04bc0000   mouhid   mouhid.sys   Tue Jul 14 04:00:20 2009 (4A5BCA94)
fffff880`00c10000 fffff880`00c2a000   mountmgr mountmgr.sys Tue Jul 14 03:19:54 2009 (4A5BC11A)
fffff880`04d36000 fffff880`04d4e000   mpsdrv   mpsdrv.sys   Tue Jul 14 04:08:25 2009 (4A5BCC79)
fffff880`04d4e000 fffff880`04d7b000   mrxsmb   mrxsmb.sys   Sat Feb 27 10:52:19 2010 (4B88CF33)
fffff880`04d7b000 fffff880`04dc9000   mrxsmb10 mrxsmb10.sys Sat Feb 27 10:52:28 2010 (4B88CF3C)
fffff880`04dc9000 fffff880`04dec000   mrxsmb20 mrxsmb20.sys Sat Feb 27 10:52:26 2010 (4B88CF3A)
fffff880`019be000 fffff880`019c9000   Msfs     Msfs.SYS     Tue Jul 14 03:19:47 2009 (4A5BC113)
fffff880`00f1e000 fffff880`00f28000   msisadrv msisadrv.sys Tue Jul 14 03:19:26 2009 (4A5BC0FE)
fffff880`01139000 fffff880`01197000   msrpc    msrpc.sys    Tue Jul 14 03:21:32 2009 (4A5BC17C)
fffff880`02c0c000 fffff880`02c17000   mssmbios mssmbios.sys Tue Jul 14 03:31:10 2009 (4A5BC3BE)
fffff880`015ed000 fffff880`015ff000   mup      mup.sys      Tue Jul 14 03:23:45 2009 (4A5BC201)
fffff880`014fb000 fffff880`015ed000   ndis     ndis.sys     Tue Jul 14 03:21:40 2009 (4A5BC184)
fffff880`0fe52000 fffff880`0fe5e000   ndistapi ndistapi.sys Tue Jul 14 04:10:00 2009 (4A5BCCD8)
fffff880`011d1000 fffff880`01200000   ndiswan  ndiswan.sys  Tue Jul 14 04:10:11 2009 (4A5BCCE3)
fffff880`04164000 fffff880`04179000   NDProxy  NDProxy.SYS  Tue Jul 14 04:10:05 2009 (4A5BCCDD)
fffff880`02d4f000 fffff880`02d5e000   netbios  netbios.sys  Tue Jul 14 04:09:26 2009 (4A5BCCB6)
fffff880`02cd0000 fffff880`02d15000   netbt    netbt.sys    Tue Jul 14 03:21:28 2009 (4A5BC178)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Tue Jul 14 03:21:46 2009 (4A5BC18A)
fffff880`019c9000 fffff880`019da000   Npfs     Npfs.SYS     Tue Jul 14 03:19:48 2009 (4A5BC114)
fffff880`02c00000 fffff880`02c0c000   nsiproxy nsiproxy.sys Tue Jul 14 03:21:02 2009 (4A5BC15E)
fffff800`03859000 fffff800`03e36000   nt       ntkrnlmp.exe Tue Jul 14 03:40:48 2009 (4A5BC600)
fffff880`01202000 fffff880`013a5000   Ntfs     Ntfs.sys     Tue Jul 14 03:20:47 2009 (4A5BC14F)
fffff880`0192b000 fffff880`01934000   Null     Null.SYS     Tue Jul 14 03:19:37 2009 (4A5BC109)
fffff880`10aba000 fffff880`10abb180   nvBridge nvBridge.kmd Sat Jan 08 04:57:22 2011 (4D27C482)
fffff880`0fe5f000 fffff880`10ab9d00   nvlddmkm nvlddmkm.sys Sat Jan 08 05:07:22 2011 (4D27C6DA)
fffff880`02d29000 fffff880`02d4f000   pacer    pacer.sys    Tue Jul 14 04:09:41 2009 (4A5BCCC5)
fffff880`03fc2000 fffff880`03fdf000   parport  parport.sys  Tue Jul 14 04:00:40 2009 (4A5BCAA8)
fffff880`00f68000 fffff880`00f7d000   partmgr  partmgr.sys  Tue Jul 14 03:19:58 2009 (4A5BC11E)
fffff880`00f28000 fffff880`00f5b000   pci      pci.sys      Tue Jul 14 03:19:51 2009 (4A5BC117)
fffff880`00fee000 fffff880`00ff5000   pciide   pciide.sys   Tue Jul 14 03:19:49 2009 (4A5BC115)
fffff880`00c00000 fffff880`00c10000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 03:19:48 2009 (4A5BC114)
fffff880`013bf000 fffff880`013d0000   pcw      pcw.sys      Tue Jul 14 03:19:27 2009 (4A5BC0FF)
fffff880`04000000 fffff880`040a6000   peauth   peauth.sys   Tue Jul 14 05:01:19 2009 (4A5BD8DF)
fffff880`04aa1000 fffff880`04ade000   portcls  portcls.sys  Tue Jul 14 04:06:27 2009 (4A5BCC03)
fffff880`00ccc000 fffff880`00ce0000   PSHED    PSHED.dll    Tue Jul 14 05:32:23 2009 (4A5BE027)
fffff880`0180d000 fffff880`01831000   rasl2tp  rasl2tp.sys  Tue Jul 14 04:10:11 2009 (4A5BCCE3)
fffff880`03e26000 fffff880`03e41000   raspppoe raspppoe.sys Tue Jul 14 04:10:17 2009 (4A5BCCE9)
fffff880`013da000 fffff880`013fb000   raspptp  raspptp.sys  Tue Jul 14 04:10:18 2009 (4A5BCCEA)
fffff880`02c26000 fffff880`02c40000   rassstp  rassstp.sys  Tue Jul 14 04:10:25 2009 (4A5BCCF1)
fffff880`02daa000 fffff880`02dfb000   rdbss    rdbss.sys    Tue Jul 14 03:24:09 2009 (4A5BC219)
fffff880`03ff5000 fffff880`04000000   rdpbus   rdpbus.sys   Tue Jul 14 04:17:46 2009 (4A5BCEAA)
fffff880`019a3000 fffff880`019ac000   RDPCDD   RDPCDD.sys   Tue Jul 14 04:16:34 2009 (4A5BCE62)
fffff880`019ac000 fffff880`019b5000   rdpencdd rdpencdd.sys Tue Jul 14 04:16:34 2009 (4A5BCE62)
fffff880`019b5000 fffff880`019be000   rdprefmp rdprefmp.sys Tue Jul 14 04:16:35 2009 (4A5BCE63)
fffff880`01197000 fffff880`011d1000   rdyboost rdyboost.sys Tue Jul 14 03:34:34 2009 (4A5BC48A)
fffff880`03b6b000 fffff880`03b83000   rspndr   rspndr.sys   Tue Jul 14 04:08:50 2009 (4A5BCC92)
fffff880`04843000 fffff880`04aa0a00   RTKVHD64 RTKVHD64.sys Tue Sep 14 13:17:43 2010 (4C8F3DB7)
fffff880`04c21000 fffff880`04c2c000   secdrv   secdrv.SYS   Wed Sep 13 17:18:38 2006 (4508052E)
fffff880`0fe11000 fffff880`0fe1d000   serenum  serenum.sys  Tue Jul 14 04:00:33 2009 (4A5BCAA1)
fffff880`02d5e000 fffff880`02d7b000   serial   serial.sys   Tue Jul 14 04:00:40 2009 (4A5BCAA8)
fffff880`014e5000 fffff880`014ed000   spldr    spldr.sys    Mon May 11 20:56:27 2009 (4A0858BB)
fffff880`0589c000 fffff880`05932000   srv      srv.sys      Fri Aug 27 07:38:00 2010 (4C773318)
fffff880`04179000 fffff880`041e0000   srv2     srv2.sys     Fri Aug 27 07:37:46 2010 (4C77330A)
fffff880`03b83000 fffff880`03bb0000   srvnet   srvnet.sys   Fri Aug 27 07:37:24 2010 (4C7732F4)
fffff880`10bf6000 fffff880`10bf7480   swenum   swenum.sys   Tue Jul 14 04:00:18 2009 (4A5BCA92)
fffff880`01602000 fffff880`017ff000   tcpip    tcpip.sys    Mon Jun 14 07:39:04 2010 (4C15A458)
fffff880`04c2c000 fffff880`04c3e000   tcpipreg tcpipreg.sys Tue Jul 14 04:09:49 2009 (4A5BCCCD)
fffff880`01800000 fffff880`0180d000   TDI      TDI.SYS      Tue Jul 14 03:21:18 2009 (4A5BC16E)
fffff880`019da000 fffff880`019f8000   tdx      tdx.sys      Tue Jul 14 03:21:15 2009 (4A5BC16B)
fffff880`02d96000 fffff880`02daa000   termdd   termdd.sys   Tue Jul 14 04:16:36 2009 (4A5BCE64)
fffff960`00540000 fffff960`0054a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03ef7000 fffff880`03f1d000   tunnel   tunnel.sys   Tue Jul 14 04:09:37 2009 (4A5BCCC1)
fffff880`040f8000 fffff880`0410a000   umbus    umbus.sys    Tue Jul 14 04:06:56 2009 (4A5BCC20)
fffff880`04b56000 fffff880`04b73000   usbccgp  usbccgp.sys  Tue Jul 14 04:06:45 2009 (4A5BCC15)
fffff880`04b73000 fffff880`04b74f00   USBD     USBD.SYS     Tue Jul 14 04:06:23 2009 (4A5BCBFF)
fffff880`0fe1d000 fffff880`0fe2e000   usbehci  usbehci.sys  Tue Jul 14 04:06:30 2009 (4A5BCC06)
fffff880`0410a000 fffff880`04164000   usbhub   usbhub.sys   Tue Jul 14 04:07:09 2009 (4A5BCC2D)
fffff880`03f6c000 fffff880`03fc2000   USBPORT  USBPORT.SYS  Tue Jul 14 04:06:31 2009 (4A5BCC07)
fffff880`00f5b000 fffff880`00f68000   vdrvroot vdrvroot.sys Tue Jul 14 04:01:31 2009 (4A5BCADB)
fffff880`01960000 fffff880`0196e000   vga      vga.sys      Tue Jul 14 03:38:47 2009 (4A5BC587)
fffff880`0196e000 fffff880`01993000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 03:38:51 2009 (4A5BC58B)
fffff880`014d5000 fffff880`014e5000   vmstorfl vmstorfl.sys Tue Jul 14 03:42:54 2009 (4A5BC67E)
fffff880`00f7d000 fffff880`00f92000   volmgr   volmgr.sys   Tue Jul 14 03:19:57 2009 (4A5BC11D)
fffff880`00f92000 fffff880`00fee000   volmgrx  volmgrx.sys  Tue Jul 14 03:20:33 2009 (4A5BC141)
fffff880`01073000 fffff880`010bf000   volsnap  volsnap.sys  Tue Jul 14 03:20:08 2009 (4A5BC128)
fffff880`02d7b000 fffff880`02d96000   wanarp   wanarp.sys   Tue Jul 14 04:10:21 2009 (4A5BCCED)
fffff880`01993000 fffff880`019a3000   watchdog watchdog.sys Tue Jul 14 03:37:35 2009 (4A5BC53F)
fffff880`00e0b000 fffff880`00eaf000   Wdf01000 Wdf01000.sys Tue Jul 14 03:22:07 2009 (4A5BC19F)
fffff880`00eaf000 fffff880`00ebe000   WDFLDR   WDFLDR.SYS   Tue Jul 14 03:19:54 2009 (4A5BC11A)
fffff880`02d20000 fffff880`02d29000   wfplwf   wfplwf.sys   Tue Jul 14 04:09:26 2009 (4A5BCCB6)
fffff960`00070000 fffff960`00380000   win32k   win32k.sys   unavailable (00000000)
fffff880`00f15000 fffff880`00f1e000   WMILIB   WMILIB.SYS   Tue Jul 14 03:19:51 2009 (4A5BC117)
fffff880`02d15000 fffff880`02d20000   ws2ifsl  ws2ifsl.sys  Tue Jul 14 04:10:33 2009 (4A5BCCF9)
fffff880`03b35000 fffff880`03b56000   WudfPf   WudfPf.sys   Tue Jul 14 04:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`05932000 fffff880`059a3000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00071000
fffff880`018cb000 fffff880`018d9000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`018d9000 fffff880`018e5000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`018e5000 fffff880`018ee000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`018ee000 fffff880`01901000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
 


Upvote 0 Downvote
Hi Cybercore,

Thanks for the quick reply.. I checked Link Removed , but it showed that my drivers are all updated and nothing there that says "Intel Management Engine Interface". I guess there is no download for my board there. I googled it though and found this link
Link Removed due to 404 Error
- its a driver dated Sep 17, 2009 and its version 6.0.0.1179. Do you suggest i update to that? Can you tell me what version and date my current driver for "Intel Management Engine Interface" is to see which is the latest. I bought my board around December 2010 but I know drivers are sometimes outdated :-/

* I ran sfc /scannow and found nothing

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

** I still have to run the HDD test. I also dont know how to get the RamMon report.
 


Upvote 0 Downvote
Your memory looks good, the settings are right and the sticks are identical.
DDR1333 9-9-9-24 1.5v
The only possible inconsistency might be that the sticks are not from the same batch:

Slot#1
99U5471-002.A00LF
Week 1 of Year 2011


Slot# 2
99U5471-002.A00LF
Week 36 of Year 2010


If your HDD is fine, reinstall the system. It'll fix nothing, but if your PC keeps crashing after the reinstall, then remove one of the sticks and test RAM per stick and try each in different slots.

You may also want to load defaults in the bios.
 


Upvote 0 Downvote
hi. BIOS settings are already set to default already :(

before I was using PQI DDR3 memory and i thought I need to replace that so i did. I bought another Kingston 2gb which is what i'm using right now. but before that, I ran my PC using 1 stick and it still crashed. Let me try it again and I'll see what happens.. Thanks for the help :D
 


Upvote 0 Downvote
yep.. i have intel DH55PJ. Mainly supports core i3 and DDR3.. i got couple of blue sceens and they are getting worse each time.. more frequent. I'll reload my OS as soon as i get a hold of an external HDD. I'll get one maybe this Wednesday.
 


Upvote 0 Downvote
Hey.. I reformatted my PC and loaded programs as well but not all that I have to narrow the issue down. I got 2 crashes consecutive. they both point out to "intelppm.sys". The only Intel manufactured component I have is my board and my processor. Please see attached dump files. Thanks.

Link Removed
 


Upvote 0 Downvote
BTW. I ran MEMTEST again and both my sticks passed. 1 stick I ran for 31 Passes. and 8 Passes for the other stick. Before I got the new crash, I used only 1 (2gb) stick in 1 slot and everything was fine. I transferred the same stick to the other slot and worked good for a while until just now when my PC crashed. I transferred the stick back to the first slot and after a while, it still gave me the same crash. I'll still comtinue running the test in my PC to narrow down the issue. Do you know another program that can test the board or maybe the memory slots and stress test for RAM?

Thanks.
 


Upvote 0 Downvote
Have you disabled driver verifier??

cmd > verifier.exe /reset

Attach your latest crash dump.
 


Upvote 0 Downvote
Link Removed --->> Attached are my latest crashes

Run a full memtest 38 passes for more than 15 hours. Never got an error.
I am suspecting this might be related to my HDD. Dumps are not really clear to me as well but i remember getting an error about ATAPI.SYS, or something like that. I lost the dump file though after running CCleaner. If its not the HDD, could be my board :( , which makes me really wish its my HDD since HDD can just be swapped off the store where I bought my Parts. They said though that if its my board, they will have to ship it somewhere else and will take 3-4 weeks ETA. sucks.! Can MOBO really be repaired? parts are too small though and might not be good as new after :-/

I will reimage my OS to an external HDD and boot from there. If it works then problem could be with the HDD right?

Thanks again for the help and sorry for the long message :D
 


Upvote 0 Downvote
Hey Cyber.. Thanks so much for your help. I got a brand new HDD. I returned my HDD hoping that it was the issue. They said that it'll take 3 weeks for me to get a replacement so while waiting, I bought a new WD HDD. I installed OS and everything seems to working fine. Will keep you posted but I hope I wont get another crash. Seems like it was a faulty HDD from the start :D
 


Upvote 0 Downvote
Solution
You must log in or register to reply here.

Similar threads

FLAM3playZ
  • Solved
Windows 10 How to fix frequent BSODs caused by nvlddmkm.sys, ntoskrnl.exe and win32kbase.sys? (PLEASE HELP ANYONE)
Replies
12
Views
5K
kemical
kemical
T
  • Solved
Windows 10 Getting Frequent Blue Screen/Restart/Freeze on new computer(with Dump)
Replies
9
Views
2K
kemical
kemical
BobDobalina
  • Solved
Windows 10 Horror-PC with new BSOD and alot of other weird problems
Replies
3
Views
1K
Neemobeer
Neemobeer
V
  • Solved
Windows 10 BSOD win 10 VIDEO_TDR_FAILURE (116) need help please
Replies
1
Views
3K
kemical
kemical
M
  • Solved
Windows 10 Frequent BSOD for over 1.5 years have recently replaced my RAM, PSU and Motherboard to no avail. Looking for help/advice.
Replies
3
Views
3K
kemical
kemical
Back
Top