recurring BSOD at random, various error codes?

swaggatron · Dec 29, 2011

Someone gave me this computer for Christmas, brand new and in box and everything. I was told all the installations and configurations was already done for me (to accommodate the fact that I'm not very good with computers).

The first time I started it up, I got the error screen just from accidentally opening Internet Explorer. I figured maybe I didn't plug something in right, so I double-checked and everything looked fine. The anti-virus (I use AVG) didn't detect anything suspicious. I checked that all the programs could run smoothly. I did a system health check. Checked device manager to make sure my computer wasn't connected to something that might cause problems. After doing all that, all I got a handful of errors, and two more bluescreens. I even did an error check (took 4 hours by the way, not doing that again), it said there was nothing wrong.

But since then, it's been giving me bluescreens no matter what I do. The error codes weren't always the same and sometimes it would tell me BAD_POOL_ERROR and stuff, but most times it doesn't.

The good side is that the computer always boots up and works fine (up until the bluescreen). The bad side is that even if I don't do anything, it will eventually give me an error page. Like today, it gave me a bluescreen when I wasn't even logged on, and no programs were running.

I'm all out of ideas, and I really don't feel like dragging this back to the store. Is there a way to fix it myself? I checked the posting instruction and downloaded the BSOD Dump File and Collection App but haven't had a chance to run it yet. I'll post that in a bit, but if anyone could help me now, that'd be nice. Thank you.

writhziden · Dec 29, 2011

Hello swaggatron, welcome to SevenForums. Once you are able to get the blue screen error information, we will be able to assist you. Hopefully it is something simple that we can help you sort out.

swaggatron · Dec 29, 2011

Hopefully, I did this correctly. $:

writhziden · Dec 29, 2011

Code:

[list=1]
[*]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122511-24554-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02c15000 PsLoadedModuleList = 0xfffff800`02e5a670
Debug session time: Sun Dec 25 09:25:42.750 2011 (UTC - 7:00)
System Uptime: 0 days 0:43:04.435
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}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+58d )

Followup: MachineOwner
---------

3: 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: 
+6261303161633763
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:  2

EXCEPTION_RECORD:  fffff88002ffb138 -- (.exr 0xfffff88002ffb138)
ExceptionAddress: fffff8800614ebf1 (nwifi!Pt6RepackRecvNBL+0x000000000000058d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffb1e0 -- (.trap 0xfffff88002ffb1e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=3fa2ecd0036177a8 rbx=0000000000000000 rcx=00000000000005fc
rdx=fffff88002ffb3e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800614ebf1 rsp=fffff88002ffb370 rbp=fffffa8003f4d01c
 r8=0000000000000000  r9=0000000000000000 r10=fffff88006184110
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nwifi!Pt6RepackRecvNBL+0x58d:
fffff880`0614ebf1 488b00          mov     rax,qword ptr [rax] ds:a870:3fa2ecd0`036177a8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c895fe to fffff80002c91c10

STACK_TEXT:  
fffff880`02ffa218 fffff800`02c895fe : ffff0000`038600a8 00000000`00000000 fffff880`02ffa990 fffff800`02cbd830 : nt!KeBugCheck
fffff880`02ffa220 fffff800`02cbd4fd : fffff800`02e9b71c fffff800`02dd8c30 fffff800`02c15000 fffff880`02ffb138 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa250 fffff800`02cbc2d5 : fffff800`02ddc0fc fffff880`02ffa2c8 fffff880`02ffb138 fffff800`02c15000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa280 fffff800`02ccd361 : fffff880`02ffb138 fffff880`02ffa990 fffff880`00000000 fffffa80`00000005 : nt!RtlDispatchException+0x415
fffff880`02ffa960 fffff800`02c912c2 : fffff880`02ffb138 3fa2ecd0`036177a8 fffff880`02ffb1e0 fffff880`02ffb3e0 : nt!KiDispatchException+0x135
fffff880`02ffb000 fffff800`02c8fbca : 00000000`00000012 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb1e0 fffff880`0614ebf1 : 00000000`00000103 00000000`00000001 fffffa80`03e6d220 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb370 fffff880`0614f021 : fffffa80`051d4380 00000000`00000000 00000000`00000000 fffffa80`03f77010 : nwifi!Pt6RepackRecvNBL+0x58d
fffff880`02ffb3c0 fffff880`0614f6fc : fffffa80`03f77010 fffffa80`03f3fa62 fffffa80`00002a62 fffffa80`03f77010 : nwifi!Pt6RepackRecvNBL+0x9bd
fffff880`02ffb610 fffff880`015194f7 : fffffa80`03b051a0 fffffa80`03ea9310 00000000`00000001 fffffa80`03f40eb8 : nwifi!Pt6Receive+0x1a4
fffff880`02ffb670 fffff880`09eb4202 : 00000000`00000000 fffff880`00f84130 fffffa80`03b0c8a0 fffffa80`03b05000 : ndis! ?? ::FNODOBFM::`string'+0xcf1f
fffff880`02ffb6c0 00000000`00000000 : fffff880`00f84130 fffffa80`03b0c8a0 fffffa80`03b05000 fffffa80`00000001 : athrxusb+0x11202


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+58d
fffff880`0614ebf1 488b00          mov     rax,qword ptr [rax]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+58d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+58d

BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+58d

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122511-24195-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02c15000 PsLoadedModuleList = 0xfffff800`02e5a670
Debug session time: Sun Dec 25 11:12:04.617 2011 (UTC - 7:00)
System Uptime: 0 days 1:45:22.303
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8005d8a000, fffffa8005d8af30, 4f30000}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+106b6 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8005d8a000, The pool entry we were looking for within the page.
Arg3: fffffa8005d8af30, The next pool entry.
Arg4: 0000000004f30000, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec4100
 fffffa8005d8a000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dbfcae to fffff80002c91c40

