Problem Devices:
Code:
ehdrv ROOT \ LEGACY_EHDRV \ 0000 This device is not present, not working properly, or does not have all its drivers installed.
epfwwfp ROOT \ LEGACY_EPFWWFP \ 0000 This device is not present, not working properly, or does not have all its drivers installed.
Security Processor Loader Driver ROOT \ LEGACY_SPLDR \ 0000 This device is not present, not working properly, or does not have all its drivers installed.
If you are running in Safe Mode during the generation of the crash report, the above are normal and not of concern.
Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\VAB\Windows_NT6_BSOD_jcgriff2\042312-19390-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c8d650
Debug session time: Mon Apr 23 05:31:42.261 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:24.635
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 : amdppm.sys ( amdppm!ReadIoMemRaw+30 )
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:
+6438353135303237
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: fffff88002f8d8e8 -- (.exr 0xfffff88002f8d8e8)
ExceptionAddress: fffff880045d26e4 (amdppm!ReadIoMemRaw+0x0000000000000030)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000fe11000414
Attempt to write to address 000000fe11000414
TRAP_FRAME: fffff88002f8d990 -- (.trap 0xfffff88002f8d990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000815
rdx=0000000000000815 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880045d26e4 rsp=fffff88002f8db28 rbp=0000000000000000
r8=0000000000000008 r9=fffffa8004f10588 r10=0000000000025d02
r11=fffff88002f8daa0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
amdppm!ReadIoMemRaw+0x30:
fffff880`045d26e4 0fb6c0 movzx eax,al
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002abd67e to fffff80002ac5c50
STACK_TEXT:
fffff880`02f8c9c8 fffff800`02abd67e : 00000000`00000000 fffff880`01598892 fffff880`02f8d140 fffff800`02af0c80 : nt!KeBugCheck
fffff880`02f8c9d0 fffff800`02af094d : fffff800`02cce488 fffff800`02c0c84c fffff800`02a49000 fffff880`02f8d8e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8ca00 fffff800`02aef725 : fffff800`02c0efac fffff880`02f8ca78 fffff880`02f8d8e8 fffff800`02a49000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8ca30 fffff800`02b006a1 : fffff880`02f8d8e8 fffff880`02f8d140 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff880`02f8d110 fffff800`02ac5302 : fffff880`02f8d8e8 00000000`00000001 fffff880`02f8d990 fffff880`02f65180 : nt!KiDispatchException+0x135
fffff880`02f8d7b0 fffff800`02ac3e7a : 00000000`00000001 000000fe`11000414 00000000`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`02f8d990 fffff880`045d26e4 : fffff880`045d272d fffffa80`04e5e020 fffff880`03ea45c1 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`02f8db28 fffff880`045d272d : fffffa80`04e5e020 fffff880`03ea45c1 00000000`00000000 fffffa80`04f69480 : amdppm!ReadIoMemRaw+0x30
fffff880`02f8db30 fffff800`02ace809 : 00000000`003165ae fffffa80`04f12dd0 00000000`00000000 00000000`00000000 : amdppm!ReadGenAddr+0x21
fffff880`02f8db60 fffff800`02abd95c : fffff880`02f65180 fffff880`00000001 00000000`00000000 fffff880`00000000 : nt!PoIdle+0x52a
fffff880`02f8dc40 00000000`00000000 : fffff880`02f8e000 fffff880`02f88000 fffff880`02f8dc00 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
amdppm!ReadIoMemRaw+30
fffff880`045d26e4 0fb6c0 movzx eax,al
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: amdppm!ReadIoMemRaw+30
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: amdppm
IMAGE_NAME: amdppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd
FAILURE_BUCKET_ID: X64_0x1E_0_amdppm!ReadIoMemRaw+30
BUCKET_ID: X64_0x1E_0_amdppm!ReadIoMemRaw+30
Followup: MachineOwner
---------
The above crash indicates your processor as the fault. This is likely due to corrupt data based on the bugcheck code itself. - If you are overclocking any hardware, please stop.
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Quote