Antivirus software:
Code:
avastsvc.exe c:\program files\avast software\avast\avastsvc.exe 1296 8 200 1380 25/02/2012 01:05 6.0.1367.0 43.72 KB (44,768 bytes) 15/02/2012 17:21
avastui.exe c:\program files\avast software\avast\avastui.exe 3692 8 200 1380 25/02/2012 01:05 6.0.1367.0 3.57 MB (3,744,552 bytes) 15/02/2012 17:21
Possible unstable device:
Code:
[01]: TP-LINK Wireless USB Adapter
Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\022512-29562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c47670
Debug session time: Fri Feb 24 18:04:48.154 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:11.746
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80073ba8f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80073ba8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031bd6f0 fffff800`02cc4c59 : fffffa80`073ba8d0 fffffa80`06427680 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`02ba4f57 : fffffa80`073ba8d0 fffff800`02c1f2b8 fffffa80`06427680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`02b0c5d5 : fffff800`02c80ae0 00000000`00000001 fffffa80`073b9820 fffffa80`06427680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`02a89001 : fffff880`00c3be00 fffff800`02b0c5b0 fffffa80`06427600 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`02d19fee : 00000000`00000000 fffffa80`06427680 00000000`00000080 fffffa80`0639d9e0 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`02a705e6 : fffff880`02f64180 fffffa80`06427680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd220 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\021912-15459-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c4f670
Debug session time: Sun Feb 19 13:18:10.462 2012 (UTC - 7:00)
System Uptime: 0 days 3:30:12.038
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff880043475cd}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSetState+35 )
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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880043475cd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb9100
0000000000000028
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iSetState+35
fffff880`043475cd 4c394a28 cmp qword ptr [rdx+28h],r9
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002f22d10 -- (.trap 0xfffff88002f22d10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043475cd rsp=fffff88002f22ea0 rbp=fffffa8007f06a00
r8=fffffa80075bd1a0 r9=0000000000000000 r10=00000000ffffffff
r11=fffffa80075bd1a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
USBPORT!USBPORT_Xdpc_iSetState+0x35:
fffff880`043475cd 4c394a28 cmp qword ptr [rdx+28h],r9 ds:ffff:00000000`00000028=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a861e9 to fffff80002a86c40
STACK_TEXT:
fffff880`02f22bc8 fffff800`02a861e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f22bd0 fffff800`02a84e60 : fffffa80`08cd1340 fffffa80`075bd101 00000000`00000002 fffffa80`075bdd28 : nt!KiBugCheckDispatch+0x69
fffff880`02f22d10 fffff880`043475cd : fffffa80`0771e418 00000000`00000022 00000000`00000000 00000000`ffffffff : nt!KiPageFault+0x260
fffff880`02f22ea0 fffff880`04347f89 : fffffa80`075bd050 00000000`00000000 fffffa80`075bdd02 fffffa80`075bdd28 : USBPORT!USBPORT_Xdpc_iSetState+0x35
fffff880`02f22ed0 fffff800`02a920ac : fffff880`009ea180 fffffa80`075bdd28 fffffa80`075bdd40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f22f00 fffff800`02a89765 : 00000000`00000000 fffffa80`07fc2b60 00000000`00000000 fffff880`04347db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f22fb0 fffff800`02a8957c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`02badff0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iSetState+35
fffff880`043475cd 4c394a28 cmp qword ptr [rdx+28h],r9
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iSetState+35
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c08
FAILURE_BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35
BUCKET_ID: X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35
Followup: MachineOwner
---------
- Still a stop 0x124.
- A USB related crash. Probably due to your network wireless USB adapter.
Stop 0x124 - what it means and what to try is still recommended. What were the results of the stress tests? Definitely do the RAM tests, as well. Underclocking your CPU may also mean the RAM settings are not configured properly.
Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)
Thanks to Dave76 for help learning RAM Stability
You could try USB Driver - General Fix for Problems to fix any USB driver related problems.
You could also try Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English) (works for all computers, not just HP Pavilions) to reset the USB ports themselves in case your USB ports entered a different power state to protect the system from a power surge.