STACK_TEXT:  
fffff880`031a8458 fffff800`02dbfcae : 00000000`00000019 00000000`00000020 fffffa80`05d8a000 fffffa80`05d8af30 : nt!KeBugCheckEx
fffff880`031a8460 fffff880`01508195 : 00000000`00000000 fffffa80`05b281a0 fffffa80`72614841 00000000`00000200 : nt!ExDeferredFreePool+0x12da
fffff880`031a8510 fffff880`06cc46b6 : 00000000`00000006 00000000`00000000 00000000`00000000 fffffa80`06ec9170 : ndis!NdisFreeMemory+0x15
fffff880`031a8540 00000000`00000006 : 00000000`00000000 00000000`00000000 fffffa80`06ec9170 fffffa80`05cf80c0 : athrxusb+0x106b6
fffff880`031a8548 00000000`00000000 : 00000000`00000000 fffffa80`06ec9170 fffffa80`05cf80c0 00000000`00000000 : 0x6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrxusb+106b6
fffff880`06cc46b6 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrxusb+106b6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrxusb

IMAGE_NAME:  athrxusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  488f1151

FAILURE_BUCKET_ID:  X64_0x19_20_athrxusb+106b6

BUCKET_ID:  X64_0x19_20_athrxusb+106b6

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122511-30498-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02c01000 PsLoadedModuleList = 0xfffff800`02e46670
Debug session time: Sun Dec 25 15:19:27.813 2011 (UTC - 7:00)
System Uptime: 0 days 2:43:33.515
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80039af680, fffff8000402f510}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : usbhub.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80039af680, The thread currently holding on to the Pnp lock.
Arg4: fffff8000402f510

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'AVGIDSFilter' and 'hiber_storpo' overlap

DRVPOWERSTATE_SUBCODE:  4

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15

MODULE_NAME: usbhub

