bsod while watching videos online.

[themaster4561]

Hi i have windows 7 pro 64 bit. It doesnt happen everytime but sometimes when i watch videos online the computer will bsod and restart. I have an intel motherboard with core 2 quad and 4 gb of corsair ddr3. My video card is nvidia geforce 9400 gt. I have bought new memory and put a new cpu fan because it was overheating. I have also replaced the hard drive and it still bsod. I have another computer with a similar build which works perfectly fine. I have swtiched out the video cards from my other computer to this computer and it still bsod. I am thinking the motherboard could be defective or possibly the processor maybe damaged from overheating from the previous fan?idk I am hoping there is a software conflict that is causing this that is why i attatched the dump files. Can somebody please help me with this problem?

 

[Jonathan_King]

It looks as if your Linksys Wireless Adapter is causing the problems. I suggest updating the driver for it, or uninstall it and install a fresh copy.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_041810-20124-01.zip\041810-20124-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Sun Apr 18 21:25:58.762 2010 (GMT-4)
System Uptime: 0 days 0:10:00.276
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\WUSB54Gv4x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys
Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf )

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

0: 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: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c578 -- (.exr 0xfffff80000b9c578)
ExceptionAddress: fffff880047397cf (WUSB54Gv4x64+0x000000000002d7cf)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c620 -- (.trap 0xfffff80000b9c620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=38660f0066e02c1b rbx=0000000000000000 rcx=fffffa8006e0bff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880047397cf rsp=fffff80000b9c7b0 rbp=0000000000000000
 r8=fffffa8006103e00  r9=0000000000000000 r10=fffffa80051f3b50
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
WUSB54Gv4x64+0x2d7cf:
fffff880`047397cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acd32e to fffff80002ad55d0

STACK_TEXT:  
fffff800`00b9b668 fffff800`02acd32e : fffffa80`06d15d60 00000000`00000000 fffff800`00b9bde0 fffff800`02b02524 : nt!KeBugCheck
fffff800`00b9b670 fffff800`02afb2ed : fffff800`02ce3b88 fffff800`02c1ca40 fffff800`02a65000 fffff800`00b9c578 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b6a0 fffff800`02b02950 : fffff800`02c24b24 fffff800`00b9b718 fffff800`00b9c578 fffff800`02a65000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b6d0 fffff800`02b0f8df : fffff800`00b9c578 fffff800`00b9bde0 fffff800`00000000 fffffa80`051f3b50 : nt!RtlDispatchException+0x410
fffff800`00b9bdb0 fffff800`02ad4c42 : fffff800`00b9c578 fffffa80`06e6cc40 fffff800`00b9c620 fffffa80`06e2c620 : nt!KiDispatchException+0x16f
fffff800`00b9c440 fffff800`02ad354a : fffffa80`00000000 00000000`00000001 fffffa80`07016010 fffff880`047a7808 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c620 fffff880`047397cf : fffffa80`06e0c000 fffff800`00b9c860 fffffa80`051f3b50 fffffa80`06e6cc40 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c7b0 fffffa80`06e0c000 : fffff800`00b9c860 fffffa80`051f3b50 fffffa80`06e6cc40 fffffa80`06e0c000 : WUSB54Gv4x64+0x2d7cf
fffff800`00b9c7b8 fffff800`00b9c860 : fffffa80`051f3b50 fffffa80`06e6cc40 fffffa80`06e0c000 fffffa80`06e68980 : 0xfffffa80`06e0c000
fffff800`00b9c7c0 fffffa80`051f3b50 : fffffa80`06e6cc40 fffffa80`06e0c000 fffffa80`06e68980 00000000`00000001 : 0xfffff800`00b9c860
fffff800`00b9c7c8 fffffa80`06e6cc40 : fffffa80`06e0c000 fffffa80`06e68980 00000000`00000001 38660f00`66e02c1b : 0xfffffa80`051f3b50
fffff800`00b9c7d0 fffffa80`06e0c000 : fffffa80`06e68980 00000000`00000001 38660f00`66e02c1b fffffa80`051f3b50 : 0xfffffa80`06e6cc40
fffff800`00b9c7d8 fffffa80`06e68980 : 00000000`00000001 38660f00`66e02c1b fffffa80`051f3b50 fffff880`04739a1a : 0xfffffa80`06e0c000
fffff800`00b9c7e0 00000000`00000001 : 38660f00`66e02c1b fffffa80`051f3b50 fffff880`04739a1a fffffa80`06df8000 : 0xfffffa80`06e68980
fffff800`00b9c7e8 38660f00`66e02c1b : fffffa80`051f3b50 fffff880`04739a1a fffffa80`06df8000 fffffa80`06e84a60 : 0x1
fffff800`00b9c7f0 fffffa80`051f3b50 : fffff880`04739a1a fffffa80`06df8000 fffffa80`06e84a60 00000000`00000000 : 0x38660f00`66e02c1b
fffff800`00b9c7f8 fffff880`04739a1a : fffffa80`06df8000 fffffa80`06e84a60 00000000`00000000 fffffa80`00000000 : 0xfffffa80`051f3b50
fffff800`00b9c800 fffffa80`06df8000 : fffffa80`06e84a60 00000000`00000000 fffffa80`00000000 fffffa80`051f3b50 : WUSB54Gv4x64+0x2da1a
fffff800`00b9c808 fffffa80`06e84a60 : 00000000`00000000 fffffa80`00000000 fffffa80`051f3b50 fffff880`0473996a : 0xfffffa80`06df8000
fffff800`00b9c810 00000000`00000000 : fffffa80`00000000 fffffa80`051f3b50 fffff880`0473996a fffffa80`06df8000 : 0xfffffa80`06e84a60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUSB54Gv4x64+2d7cf
fffff880`047397cf ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  WUSB54Gv4x64+2d7cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WUSB54Gv4x64

IMAGE_NAME:  WUSB54Gv4x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45923fcb

FAILURE_BUCKET_ID:  X64_0x1E_WUSB54Gv4x64+2d7cf

BUCKET_ID:  X64_0x1E_WUSB54Gv4x64+2d7cf

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

 

[themaster4561]

I will go ahead and do that, but is that what all the dump files are saying?

 

[Jonathan_King]

Yep, that's what they all say.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_041810-24507-01.zip\041810-24507-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a5b000 PsLoadedModuleList = 0xfffff800`02c98e50
Debug session time: Sun Apr 18 21:15:06.269 2010 (GMT-4)
System Uptime: 0 days 0:02:19.157
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\WUSB54Gv4x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys
Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf )

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: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffb578 -- (.exr 0xfffff88002ffb578)
ExceptionAddress: fffff880047397cf (WUSB54Gv4x64+0x000000000002d7cf)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffb620 -- (.trap 0xfffff88002ffb620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=38660f00ea902c1b rbx=0000000000000000 rcx=fffffa8006f36ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880047397cf rsp=fffff88002ffb7b0 rbp=0000000000000000
 r8=fffffa800717ce00  r9=0000000000000000 r10=fffffa8006f19a70
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
WUSB54Gv4x64+0x2d7cf:
fffff880`047397cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac332e to fffff80002acb5d0

STACK_TEXT:  
fffff880`02ffa668 fffff800`02ac332e : fffff880`02ffa6f0 fffff880`0477900f fffff880`02ffade0 fffff800`02af8524 : nt!KeBugCheck
fffff880`02ffa670 fffff800`02af12ed : fffff800`02cd9b88 fffff800`02c12a40 fffff800`02a5b000 fffff880`02ffb578 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa6a0 fffff800`02af8950 : fffff800`02c1ab24 fffff880`02ffa718 fffff880`02ffb578 fffff800`02a5b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa6d0 fffff800`02b058df : fffff880`02ffb578 fffff880`02ffade0 fffff880`00000000 fffffa80`06f19a70 : nt!RtlDispatchException+0x410
fffff880`02ffadb0 fffff800`02acac42 : fffff880`02ffb578 fffffa80`06f6dbd0 fffff880`02ffb620 fffffa80`06d8a370 : nt!KiDispatchException+0x16f
fffff880`02ffb440 fffff800`02ac954a : fffffa80`00000000 00000000`00000001 fffffa80`070cd010 fffff880`0477c808 : nt!KiExceptionDispatch+0xc2
fffff880`02ffb620 fffff880`047397cf : fffffa80`06f37000 fffff880`02ffb860 fffffa80`06f19a70 fffffa80`06f6dbd0 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffb7b0 fffffa80`06f37000 : fffff880`02ffb860 fffffa80`06f19a70 fffffa80`06f6dbd0 fffffa80`06f37000 : WUSB54Gv4x64+0x2d7cf
fffff880`02ffb7b8 fffff880`02ffb860 : fffffa80`06f19a70 fffffa80`06f6dbd0 fffffa80`06f37000 fffffa80`06f8ab90 : 0xfffffa80`06f37000
fffff880`02ffb7c0 fffffa80`06f19a70 : fffffa80`06f6dbd0 fffffa80`06f37000 fffffa80`06f8ab90 00000000`07b3e001 : 0xfffff880`02ffb860
fffff880`02ffb7c8 fffffa80`06f6dbd0 : fffffa80`06f37000 fffffa80`06f8ab90 00000000`07b3e001 38660f00`ea902c1b : 0xfffffa80`06f19a70
fffff880`02ffb7d0 fffffa80`06f37000 : fffffa80`06f8ab90 00000000`07b3e001 38660f00`ea902c1b fffffa80`06f19a70 : 0xfffffa80`06f6dbd0
fffff880`02ffb7d8 fffffa80`06f8ab90 : 00000000`07b3e001 38660f00`ea902c1b fffffa80`06f19a70 fffff880`04739a1a : 0xfffffa80`06f37000
fffff880`02ffb7e0 00000000`07b3e001 : 38660f00`ea902c1b fffffa80`06f19a70 fffff880`04739a1a fffffa80`06f23000 : 0xfffffa80`06f8ab90
fffff880`02ffb7e8 38660f00`ea902c1b : fffffa80`06f19a70 fffff880`04739a1a fffffa80`06f23000 fffffa80`06f8be70 : 0x7b3e001
fffff880`02ffb7f0 fffffa80`06f19a70 : fffff880`04739a1a fffffa80`06f23000 fffffa80`06f8be70 00000000`00000000 : 0x38660f00`ea902c1b
fffff880`02ffb7f8 fffff880`04739a1a : fffffa80`06f23000 fffffa80`06f8be70 00000000`00000000 fffffa80`06a8a7a8 : 0xfffffa80`06f19a70
fffff880`02ffb800 fffffa80`06f23000 : fffffa80`06f8be70 00000000`00000000 fffffa80`06a8a7a8 fffffa80`06f19a70 : WUSB54Gv4x64+0x2da1a
fffff880`02ffb808 fffffa80`06f8be70 : 00000000`00000000 fffffa80`06a8a7a8 fffffa80`06f19a70 fffff880`0473996a : 0xfffffa80`06f23000
fffff880`02ffb810 00000000`00000000 : fffffa80`06a8a7a8 fffffa80`06f19a70 fffff880`0473996a fffffa80`06f23000 : 0xfffffa80`06f8be70


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUSB54Gv4x64+2d7cf
fffff880`047397cf ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  WUSB54Gv4x64+2d7cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WUSB54Gv4x64

IMAGE_NAME:  WUSB54Gv4x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45923fcb

FAILURE_BUCKET_ID:  X64_0x1E_WUSB54Gv4x64+2d7cf

BUCKET_ID:  X64_0x1E_WUSB54Gv4x64+2d7cf

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp2_041710-27362-01.zip\041710-27362-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Sat Apr 17 15:24:52.979 2010 (GMT-4)
System Uptime: 2 days 9:07:28.867
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\WUSB54Gv4x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys
Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf )

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

2: 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: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f927e8 -- (.exr 0xfffff88002f927e8)
ExceptionAddress: fffff88001f467cf (WUSB54Gv4x64+0x000000000002d7cf)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f92890 -- (.trap 0xfffff88002f92890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=31b2240025c0c6f7 rbx=0000000000000000 rcx=fffffa8006d29ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001f467cf rsp=fffff88002f92a20 rbp=0000000000000000
 r8=fffffa8007370e00  r9=0000000000000000 r10=fffffa8006ca3420
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`01f467cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7f32e to fffff80002a875d0

STACK_TEXT:  
fffff880`02f918d8 fffff800`02a7f32e : fffff880`02f91960 fffff880`01e0600f fffff880`02f92050 fffff800`02ab4524 : nt!KeBugCheck
fffff880`02f918e0 fffff800`02aad2ed : fffff800`02c95b88 fffff800`02bcea40 fffff800`02a17000 fffff880`02f927e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f91910 fffff800`02ab4950 : fffff800`02bd6a50 fffff880`02f91988 fffff880`02f927e8 fffff800`02a17000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f91940 fffff800`02ac18df : fffff880`02f927e8 fffff880`02f92050 fffff880`00000000 fffffa80`06ca3420 : nt!RtlDispatchException+0x410
fffff880`02f92020 fffff800`02a86c42 : fffff880`02f927e8 fffffa80`06d33e70 fffff880`02f92890 fffffa80`06cb2020 : nt!KiDispatchException+0x16f
fffff880`02f926b0 fffff800`02a8554a : fffffa80`00000000 00000000`00000001 fffffa80`0653b010 fffff880`01e09808 : nt!KiExceptionDispatch+0xc2
fffff880`02f92890 fffff880`01f467cf : fffffa80`06d2a000 fffff880`02f92ad0 fffffa80`06ca3420 fffffa80`06d33e70 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f92a20 fffffa80`06d2a000 : fffff880`02f92ad0 fffffa80`06ca3420 fffffa80`06d33e70 fffffa80`06d2a000 : WUSB54Gv4x64+0x2d7cf
fffff880`02f92a28 fffff880`02f92ad0 : fffffa80`06ca3420 fffffa80`06d33e70 fffffa80`06d2a000 fffffa80`06c7fc10 : 0xfffffa80`06d2a000
fffff880`02f92a30 fffffa80`06ca3420 : fffffa80`06d33e70 fffffa80`06d2a000 fffffa80`06c7fc10 00000000`06711001 : 0xfffff880`02f92ad0
fffff880`02f92a38 fffffa80`06d33e70 : fffffa80`06d2a000 fffffa80`06c7fc10 00000000`06711001 31b22400`25c0c6f7 : 0xfffffa80`06ca3420
fffff880`02f92a40 fffffa80`06d2a000 : fffffa80`06c7fc10 00000000`06711001 31b22400`25c0c6f7 fffffa80`06ca3420 : 0xfffffa80`06d33e70
fffff880`02f92a48 fffffa80`06c7fc10 : 00000000`06711001 31b22400`25c0c6f7 fffffa80`06ca3420 fffff880`01f46a1a : 0xfffffa80`06d2a000
fffff880`02f92a50 00000000`06711001 : 31b22400`25c0c6f7 fffffa80`06ca3420 fffff880`01f46a1a fffffa80`06d16000 : 0xfffffa80`06c7fc10
fffff880`02f92a58 31b22400`25c0c6f7 : fffffa80`06ca3420 fffff880`01f46a1a fffffa80`06d16000 fffffa80`06d31da0 : 0x6711001
fffff880`02f92a60 fffffa80`06ca3420 : fffff880`01f46a1a fffffa80`06d16000 fffffa80`06d31da0 fffffa80`06711001 : 0x31b22400`25c0c6f7
fffff880`02f92a68 fffff880`01f46a1a : fffffa80`06d16000 fffffa80`06d31da0 fffffa80`06711001 00000000`00000000 : 0xfffffa80`06ca3420
fffff880`02f92a70 fffffa80`06d16000 : fffffa80`06d31da0 fffffa80`06711001 00000000`00000000 fffffa80`06ca3420 : WUSB54Gv4x64+0x2da1a
fffff880`02f92a78 fffffa80`06d31da0 : fffffa80`06711001 00000000`00000000 fffffa80`06ca3420 fffff880`01f4696a : 0xfffffa80`06d16000
fffff880`02f92a80 fffffa80`06711001 : 00000000`00000000 fffffa80`06ca3420 fffff880`01f4696a fffffa80`06d16000 : 0xfffffa80`06d31da0
fffff880`02f92a88 00000000`00000000 : fffffa80`06ca3420 fffff880`01f4696a fffffa80`06d16000 fffffa80`060c9510 : 0xfffffa80`06711001


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUSB54Gv4x64+2d7cf
fffff880`01f467cf ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  WUSB54Gv4x64+2d7cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WUSB54Gv4x64

IMAGE_NAME:  WUSB54Gv4x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45923fcb

FAILURE_BUCKET_ID:  X64_0x1E_WUSB54Gv4x64+2d7cf

BUCKET_ID:  X64_0x1E_WUSB54Gv4x64+2d7cf

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

 

[themaster4561]

Yup i believe that was it, i tested the wireless adapter on my other computer and it bsod. Thank you for your help, very much appreciated!Also, Do you have any suggestions on wireless adapter or drivers that are 64 bit compatible that will work with windows 7. I just did some research on mine and it appears alot of people have experienced bsod with their 64 bit windows with this particular driver WUSB54Gv4x64.sys ?

 

[Jonathan_King]

Well to be honest, for just about every driver, there is someone out there who has had BSODs because of it.

What is the model of your wireless adapter? Try searching on the manufacturer's site for drivers.