Re: mouse crawled to snail's-pace and unresponsive, bsod with driver verifier
Not that I don't appreciate all the work you do griff. But You really should create a doc that allows users to read their own output so that they learn more about how to diagnose, and you don't have to go through so many yourself. They could still the analysts here as a last resort. I worry you all give too much
Re: mouse crawled to snail's-pace and unresponsive, bsod with driver verifier
You're welcome. I hope you remain BSOD-free.
Unfortunately, there is no master checklist because of the many variables involved.
Debugging Tools for Windows is really for driver developers and Microsoft Crash Control Escalation. Forums have adapted its use for the end-user side to the best of our ability. Also when hardware failure enters the picture, the results found in BSOD dump logs can be misleading -- you have failing hardware interacting with the OS, which can produce an unreliable dump file.
I learned what I know on my own, starting in late 2007 -- quite accidentally. Then, I got hooked.
I just had the problem again. What it does is that the mouse crawls to where it's moving every 20 seconds, the screen tries to reset, ctrl+alt+del does nothing (well it might) but it takes so long to even try and enter the screen that it basically does nothing. There is no BSOD, and no minidump. I ran driver verifier to induce a BSOD and here are the results of the script and perfmon:
[font=lucida console]HD-Hypervisor-amd64.sys Mon Oct 10 17:58:16 2011 (4E936A78)[/font]
It may belong to Linux or other OS; not sure.
I suggest removal.
Regards. . .
jcgriff2
`
BSOD SUMMARY
Code:
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\101411-21793-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Oct 14 13:31:04.133 2011 (GMT-4)
System Uptime: 0 days 0:00:52.866
BugCheck D1, {fffff98057732ee0, 2, 1, fffff88008c29c66}
*** WARNING: Unable to verify timestamp for HD-Hypervisor-amd64.sys
*** ERROR: Module load completed but symbols could not be loaded for HD-Hypervisor-amd64.sys
Probably caused by : HD-Hypervisor-amd64.sys ( HD_Hypervisor_amd64+5c66 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_HD_Hypervisor_amd64+5c66
Bugcheck code 000000D1
Arguments fffff980`57732ee0 00000000`00000002 00000000`00000001 fffff880`08c29c66
BiosVersion = P1.70
BiosReleaseDate = 06/22/2011
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed: 3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
Code:
[font=lucida console]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\101411-21793-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*a:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0344a000 PsLoadedModuleList = 0xfffff800`0368f670
Debug session time: Fri Oct 14 13:31:04.133 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:52.866
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff98057732ee0, 2, 1, fffff88008c29c66}
Unable to load image HD-Hypervisor-amd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HD-Hypervisor-amd64.sys
*** ERROR: Module load completed but symbols could not be loaded for HD-Hypervisor-amd64.sys
Probably caused by : HD-Hypervisor-amd64.sys ( HD_Hypervisor_amd64+5c66 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff98057732ee0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88008c29c66, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036f9100
fffff98057732ee0
CURRENT_IRQL: 2
FAULTING_IP:
HD_Hypervisor_amd64+5c66
fffff880`08c29c66 488939 mov qword ptr [rcx],rdi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88003585570 -- (.trap 0xfffff88003585570)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff98057732ee0
rdx=fffff88008c351e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008c29c66 rsp=fffff88003585700 rbp=0000000000000000
r8=fffffa800cdaf040 r9=0000000000000000 r10=fffff88003585860
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
HD_Hypervisor_amd64+0x5c66:
fffff880`08c29c66 488939 mov qword ptr [rcx],rdi ds:aff0:fffff980`57732ee0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034c61e9 to fffff800034c6c40
STACK_TEXT:
fffff880`03585428 fffff800`034c61e9 : 00000000`0000000a fffff980`57732ee0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03585430 fffff800`034c4e60 : 00000000`00000003 00000000`00000010 00000000`00000003 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03585570 fffff880`08c29c66 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000007db : nt!KiPageFault+0x260
fffff880`03585700 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`000007db 00000000`0000000a : HD_Hypervisor_amd64+0x5c66
STACK_COMMAND: kb
FOLLOWUP_IP:
HD_Hypervisor_amd64+5c66
fffff880`08c29c66 488939 mov qword ptr [rcx],rdi
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: HD_Hypervisor_amd64+5c66
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HD_Hypervisor_amd64
IMAGE_NAME: HD-Hypervisor-amd64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e936a78
FAILURE_BUCKET_ID: X64_0xD1_HD_Hypervisor_amd64+5c66
BUCKET_ID: X64_0xD1_HD_Hypervisor_amd64+5c66
Followup: MachineOwner
---------
3: kd> lmvm HD_Hypervisor_amd64
start end module name
fffff880`08c24000 fffff880`08c39000 HD_Hypervisor_amd64 T (no symbols)
Loaded symbol image file: HD-Hypervisor-amd64.sys
Image path: HD-Hypervisor-amd64.sys
Image name: HD-Hypervisor-amd64.sys
Timestamp: Mon Oct 10 17:58:16 2011 (4E936A78)
CheckSum: 0001FE20
ImageSize: 00015000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
[/font]
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Forum
4.7M posts
957.9K members
Since 2002
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!