FAULTING_MODULE: fffff880060ff000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`031b6070 fffff800`02c82f32 : fffffa80`039af680 fffffa80`039af680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`031b61b0 fffff800`02c8574f : 00000000`00000000 fffff880`0152c110 00000000`00000000 fffffa80`039af680 : nt!KiCommitThreadWait+0x1d2
fffff880`031b6240 fffff880`014d4992 : 00000000`00000000 fffff880`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`031b62e0 fffff880`06cc15cc : 00000000`00000000 fffff880`00000000 00000000`00000000 fffffa80`05bbe1a0 : ndis!NdisWaitEvent+0x32
fffff880`031b6320 00000000`00000000 : fffff880`00000000 00000000`00000000 fffffa80`05bbe1a0 fffff880`02f63180 : athrxusb+0x35cc


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_4_athrxusb_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_4_athrxusb_IMAGE_usbhub.sys

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122611-23400-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e01000 PsLoadedModuleList = 0xfffff800`03046670
Debug session time: Mon Dec 26 12:28:52.340 2011 (UTC - 7:00)
System Uptime: 0 days 1:29:33.025
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {99, fffffa8005f60f40, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+1068a )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000099, Attempt to free pool with invalid address  (or corruption in pool header)
Arg2: fffffa8005f60f40, Address being freed
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

Debugging Details:
------------------


BUGCHECK_STR:  0xc2_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033073dc to fffff80002e7dc40

STACK_TEXT:  
fffff880`009e77e8 fffff800`033073dc : 00000000`000000c2 00000000`00000099 fffffa80`05f60f40 00000000`00000000 : nt!KeBugCheckEx
fffff880`009e77f0 fffff800`02f2d6e1 : fffffa80`05ece620 00000000`00000100 00000000`00000000 00000000`000007ff : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009e7830 fffff800`02fabc73 : fffffa80`05f60f30 00000000`00000610 00000000`00000072 fffffa80`05ece618 : nt!VerifierFreeTrackedPool+0x41
fffff880`009e7870 fffff880`06c7268a : fffffa80`04392830 00000000`00000002 00000000`00000000 fffffa80`055bf970 : nt!ExDeferredFreePool+0x129f
fffff880`009e7920 fffffa80`04392830 : 00000000`00000002 00000000`00000000 fffffa80`055bf970 fffffa80`05ed21a0 : athrxusb+0x1068a
fffff880`009e7928 00000000`00000002 : 00000000`00000000 fffffa80`055bf970 fffffa80`05ed21a0 fffffa80`04392830 : 0xfffffa80`04392830
fffff880`009e7930 00000000`00000000 : fffffa80`055bf970 fffffa80`05ed21a0 fffffa80`04392830 00000000`00000006 : 0x2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrxusb+1068a
fffff880`06c7268a ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  athrxusb+1068a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrxusb

IMAGE_NAME:  athrxusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  488f1151

FAILURE_BUCKET_ID:  X64_0xc2_99_athrxusb+1068a

BUCKET_ID:  X64_0xc2_99_athrxusb+1068a

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122611-41106-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e67000 PsLoadedModuleList = 0xfffff800`030ac670
Debug session time: Mon Dec 26 14:35:45.404 2011 (UTC - 7:00)
System Uptime: 0 days 1:08:06.090
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80039b0680, fffff8000443f510}

Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80039b0680, The thread currently holding on to the Pnp lock.
Arg4: fffff8000443f510

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa80039b0680

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ee8f32 to fffff80002ee64da

STACK_TEXT:  
fffff880`031b6890 fffff800`02ee8f32 : fffffa80`039b0680 fffffa80`039b0680 00000000`00000000 00000000`00000003 : nt!KiSwapContext+0x7a
fffff880`031b69d0 fffff800`02eeb74f : 00000000`00000000 00000000`00000000 00000000`00000015 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`031b6a60 fffff800`02ec4872 : 00000000`00000000 fffff800`0000001b 00000000`00000000 fffff880`009e8100 : nt!KeWaitForSingleObject+0x19f
fffff880`031b6b00 fffff800`02ee9b6c : ffffffff`fd9da600 fffffa80`0566db10 fffff800`030e2b80 fffffa80`00000600 : nt!ExpWaitForResource+0xae
fffff880`031b6b70 fffff800`0321e6d2 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`031b6be0 fffff800`02fe0600 : 00000000`00000000 fffff800`030842b8 00000000`00000001 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1c44c
fffff880`031b6c10 fffff800`02eee001 : fffff800`02fe05c0 fffff800`031da901 fffffa80`039b0600 00000000`00000000 : nt!PnpDeviceActionWorker+0x40
fffff880`031b6cb0 fffff800`0317efee : 0065006c`00620061 fffffa80`039b0680 00000000`00000080 fffffa80`0399aae0 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02ed55e6 : fffff880`02f63180 fffffa80`039b0680 fffff880`02f6dfc0 0075006f`006b0063 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`09eb3540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa80039b0680 ; kb

