Hey guys,
i have a problem with my acer veriton m460 running windows 7 ulitmate
it will run fine for hours then all of a sudden blue screen comes up and the restarts. then it will do it every 15mins or so or even within the 1st 5mins of start up
the code is 2057
and this is the mini dump files
This one was caused by hardware, specifically intelppm.sys, and HAL. The intel driver is either a VM driver or cpu. I would update the BIOS, ans run a system file check
type cmd in search>right click and run as admin>sfc /scannow.
If you are overclocking STOP
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\020810-16380-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82851000 PsLoadedModuleList = 0x82990570
Debug session time: Mon Feb 8 17:36:23.024 2010 (GMT-5)
System Uptime: 0 days 0:01:35.804
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {0, 0, 0, 0}
Probably caused by : intelppm.sys ( intelppm!GV3HardwareFeedback+3f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_0
TRAP_FRAME: 80ddeb54 -- (.trap 0xffffffff80ddeb54)
ErrCode = 00000000
eax=00000000 ebx=00000001 ecx=00000000 edx=00000000 esi=80ddec58 edi=84865fd4
eip=828a8d94 esp=80ddebc8 ebp=80ddebf8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!_aulldiv+0x14:
828a8d94 f7f1 div eax,ecx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 828a8d94 to 828875fb
STACK_TEXT:
80ddeb54 828a8d94 badb0d00 00000000 8717e310 nt!KiTrap00+0x8b
80ddebcc 8f1030a5 00000000 00000000 00000000 nt!_aulldiv+0x14
80ddebf8 8f104d2d 00000000 80dc2120 00000000 intelppm!GV3HardwareFeedback+0x3f
80ddec0c 8293bc2b 00000001 80dc2120 00000001 intelppm!PerfStatesFeedbackHandler+0x25
80ddec60 8293c25c 80dc5520 80dc7884 80dc3a00 nt!PpmPerfRecordUtility+0x1b8
80ddec78 828a6815 80dc5520 80dc2120 00000000 nt!PpmPerfAction+0x25
80ddecd4 828a6678 80dc2120 80dc7800 00000000 nt!KiExecuteAllDpcs+0xf9
80dded20 828a6498 00000000 0000000e 25c9bb02 nt!KiRetireDpcList+0xd5
80dded24 00000000 0000000e 25c9bb02 f80f183d nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm!GV3HardwareFeedback+3f
8f1030a5 80fb01 cmp bl,1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: intelppm!GV3HardwareFeedback+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07
FAILURE_BUCKET_ID: 0x7f_0_intelppm!GV3HardwareFeedback+3f
BUCKET_ID: 0x7f_0_intelppm!GV3HardwareFeedback+3f
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_0
TRAP_FRAME: 80ddeb54 -- (.trap 0xffffffff80ddeb54)
ErrCode = 00000000
eax=00000000 ebx=00000001 ecx=00000000 edx=00000000 esi=80ddec58 edi=84865fd4
eip=828a8d94 esp=80ddebc8 ebp=80ddebf8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!_aulldiv+0x14:
828a8d94 f7f1 div eax,ecx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 828a8d94 to 828875fb
STACK_TEXT:
80ddeb54 828a8d94 badb0d00 00000000 8717e310 nt!KiTrap00+0x8b
80ddebcc 8f1030a5 00000000 00000000 00000000 nt!_aulldiv+0x14
80ddebf8 8f104d2d 00000000 80dc2120 00000000 intelppm!GV3HardwareFeedback+0x3f
80ddec0c 8293bc2b 00000001 80dc2120 00000001 intelppm!PerfStatesFeedbackHandler+0x25
80ddec60 8293c25c 80dc5520 80dc7884 80dc3a00 nt!PpmPerfRecordUtility+0x1b8
80ddec78 828a6815 80dc5520 80dc2120 00000000 nt!PpmPerfAction+0x25
80ddecd4 828a6678 80dc2120 80dc7800 00000000 nt!KiExecuteAllDpcs+0xf9
80dded20 828a6498 00000000 0000000e 25c9bb02 nt!KiRetireDpcList+0xd5
80dded24 00000000 0000000e 25c9bb02 f80f183d nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm!GV3HardwareFeedback+3f
8f1030a5 80fb01 cmp bl,1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: intelppm!GV3HardwareFeedback+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07
FAILURE_BUCKET_ID: 0x7f_0_intelppm!GV3HardwareFeedback+3f
BUCKET_ID: 0x7f_0_intelppm!GV3HardwareFeedback+3f
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_0
TRAP_FRAME: 80ddeb54 -- (.trap 0xffffffff80ddeb54)
ErrCode = 00000000
eax=00000000 ebx=00000001 ecx=00000000 edx=00000000 esi=80ddec58 edi=84865fd4
eip=828a8d94 esp=80ddebc8 ebp=80ddebf8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!_aulldiv+0x14:
828a8d94 f7f1 div eax,ecx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 828a8d94 to 828875fb
STACK_TEXT:
80ddeb54 828a8d94 badb0d00 00000000 8717e310 nt!KiTrap00+0x8b
80ddebcc 8f1030a5 00000000 00000000 00000000 nt!_aulldiv+0x14
80ddebf8 8f104d2d 00000000 80dc2120 00000000 intelppm!GV3HardwareFeedback+0x3f
80ddec0c 8293bc2b 00000001 80dc2120 00000001 intelppm!PerfStatesFeedbackHandler+0x25
80ddec60 8293c25c 80dc5520 80dc7884 80dc3a00 nt!PpmPerfRecordUtility+0x1b8
80ddec78 828a6815 80dc5520 80dc2120 00000000 nt!PpmPerfAction+0x25
80ddecd4 828a6678 80dc2120 80dc7800 00000000 nt!KiExecuteAllDpcs+0xf9
80dded20 828a6498 00000000 0000000e 25c9bb02 nt!KiRetireDpcList+0xd5
80dded24 00000000 0000000e 25c9bb02 f80f183d nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
intelppm!GV3HardwareFeedback+3f
8f1030a5 80fb01 cmp bl,1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: intelppm!GV3HardwareFeedback+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07
FAILURE_BUCKET_ID: 0x7f_0_intelppm!GV3HardwareFeedback+3f
BUCKET_ID: 0x7f_0_intelppm!GV3HardwareFeedback+3f
Followup: MachineOwner
---------