Hello all, it's me again. I I fixed one problem only to get another. Would someone be so kind as to look at my dump file and tell me what drive is making my system so angry with me. I think it's the wireless card but can't tell. I don't think I have the card it thinks I have.
Thanks so much for your time.
HP G60 Laptop Intel Dual Core
These were caused by your hardware please read here for what it means and what to try
Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try
Thanks
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\New folder\011311-19406-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Thu Jan 13 20:28:07.802 2011 (GMT-5)
System Uptime: 0 days 3:55:08.862
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {617ce02, 2, 1, fffff880045a1532}
Probably caused by : hardware ( hidusb!HumReadReport+13f )
Followup: MachineOwner
---------
1: 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: 000000000617ce02, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880045a1532, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc30e0
000000000617ce02
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Core_AllocTransferEx+3e2
fffff880`045a1532 c70266890248 mov dword ptr [rdx],48028966h
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002f1b330 -- (.trap 0xfffff88002f1b330)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000008348c7bf rbx=0000000000000000 rcx=000000000000000f
rdx=000000000617ce02 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880045a1532 rsp=fffff88002f1b4c0 rbp=0000000000000000
r8=0000000000000000 r9=fffffa800617cc30 r10=fffff880009e8b80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
USBPORT!USBPORT_Core_AllocTransferEx+0x3e2:
fffff880`045a1532 c70266890248 mov dword ptr [rdx],48028966h ds:00000000`0617ce02=????????
Resetting default scope
MISALIGNED_IP:
USBPORT!USBPORT_Core_AllocTransferEx+3e2
fffff880`045a1532 c70266890248 mov dword ptr [rdx],48028966h
LAST_CONTROL_TRANSFER: from fffff80002a8aca9 to fffff80002a8b740
STACK_TEXT:
fffff880`02f1b1e8 fffff800`02a8aca9 : 00000000`0000000a 00000000`0617ce02 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b1f0 fffff800`02a89920 : fffffa80`00000000 fffffa80`0617cc30 00000000`08600000 fffffa80`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b330 fffff880`045a1532 : fffffa80`0617cc30 00000000`00000000 fffffa80`03d69ad0 fffffa80`05161158 : nt!KiPageFault+0x260
fffff880`02f1b4c0 fffff880`045b11c4 : fffffa80`05160050 fffffa80`00000380 fffffa80`04724940 fffffa80`0514dc60 : USBPORT!USBPORT_Core_AllocTransferEx+0x3e2
fffff880`02f1b550 fffff880`045b9d44 : fffffa80`0514dc60 fffffa80`057b0009 fffffa80`0514dc60 fffffa80`03d69ad0 : USBPORT!USBPORT_ProcessURB+0x944
fffff880`02f1b600 fffff880`04593ad4 : 00000000`00000000 fffffa80`057b9050 fffffa80`0488dc30 fffffa80`0514dc60 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff880`02f1b640 fffff880`04edf566 : fffffa80`057bb050 fffffa80`049e7060 fffffa80`0514dc60 fffffa80`057bb1a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff880`02f1b680 fffff880`04f0fcab : 00000000`00000000 00000000`00000000 fffffa80`049e7060 00000000`00000801 : usbhub!UsbhFdoUrbPdoFilter+0xde
fffff880`02f1b6b0 fffff880`04eddfb7 : fffffa80`059a6a18 00000000`00000000 fffffa80`0514dc60 fffffa80`047f7b58 : usbhub!UsbhPdoInternalDeviceControl+0x373
fffff880`02f1b700 fffff880`06021ec4 : 00000000`00000000 fffffa80`047f7c58 00000000`00000002 fffffa80`0514dc60 : usbhub!UsbhGenDispatch+0x57
fffff880`02f1b730 fffff880`0601e812 : fffffa80`059a6a18 fffffa80`0514dc60 fffffa80`00000324 fffffa80`0514dc60 : usbccgp!UsbcForwardIrp+0x30
fffff880`02f1b760 fffff880`0601eaba : fffffa80`047f7b58 00000000`00220003 fffffa80`0514dc60 fffffa80`059a6a18 : usbccgp!DispatchPdoUrb+0xfa
fffff880`02f1b7a0 fffff880`0601c72e : 00000000`0000000f fffffa80`059a6a10 fffffa80`059a6a18 fffffa80`0514dc60 : usbccgp!DispatchPdoInternalDeviceControl+0x17a
fffff880`02f1b7d0 fffff880`077df48f : fffffa80`059a68c0 fffffa80`0514dc01 00000000`00000000 00000000`000007ff : usbccgp!USBC_Dispatch+0x2de
fffff880`02f1b850 fffff880`077def5b : fffffa80`0514dee0 fffffa80`059f4c01 fffff880`02f1b910 fffffa80`059f4b40 : hidusb!HumReadReport+0x13f
fffff880`02f1b8a0 fffff880`0760465d : fffffa80`05a76301 fffffa80`05a763d0 fffffa80`0514dc60 00000000`00000006 : hidusb!HumInternalIoctl+0x137
fffff880`02f1b910 fffff880`07604e7d : fffffa80`05a763d0 fffffa80`059f4cb0 00000000`00000000 00000000`00000006 : HIDCLASS!HidpSubmitInterruptRead+0xdd
fffff880`02f1b970 fffff800`02a8dd26 : fffffa80`0514dee3 00000000`00000000 fffffa80`059f4b01 fffffa80`0514dc00 : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff880`02f1ba00 fffff880`045a25d9 : fffffa80`05160050 fffffa80`03d69a00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f1bae0 fffff880`045a2ab7 : fffffa80`061f7302 fffffa80`0514dc60 00000000`ffffffff fffffa80`05160ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f1bbc0 fffff880`045a064f : fffffa80`05160ea8 fffffa80`051601a0 fffffa80`05161040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f1bc20 fffff880`04591f89 : fffffa80`05160050 00000000`00000000 fffffa80`05160e02 fffffa80`05160ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f1bc60 fffff800`02a96bfc : fffff880`009e8180 fffffa80`05160ea8 fffffa80`05160ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bc90 fffff800`02a93eea : fffff880`009e8180 fffff880`009f2f40 00000000`00000000 fffff880`04591db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
hidusb!HumReadReport+13f
fffff880`077df48f 488b4c2460 mov rcx,qword ptr [rsp+60h]
SYMBOL_STACK_INDEX: e
SYMBOL_NAME: hidusb!HumReadReport+13f
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
---------
Also these drivers are acting up and should be updated/re-installed
athrx.sys your atheros wifi driver.. Your realtec lan driver Rt64win7.sys.
ken J