FOLLOWUP_IP: 
nt!KiSwapContext+7a
fffff800`02ee64da 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiSwapContext+7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122711-27362-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e0d000 PsLoadedModuleList = 0xfffff800`03052670
Debug session time: Tue Dec 27 11:50:11.036 2011 (UTC - 7:00)
System Uptime: 0 days 0:04:38.722
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}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+58d )

Followup: MachineOwner
---------

3: 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: 
+6261303161633763
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:  2

EXCEPTION_RECORD:  fffff88002ffb138 -- (.exr 0xfffff88002ffb138)
ExceptionAddress: fffff88006608bf1 (nwifi!Pt6RepackRecvNBL+0x000000000000058d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffb1e0 -- (.trap 0xfffff88002ffb1e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=14c44d2328c6e5a0 rbx=0000000000000000 rcx=00000000000005fc
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006608bf1 rsp=fffff88002ffb370 rbp=fffff8800978001c
 r8=000000012c8c4000  r9=0000000000000000 r10=0000000000000000
r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nwifi!Pt6RepackRecvNBL+0x58d:
fffff880`06608bf1 488b00          mov     rax,qword ptr [rax] ds:d020:14c44d23`28c6e5a0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e815fe to fffff80002e89c10

STACK_TEXT:  
fffff880`02ffa218 fffff800`02e815fe : 00000000`00000000 00000000`00000000 fffff880`02ffa990 fffff800`02eb5830 : nt!KeBugCheck
fffff880`02ffa220 fffff800`02eb54fd : fffff800`0309371c fffff800`02fd0c30 fffff800`02e0d000 fffff880`02ffb138 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa250 fffff800`02eb42d5 : fffff800`02fd40fc fffff880`02ffa2c8 fffff880`02ffb138 fffff800`02e0d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa280 fffff800`02ec5361 : fffff880`02ffb138 fffff880`02ffa990 fffff880`00000000 fffffa80`00000005 : nt!RtlDispatchException+0x415
fffff880`02ffa960 fffff800`02e892c2 : fffff880`02ffb138 14c44d23`28c6e5a0 fffff880`02ffb1e0 fffff880`02ffb3e0 : nt!KiDispatchException+0x135
fffff880`02ffb000 fffff800`02e87bca : 00000000`00000012 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb1e0 fffff880`06608bf1 : fffffa80`06094f40 00000000`00000000 fffffa80`00000001 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb370 fffff880`06609021 : fffffa80`06780460 00000000`00000000 00000000`00000000 fffffa80`066ff010 : nwifi!Pt6RepackRecvNBL+0x58d
fffff880`02ffb3c0 fffff880`066096fc : fffffa80`066ff010 fffffa80`05fc341a fffffa80`0000041a fffffa80`066ff010 : nwifi!Pt6RepackRecvNBL+0x9bd
fffff880`02ffb610 fffff880`0144e4f7 : fffffa80`05fca1a0 fffffa80`060fb5f0 00000000`00000001 fffffa80`06090288 : nwifi!Pt6Receive+0x1a4
fffff880`02ffb670 fffff880`06a4d202 : 00000000`00000000 fffff880`00ea9130 fffffa80`0602cd60 fffffa80`05fca000 : ndis! ?? ::FNODOBFM::`string'+0xcf1f
fffff880`02ffb6c0 00000000`00000000 : fffff880`00ea9130 fffffa80`0602cd60 fffffa80`05fca000 fffffa80`00000001 : athrxusb+0x11202


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+58d
fffff880`06608bf1 488b00          mov     rax,qword ptr [rax]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+58d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+58d

BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+58d

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122711-26847-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e4d000 PsLoadedModuleList = 0xfffff800`03092670
Debug session time: Tue Dec 27 19:13:02.650 2011 (UTC - 7:00)
System Uptime: 0 days 7:21:57.945
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {99, fffffa800726df50, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000099, Attempt to free pool with invalid address  (or corruption in pool header)
Arg2: fffffa800726df50, Address being freed
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

Debugging Details:
------------------


FAULTING_IP: 
nt!ObfDereferenceObject+dc
fffff800`02ed3afc e95fffffff      jmp     nt!ObfDereferenceObject+0x40 (fffff800`02ed3a60)

BUGCHECK_STR:  0xc2_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033533dc to fffff80002ec9c40

STACK_TEXT:  
fffff880`07f579a8 fffff800`033533dc : 00000000`000000c2 00000000`00000099 fffffa80`0726df50 00000000`00000000 : nt!KeBugCheckEx
fffff880`07f579b0 fffff800`02f796e1 : 00000000`00000001 00000000`00000000 fffffa80`07727b60 fffff880`00961000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`07f579f0 fffff800`02ff7c73 : fffffa80`0726df40 00000000`00000000 00000000`0000005e 00000000`000000b8 : nt!VerifierFreeTrackedPool+0x41
fffff880`07f57a30 fffff800`02ed3afc : fffffa80`0726df80 fffffa80`07607b30 fffffa80`03a77350 fffffa80`0726df80 : nt!ExDeferredFreePool+0x129f
fffff880`07f57ae0 fffff800`031c0f44 : fffffa80`07607b30 00000000`00000000 fffffa80`07727b60 00000000`00000000 : nt!ObfDereferenceObject+0xdc
fffff880`07f57b40 fffff800`031c14f4 : 00000000`00000670 fffffa80`07607b30 fffff8a0`0d768890 00000000`00000670 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`07f57bd0 fffff800`02ec8ed3 : fffffa80`07727b60 fffff880`07f57ca0 00000000`fffdb000 00000000`0375c728 : nt!ObpCloseHandle+0x94
fffff880`07f57c20 00000000`76da140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0017df58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da140a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!VerifierBugCheckIfAppropriate+3c
fffff800`033533dc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xc2_99_nt!VerifierBugCheckIfAppropriate+3c

BUCKET_ID:  X64_0xc2_99_nt!VerifierBugCheckIfAppropriate+3c

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122811-33945-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e63000 PsLoadedModuleList = 0xfffff800`030a8670
Debug session time: Wed Dec 28 09:10:36.678 2011 (UTC - 7:00)
System Uptime: 0 days 9:02:02.363
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88001111039, 0, ffffffffffffffff}

Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : MpFilter.sys ( MpFilter+121c1 )

Followup: MachineOwner
---------

1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001111039, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'usbscan' and 'athrxusb.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`01111039 488b4820        mov     rcx,qword ptr [rax+20h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003112100
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f2b588 to fffff80002edfc40

STACK_TEXT:  
fffff880`0a7dc348 fffff800`02f2b588 : 00000000`0000001e ffffffff`c0000005 fffff880`01111039 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a7dc350 fffff800`02edf2c2 : fffff880`0a7dcb28 00000000`00000000 fffff880`0a7dcbd0 fffffa80`06724c80 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`0a7dc9f0 fffff800`02eddbca : fffffa80`0758fcb0 fffff880`011102ec fffffa80`06b0c3f8 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a7dcbd0 fffff880`01111039 : fffffa80`0478f010 00000000`00000000 fffff880`0a7dce10 fffff880`01110aae : nt!KiGeneralProtectionFault+0x10a
fffff880`0a7dcd60 fffff880`0111bdbe : fffffa80`06724c30 fffff880`0a7dce98 fffffa80`00000060 00000000`00000000 : fltmgr!GetContextFromStreamList+0x99
fffff880`0a7dcde0 fffff880`011dc1c1 : fffffa80`06724c30 fffffa80`0758fd60 00000000`00000000 fffff800`031de100 : fltmgr!FltGetStreamContext+0x3e
fffff880`0a7dce10 fffffa80`06724c30 : fffffa80`0758fd60 00000000`00000000 fffff800`031de100 00000000`00000004 : MpFilter+0x121c1
fffff880`0a7dce18 fffffa80`0758fd60 : 00000000`00000000 fffff800`031de100 00000000`00000004 fffffa80`03aeacc8 : 0xfffffa80`06724c30
fffff880`0a7dce20 00000000`00000000 : fffff800`031de100 00000000`00000004 fffffa80`03aeacc8 00000000`00000000 : 0xfffffa80`0758fd60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MpFilter+121c1
fffff880`011dc1c1 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  MpFilter+121c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MpFilter

IMAGE_NAME:  MpFilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9cc801

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_MpFilter+121c1

BUCKET_ID:  X64_0x1E_c0000005_MpFilter+121c1

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122811-33587-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e4c000 PsLoadedModuleList = 0xfffff800`03091670
Debug session time: Wed Dec 28 16:16:10.882 2011 (UTC - 7:00)
System Uptime: 0 days 0:14:38.567
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}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+103 )

Followup: MachineOwner
---------

3: 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: 
+6261303161633763
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:  2

EXCEPTION_RECORD:  fffff88002ffb2d8 -- (.exr 0xfffff88002ffb2d8)
ExceptionAddress: fffff88005608767 (nwifi!Pt6RepackRecvNBL+0x0000000000000103)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffb380 -- (.trap 0xfffff88002ffb380)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005ecd7d0 rbx=0000000000000000 rcx=fffff880056406e0
rdx=fffffa8005ed0f40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005608767 rsp=fffff88002ffb510 rbp=0000000000000000
 r8=0000000000000000  r9=41c28faa5087f58e r10=fffff8800563e110
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nwifi!Pt6RepackRecvNBL+0x103:
fffff880`05608767 450fb701        movzx   r8d,word ptr [r9] ds:41c28faa`5087f58e=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec05fe to fffff80002ec8c10

STACK_TEXT:  
fffff880`02ffa3b8 fffff800`02ec05fe : fffffa80`03f6c200 fffff800`02eda89c fffff880`02ffab30 fffff800`02ef4830 : nt!KeBugCheck
fffff880`02ffa3c0 fffff800`02ef44fd : fffff800`030d271c fffff800`0300fc30 fffff800`02e4c000 fffff880`02ffb2d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa3f0 fffff800`02ef32d5 : fffff800`030130fc fffff880`02ffa468 fffff880`02ffb2d8 fffff800`02e4c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa420 fffff800`02f04361 : fffff880`02ffb2d8 fffff880`02ffab30 fffff880`00000000 fffffa80`05ecd230 : nt!RtlDispatchException+0x415
fffff880`02ffab00 fffff800`02ec82c2 : fffff880`02ffb2d8 00000000`00000000 fffff880`02ffb380 fffffa80`065ea010 : nt!KiDispatchException+0x135
fffff880`02ffb1a0 fffff800`02ec6bca : fffffa80`05dd6048 fffffa80`00000001 fffff880`02ffb3e0 fffffa80`04807890 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb380 fffff880`05608767 : 00000000`00000000 00000000`00000000 fffffa80`065ea010 fffff800`02e0ab7f : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb510 fffff880`056096c8 : fffffa80`05e4c030 fffffa80`05cafa62 fffffa80`00002a62 fffffa80`065ea010 : nwifi!Pt6RepackRecvNBL+0x103
fffff880`02ffb610 fffff880`0143f4f7 : fffffa80`05d9b1a0 fffffa80`05ecd230 00000000`00000001 fffffa80`05e44cc8 : nwifi!Pt6Receive+0x170
fffff880`02ffb670 fffff880`01edf202 : 00000000`00000000 fffff880`00f27130 fffffa80`05de9570 fffffa80`05d9b000 : ndis! ?? ::FNODOBFM::`string'+0xcf1f
fffff880`02ffb6c0 00000000`00000000 : fffff880`00f27130 fffffa80`05de9570 fffffa80`05d9b000 fffffa80`00000001 : athrxusb+0x11202


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+103
fffff880`05608767 450fb701        movzx   r8d,word ptr [r9]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+103

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+103

BUCKET_ID:  X64_0x1E_0_nwifi!Pt6RepackRecvNBL+103

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122811-31715-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e66000 PsLoadedModuleList = 0xfffff800`030ab670
Debug session time: Wed Dec 28 17:02:46.304 2011 (UTC - 7:00)
System Uptime: 0 days 0:46:01.615
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80039ca680, fffff80000b9c510}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : usbhub.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80039ca680, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15

MODULE_NAME: usbhub

FAULTING_MODULE: fffff88003e00000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`031b6070 fffff800`02ee7f32 : fffffa80`039ca680 fffffa80`039ca680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`031b61b0 fffff800`02eea74f : 00000000`00000000 fffff880`014cc110 00000000`00000000 fffffa80`039ca680 : nt!KiCommitThreadWait+0x1d2
fffff880`031b6240 fffff880`01474992 : 00000000`00000000 fffff880`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`031b62e0 fffff880`06c675cc : 00000000`00000000 fffff880`00000000 00000000`00000000 fffffa80`05f1a1a0 : ndis!NdisWaitEvent+0x32
fffff880`031b6320 00000000`00000000 : fffff880`00000000 00000000`00000000 fffffa80`05f1a1a0 fffff880`02f63180 : athrxusb+0x35cc


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_4_athrxusb_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_4_athrxusb_IMAGE_usbhub.sys

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\swaggatron\Windows_NT6_BSOD_jcgriff2\122911-35864-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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`02e5b000 PsLoadedModuleList = 0xfffff800`030a0670
Debug session time: Thu Dec 29 00:53:56.069 2011 (UTC - 7:00)
System Uptime: 0 days 5:58:22.755
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {80060d9397, 2, 0, fffff880072790e1}

Unable to load image \SystemRoot\system32\DRIVERS\athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+760e1 )

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: 00000080060d9397, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880072790e1, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
 00000080060d9397 

CURRENT_IRQL:  2

FAULTING_IP: 
athrxusb+760e1
fffff880`072790e1 8b402c          mov     eax,dword ptr [rax+2Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffb540 -- (.trap 0xfffff88002ffb540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000080060d936b rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa8006073030 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880072790e1 rsp=fffff88002ffb6d0 rbp=0000000000000000
 r8=fffffa8006065238  r9=0000000000000000 r10=fffffffffffe5ff2
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
athrxusb+0x760e1:
fffff880`072790e1 8b402c          mov     eax,dword ptr [rax+2Ch] ds:00000080`060d9397=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed71e9 to fffff80002ed7c40

STACK_TEXT:  
fffff880`02ffb3f8 fffff800`02ed71e9 : 00000000`0000000a 00000080`060d9397 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffb400 fffff800`02ed5e60 : fffffa80`00000000 fffffa80`0465bc20 fffffa80`0465bc20 fffffa80`05f1a8a0 : nt!KiBugCheckDispatch+0x69
fffff880`02ffb540 fffff880`072790e1 : fffff880`01483110 fffffa80`03e59c40 00000000`00000282 fffff880`072146b0 : nt!KiPageFault+0x260
fffff880`02ffb6d0 fffff880`01483110 : fffffa80`03e59c40 00000000`00000282 fffff880`072146b0 00000000`00000000 : athrxusb+0x760e1
fffff880`02ffb6d8 fffffa80`03e59c40 : 00000000`00000282 fffff880`072146b0 00000000`00000000 fffffa80`03e59c40 : ndis!WPP_GLOBAL_Control
fffff880`02ffb6e0 00000000`00000282 : fffff880`072146b0 00000000`00000000 fffffa80`03e59c40 00000000`00000000 : 0xfffffa80`03e59c40
fffff880`02ffb6e8 fffff880`072146b0 : 00000000`00000000 fffffa80`03e59c40 00000000`00000000 fffff880`0723fca1 : 0x282
fffff880`02ffb6f0 00000000`00000000 : fffffa80`03e59c40 00000000`00000000 fffff880`0723fca1 00000001`06735810 : athrxusb+0x116b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrxusb+760e1
fffff880`072790e1 8b402c          mov     eax,dword ptr [rax+2Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrxusb+760e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrxusb

IMAGE_NAME:  athrxusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  488f1151

FAILURE_BUCKET_ID:  X64_0xD1_athrxusb+760e1

BUCKET_ID:  X64_0xD1_athrxusb+760e1

Followup: MachineOwner
---------


[/list]

Code:

athrxusb	fffff880`07203000	fffff880`07310000	Tue Jul 29 06:47:13 2008 (488f1151)	00107e18	None	athrxusb.sys

You need to update the above driver as it is causing most/all of your issues. Atheros is the hardest to find updates for, so I will need information about it. Do the following:

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Expand Network Adapters
6. Tell me what is listed, especially the full name of anything with Atheros in it.

swaggatron · Dec 29, 2011

-Belkin Wireless G USB Network Adapter
-Realtek PCIe GBE Family Controller

Sorry for being clueless, but what's Atheros?

writhziden · Dec 29, 2011

swaggatron said:
-Belkin Wireless G USB Network Adapter
-Realtek PCIe GBE Family Controller

Sorry for being clueless, but what's Atheros?

It appears to be a wireless USB device. Do you not have such a device plugged into your commputer? Edit: I wonder if the Belkin piggybacks with the Atheros driver... That's kinda odd unless Belkin has a parnership with Atheros that I did not know about. Do me a favor:

1. Right click the Belkin USB device in device manager and click Properties.
2. Click the Details tab
3. Click the down arrow and find and click Service.

What does it say in the box below?

writhziden · Dec 29, 2011

Belkin for information on obtaining the proper driver.

swaggatron · Dec 29, 2011

It says athrusb.
Surely it can't be the USB causing all these problems? $: I've had bluescreens even on occasions when it's unplugged. & I don't have an Ethernet cable so this is pretty much the only way I connect to the internet.

writhziden · Dec 29, 2011

swaggatron said:
It says athrusb.
Surely it can't be the USB causing all these problems? $: I've had bluescreens even on occasions when it's unplugged. & I don't have an Ethernet cable so this is pretty much the only way I connect to the internet.

The USB isn't the issue, per say. The problem is that the driver is dated before Windows 7 was released, so it was never tested on Windows 7. You need a new driver for it.

writhziden · Dec 29, 2011

Did you try the above link to find your drivers?

I fixed the link so it points to the right place for getting Windows 7 drivers. The old link pointed to XP/Vista drivers, which are basically the drivers you already have.

swaggatron · Dec 29, 2011

I do have this driver, it's the one I downloaded when I started using the device. The driver that came with the cd didn't work.

writhziden · Dec 30, 2011

You should look into replacing the wireless usb device with one that is more current. Your device is pre-Windows 7 and will continue to cause conflicts with your system. Once you have bought your device, I suggest not opening it or using it until you proceed with the following steps with your old device still plugged in:

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Expand Network Adapters
6. Right click Belkin Wireless G USB Network Adapter
7. Click Uninstall (After clicking, do not hit ok in the dialog box that pops up yet)
8. Tick the box to delete the driver software for the device
9. Click OK
10. Shut down and turn off your computer (do not restart if asked to; you want to shut down instead)
11. Open up your new device
12. Read the directions given by the new device's manufacturer for installing the device
13. Follow the directions and get your new device up and running

The above steps should provide more stability with your system. If you continue to have blue screen crashes, let us know, and we can proceed with further troubleshooting options.

The above will remove all remnants of your old device from the system to prevent them from causing conflicts in the future. A device driver can sometimes still cause issues with a system even if the device is not active, especially USB devices.

writhziden · Jan 19, 2012

Did you replace your wireless device? How is your system's stability?

recurring BSOD at random, various error codes?

swaggatron

New member

My Computer

writhziden

Closed by request.

My Computer

swaggatron

New member

My Computer

writhziden

Closed by request.

My Computer

swaggatron

New member

My Computer

writhziden

Closed by request.

My Computer

writhziden

Closed by request.

My Computer

swaggatron

New member

My Computer

writhziden

Closed by request.

My Computer

writhziden

Closed by request.

My Computer

swaggatron

New member

My Computer

writhziden

Closed by request.

My Computer

writhziden

Closed by request.

My Computer