Windows 7 Crashes only when playing ARMA2?

[Nickvio0294]

there that should work also new things ive tried.
Ran Driver Verifier it seems all is well as i received no BSODs on that.
I ran chkdsk and got no errors
I ran memtest and got 0 errors after 5 passes
I've also downloaded the latest drivers for my nvidia nforce 750 SLI chipset.

 

[Capt.Jack Sparrow]

there that should work also new things ive tried.
Ran Driver Verifier it seems all is well as i received no BSODs on that.
I ran chkdsk and got no errors
I ran memtest and got 0 errors after 5 passes
I've also downloaded the latest drivers for my nvidia nforce 750 SLI chipset.

Hello !!

I seems to like its an issue with WUSB54Gv4x64.sys. That would be your Linksys USB Wireless -G Adapter. I would recommend to disconnect the device and remove all the drivers related to it and let it run for few hours then see whether it working good.

Uninstall AVG completetly also use the Removal Tool and clean it up AVG Antivirus and Security Software - Tools download and make sure you clean all the traces of it. You could Download Microsoft Security Essentials and install it.

But how long did you ran the Driver Verifer ?? I would recommend to run it upto atleast 36 hours. If the Driver Verifier didn't pick up any drivers then it's some hardware that has caused the problem which would be little bit hard to troubleshoot.

*******************************************************************************
*                                                                             *
*                        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: 
+6882952f0150d8d8
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  arma2.exe

CURRENT_IRQL:  2

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

TRAP_FRAME:  fffff800040a6890 -- (.trap 0xfffff800040a6890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=e7b50f00dcb0598e rbx=0000000000000000 rcx=fffffa8005fc1ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b747cf rsp=fffff800040a6a20 rbp=0000000000000000
 r8=fffffa80068b0600  r9=0000000000000000 r10=fffffa8005f3c140
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`04b747cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002abb32e to fffff80002ac35d0

STACK_TEXT:  
fffff800`040a58d8 fffff800`02abb32e : fffffa80`064d5490 fffff880`04370860 fffff800`040a6050 fffff800`02af0524 : nt!KeBugCheck
fffff800`040a58e0 fffff800`02ae92ed : fffff800`02cd1b88 fffff800`02c0aa40 fffff800`02a53000 fffff800`040a67e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`040a5910 fffff800`02af0950 : fffff800`02c12a50 fffff800`040a5988 fffff800`040a67e8 fffff800`02a53000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`040a5940 fffff800`02afd8df : fffff800`040a67e8 fffff800`040a6050 fffff800`00000000 fffffa80`05f3c140 : nt!RtlDispatchException+0x410
fffff800`040a6020 fffff800`02ac2c42 : fffff800`040a67e8 fffffa80`060473a0 fffff800`040a6890 fffffa80`05f68900 : nt!KiDispatchException+0x16f
fffff800`040a66b0 fffff800`02ac154a : fffffa80`00000000 00000000`00000001 fffffa80`063ed010 fffff880`04370808 : nt!KiExceptionDispatch+0xc2
fffff800`040a6890 fffff880`04b747cf : fffffa80`05fc2000 fffff800`040a6ad0 fffffa80`05f3c140 fffffa80`060473a0 : nt!KiGeneralProtectionFault+0x10a
fffff800`040a6a20 fffffa80`05fc2000 : fffff800`040a6ad0 fffffa80`05f3c140 fffffa80`060473a0 fffffa80`05fc2000 : WUSB54Gv4x64+0x2d7cf
fffff800`040a6a28 fffff800`040a6ad0 : fffffa80`05f3c140 fffffa80`060473a0 fffffa80`05fc2000 fffffa80`060421e0 : 0xfffffa80`05fc2000
fffff800`040a6a30 fffffa80`05f3c140 : fffffa80`060473a0 fffffa80`05fc2000 fffffa80`060421e0 00000000`00000001 : 0xfffff800`040a6ad0
fffff800`040a6a38 fffffa80`060473a0 : fffffa80`05fc2000 fffffa80`060421e0 00000000`00000001 e7b50f00`dcb0598e : 0xfffffa80`05f3c140
fffff800`040a6a40 fffffa80`05fc2000 : fffffa80`060421e0 00000000`00000001 e7b50f00`dcb0598e fffffa80`05f3c140 : 0xfffffa80`060473a0
fffff800`040a6a48 fffffa80`060421e0 : 00000000`00000001 e7b50f00`dcb0598e fffffa80`05f3c140 fffff880`04b74a1a : 0xfffffa80`05fc2000
fffff800`040a6a50 00000000`00000001 : e7b50f00`dcb0598e fffffa80`05f3c140 fffff880`04b74a1a fffffa80`05fae000 : 0xfffffa80`060421e0
fffff800`040a6a58 e7b50f00`dcb0598e : fffffa80`05f3c140 fffff880`04b74a1a fffffa80`05fae000 fffffa80`06046e70 : 0x1
fffff800`040a6a60 fffffa80`05f3c140 : fffff880`04b74a1a fffffa80`05fae000 fffffa80`06046e70 fffffa80`04991201 : 0xe7b50f00`dcb0598e
fffff800`040a6a68 fffff880`04b74a1a : fffffa80`05fae000 fffffa80`06046e70 fffffa80`04991201 00000000`00000002 : 0xfffffa80`05f3c140
fffff800`040a6a70 fffffa80`05fae000 : fffffa80`06046e70 fffffa80`04991201 00000000`00000002 fffffa80`05f3c140 : WUSB54Gv4x64+0x2da1a
fffff800`040a6a78 fffffa80`06046e70 : fffffa80`04991201 00000000`00000002 fffffa80`05f3c140 fffff880`04b7496a : 0xfffffa80`05fae000
fffff800`040a6a80 fffffa80`04991201 : 00000000`00000002 fffffa80`05f3c140 fffff880`04b7496a fffffa80`05fae000 : 0xfffffa80`06046e70
fffff800`040a6a88 00000000`00000002 : fffffa80`05f3c140 fffff880`04b7496a fffffa80`05fae000 fffffa80`06047fa0 : 0xfffffa80`04991201
fffff800`040a6a90 fffffa80`05f3c140 : fffff880`04b7496a fffffa80`05fae000 fffffa80`06047fa0 00000000`00000000 : 0x2
fffff800`040a6a98 fffff880`04b7496a : fffffa80`05fae000 fffffa80`06047fa0 00000000`00000000 00000000`00000004 : 0xfffffa80`05f3c140
fffff800`040a6aa0 fffffa80`05fae000 : fffffa80`06047fa0 00000000`00000000 00000000`00000004 fffffa80`068b0680 : WUSB54Gv4x64+0x2d96a
fffff800`040a6aa8 fffffa80`06047fa0 : 00000000`00000000 00000000`00000004 fffffa80`068b0680 fffffa80`06047fa0 : 0xfffffa80`05fae000
fffff800`040a6ab0 00000000`00000000 : 00000000`00000004 fffffa80`068b0680 fffffa80`06047fa0 00000000`00000018 : 0xfffffa80`06047fa0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUSB54Gv4x64+2d7cf
fffff880`04b747cf ??              ???

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
---------

0: kd> .exr 0xfffff800040a67e8
ExceptionAddress: fffff88004b747cf (WUSB54Gv4x64+0x000000000002d7cf)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
0: kd> .trap 0xfffff800040a6890
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=e7b50f00dcb0598e rbx=0000000000000000 rcx=fffffa8005fc1ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b747cf rsp=fffff800040a6a20 rbp=0000000000000000
 r8=fffffa80068b0600  r9=0000000000000000 r10=fffffa8005f3c140
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`04b747cf ??              ???

Hope this helps,
Captain

 

[Nickvio0294]

there that should work also new things ive tried.
Ran Driver Verifier it seems all is well as i received no BSODs on that.
I ran chkdsk and got no errors
I ran memtest and got 0 errors after 5 passes
I've also downloaded the latest drivers for my nvidia nforce 750 SLI chipset.

Hello !!

I seems to like its an issue with WUSB54Gv4x64.sys. That would be your Linksys USB Wireless -G Adapter. I would recommend to disconnect the device and remove all the drivers related to it and let it run for few hours then see whether it working good.

Uninstall AVG completetly also use the Removal Tool and clean it up AVG Antivirus and Security Software - Tools download and make sure you clean all the traces of it. You could Download Microsoft Security Essentials and install it.

But how long did you ran the Driver Verifer ?? I would recommend to run it upto atleast 36 hours. If the Driver Verifier didn't pick up any drivers then it's some hardware that has caused the problem which would be little bit hard to troubleshoot.

*******************************************************************************
*                                                                             *
*                        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: 
+6882952f0150d8d8
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  arma2.exe

CURRENT_IRQL:  2

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

TRAP_FRAME:  fffff800040a6890 -- (.trap 0xfffff800040a6890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=e7b50f00dcb0598e rbx=0000000000000000 rcx=fffffa8005fc1ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b747cf rsp=fffff800040a6a20 rbp=0000000000000000
 r8=fffffa80068b0600  r9=0000000000000000 r10=fffffa8005f3c140
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`04b747cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002abb32e to fffff80002ac35d0

STACK_TEXT:  
fffff800`040a58d8 fffff800`02abb32e : fffffa80`064d5490 fffff880`04370860 fffff800`040a6050 fffff800`02af0524 : nt!KeBugCheck
fffff800`040a58e0 fffff800`02ae92ed : fffff800`02cd1b88 fffff800`02c0aa40 fffff800`02a53000 fffff800`040a67e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`040a5910 fffff800`02af0950 : fffff800`02c12a50 fffff800`040a5988 fffff800`040a67e8 fffff800`02a53000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`040a5940 fffff800`02afd8df : fffff800`040a67e8 fffff800`040a6050 fffff800`00000000 fffffa80`05f3c140 : nt!RtlDispatchException+0x410
fffff800`040a6020 fffff800`02ac2c42 : fffff800`040a67e8 fffffa80`060473a0 fffff800`040a6890 fffffa80`05f68900 : nt!KiDispatchException+0x16f
fffff800`040a66b0 fffff800`02ac154a : fffffa80`00000000 00000000`00000001 fffffa80`063ed010 fffff880`04370808 : nt!KiExceptionDispatch+0xc2
fffff800`040a6890 fffff880`04b747cf : fffffa80`05fc2000 fffff800`040a6ad0 fffffa80`05f3c140 fffffa80`060473a0 : nt!KiGeneralProtectionFault+0x10a
fffff800`040a6a20 fffffa80`05fc2000 : fffff800`040a6ad0 fffffa80`05f3c140 fffffa80`060473a0 fffffa80`05fc2000 : WUSB54Gv4x64+0x2d7cf
fffff800`040a6a28 fffff800`040a6ad0 : fffffa80`05f3c140 fffffa80`060473a0 fffffa80`05fc2000 fffffa80`060421e0 : 0xfffffa80`05fc2000
fffff800`040a6a30 fffffa80`05f3c140 : fffffa80`060473a0 fffffa80`05fc2000 fffffa80`060421e0 00000000`00000001 : 0xfffff800`040a6ad0
fffff800`040a6a38 fffffa80`060473a0 : fffffa80`05fc2000 fffffa80`060421e0 00000000`00000001 e7b50f00`dcb0598e : 0xfffffa80`05f3c140
fffff800`040a6a40 fffffa80`05fc2000 : fffffa80`060421e0 00000000`00000001 e7b50f00`dcb0598e fffffa80`05f3c140 : 0xfffffa80`060473a0
fffff800`040a6a48 fffffa80`060421e0 : 00000000`00000001 e7b50f00`dcb0598e fffffa80`05f3c140 fffff880`04b74a1a : 0xfffffa80`05fc2000
fffff800`040a6a50 00000000`00000001 : e7b50f00`dcb0598e fffffa80`05f3c140 fffff880`04b74a1a fffffa80`05fae000 : 0xfffffa80`060421e0
fffff800`040a6a58 e7b50f00`dcb0598e : fffffa80`05f3c140 fffff880`04b74a1a fffffa80`05fae000 fffffa80`06046e70 : 0x1
fffff800`040a6a60 fffffa80`05f3c140 : fffff880`04b74a1a fffffa80`05fae000 fffffa80`06046e70 fffffa80`04991201 : 0xe7b50f00`dcb0598e
fffff800`040a6a68 fffff880`04b74a1a : fffffa80`05fae000 fffffa80`06046e70 fffffa80`04991201 00000000`00000002 : 0xfffffa80`05f3c140
fffff800`040a6a70 fffffa80`05fae000 : fffffa80`06046e70 fffffa80`04991201 00000000`00000002 fffffa80`05f3c140 : WUSB54Gv4x64+0x2da1a
fffff800`040a6a78 fffffa80`06046e70 : fffffa80`04991201 00000000`00000002 fffffa80`05f3c140 fffff880`04b7496a : 0xfffffa80`05fae000
fffff800`040a6a80 fffffa80`04991201 : 00000000`00000002 fffffa80`05f3c140 fffff880`04b7496a fffffa80`05fae000 : 0xfffffa80`06046e70
fffff800`040a6a88 00000000`00000002 : fffffa80`05f3c140 fffff880`04b7496a fffffa80`05fae000 fffffa80`06047fa0 : 0xfffffa80`04991201
fffff800`040a6a90 fffffa80`05f3c140 : fffff880`04b7496a fffffa80`05fae000 fffffa80`06047fa0 00000000`00000000 : 0x2
fffff800`040a6a98 fffff880`04b7496a : fffffa80`05fae000 fffffa80`06047fa0 00000000`00000000 00000000`00000004 : 0xfffffa80`05f3c140
fffff800`040a6aa0 fffffa80`05fae000 : fffffa80`06047fa0 00000000`00000000 00000000`00000004 fffffa80`068b0680 : WUSB54Gv4x64+0x2d96a
fffff800`040a6aa8 fffffa80`06047fa0 : 00000000`00000000 00000000`00000004 fffffa80`068b0680 fffffa80`06047fa0 : 0xfffffa80`05fae000
fffff800`040a6ab0 00000000`00000000 : 00000000`00000004 fffffa80`068b0680 fffffa80`06047fa0 00000000`00000018 : 0xfffffa80`06047fa0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUSB54Gv4x64+2d7cf
fffff880`04b747cf ??              ???

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
---------

0: kd> .exr 0xfffff800040a67e8
ExceptionAddress: fffff88004b747cf (WUSB54Gv4x64+0x000000000002d7cf)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
0: kd> .trap 0xfffff800040a6890
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=e7b50f00dcb0598e rbx=0000000000000000 rcx=fffffa8005fc1ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b747cf rsp=fffff800040a6a20 rbp=0000000000000000
 r8=fffffa80068b0600  r9=0000000000000000 r10=fffffa8005f3c140
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`04b747cf ??              ???

Hope this helps,
Captain

THANK YOU for the response! = ]
How can i go about removing all traces of the adapter? and how am i suppose to play anything such as my online internet games without it?
Also I am running driver verifier and have been for a while and i tried to play some battlefield bad company 2 i noticed this verifier is causing my cpu to be at 30% or greater most of the time and battlefield caused it to operate at 100% but anyways i alt tabbed out of battlefield only to find a windows message saying a nvidia display driver failed (it mentioned something about kernel mode and i believe it had a .sys at the end of the name) but it did say it successfully recovered even though my BF BC2 crashed which is normal as it does usually once a day not only for me but for my friend to. Driver verifier has been running for a few hours and ive been trying to go about my usual tasks but some of my games are really demanding also do you suggest that i force a BSOD with the verifier on to see if anything shows up?

 

[zigzag3143]

Um Guys,. the USB adapter is only responsible for one of the crashes. We need to start addressing the entiry of the crashes.

Ken

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


Loading Dump File [C:\Users\K\Desktop\New folder (3)\021010-31890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Wed Feb 10 13:46:26.441 2010 (GMT-4)
System Uptime: 0 days 1:54:08.566
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: 
+643c952f0316d8c0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  WinSAT.exe

CURRENT_IRQL:  2

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

TRAP_FRAME:  fffff80000ba2890 -- (.trap 0xfffff80000ba2890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=e7b50f0078a0598e rbx=0000000000000000 rcx=fffffa8005f35ff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b867cf rsp=fffff80000ba2a20 rbp=0000000000000000
 r8=fffffa8005ac7e00  r9=0000000000000000 r10=fffffa8005f00010
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`04b867cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acac2e to fffff80002ad2ed0

STACK_TEXT:  
fffff800`00ba18c8 fffff800`02acac2e : fffffa80`05ec61a0 00000000`00000000 fffff800`00ba2040 fffff800`02affe28 : nt!KeBugCheck
fffff800`00ba18d0 fffff800`02af8bed : fffff800`02cdfc24 fffff800`02c18a3c fffff800`02a61000 fffff800`00ba27e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1900 fffff800`02b00250 : fffff800`02c20a88 fffff800`00ba1978 fffff800`00ba27e8 fffff800`02a61000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1930 fffff800`02b0d1b5 : fffff800`00ba27e8 fffff800`00ba2040 fffff800`00000000 fffffa80`05f00010 : nt!RtlDispatchException+0x410
fffff800`00ba2010 fffff800`02ad2542 : fffff800`00ba27e8 fffffa80`05ffce70 fffff800`00ba2890 fffffa80`05f86240 : nt!KiDispatchException+0x135
fffff800`00ba26b0 fffff800`02ad0e4a : fffffa80`00000000 00000000`00000001 fffffa80`061fd010 fffff880`0435e808 : nt!KiExceptionDispatch+0xc2
fffff800`00ba2890 fffff880`04b867cf : fffffa80`05f36000 fffff800`00ba2ad0 fffffa80`05f00010 fffffa80`05ffce70 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2a20 fffffa80`05f36000 : fffff800`00ba2ad0 fffffa80`05f00010 fffffa80`05ffce70 fffffa80`05f36000 : WUSB54Gv4x64+0x2d7cf
fffff800`00ba2a28 fffff800`00ba2ad0 : fffffa80`05f00010 fffffa80`05ffce70 fffffa80`05f36000 fffffa80`05ff59a0 : 0xfffffa80`05f36000
fffff800`00ba2a30 fffffa80`05f00010 : fffffa80`05ffce70 fffffa80`05f36000 fffffa80`05ff59a0 00000000`009e7101 : 0xfffff800`00ba2ad0
fffff800`00ba2a38 fffffa80`05ffce70 : fffffa80`05f36000 fffffa80`05ff59a0 00000000`009e7101 e7b50f00`78a0598e : 0xfffffa80`05f00010
fffff800`00ba2a40 fffffa80`05f36000 : fffffa80`05ff59a0 00000000`009e7101 e7b50f00`78a0598e fffffa80`05f00010 : 0xfffffa80`05ffce70
fffff800`00ba2a48 fffffa80`05ff59a0 : 00000000`009e7101 e7b50f00`78a0598e fffffa80`05f00010 fffff880`04b86a1a : 0xfffffa80`05f36000
fffff800`00ba2a50 00000000`009e7101 : e7b50f00`78a0598e fffffa80`05f00010 fffff880`04b86a1a fffffa80`05f22000 : 0xfffffa80`05ff59a0
fffff800`00ba2a58 e7b50f00`78a0598e : fffffa80`05f00010 fffff880`04b86a1a fffffa80`05f22000 fffffa80`05ff6a60 : 0x9e7101
fffff800`00ba2a60 fffffa80`05f00010 : fffff880`04b86a1a fffffa80`05f22000 fffffa80`05ff6a60 00000000`00000000 : 0xe7b50f00`78a0598e
fffff800`00ba2a68 fffff880`04b86a1a : fffffa80`05f22000 fffffa80`05ff6a60 00000000`00000000 00000000`00000003 : 0xfffffa80`05f00010
fffff800`00ba2a70 fffffa80`05f22000 : fffffa80`05ff6a60 00000000`00000000 00000000`00000003 fffffa80`05f00010 : WUSB54Gv4x64+0x2da1a
fffff800`00ba2a78 fffffa80`05ff6a60 : 00000000`00000000 00000000`00000003 fffffa80`05f00010 fffff880`04b8696a : 0xfffffa80`05f22000
fffff800`00ba2a80 00000000`00000000 : 00000000`00000003 fffffa80`05f00010 fffff880`04b8696a fffffa80`05f22000 : 0xfffffa80`05ff6a60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUSB54Gv4x64+2d7cf
fffff880`04b867cf ??              ???

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
---------

 

[Nickvio0294]

Would this fix it possibly? http://support.microsoft.com/kb/977067

 

[Nickvio0294]

Driver verifier has been running for about 36 hours with no problems but the one i described above.
Would you like me to force a bsod so i can get a minidump for you to analyze?

 

[YakSipper]

Driver verifier has been running for about 36 hours with no problems but the one i described above.
Would you like me to force a bsod so i can get a minidump for you to analyze?

Sure. Give us a brand new dump file so it can be clear what issues remain.

 

[Nickvio0294]

Here you go.

 

[YakSipper]

Still the USB adapter driver causing bsod. WUSB54Gv4x64.sys

Try the Vista x64 driver from here instead, for the RT2500USB:

http://www.ralinktech.com/support.php

If normal installation fails, use the device manager to manually install it.

 

[Nickvio0294]

my wireless adapter is a linskys though will that driver even work? and alright if it is indeed the wireless adaptor then I guess im going to have to unplug it and clean out all traces of it which i could need some help doing by just finding where the files may be located.
if nothing seems to work do you think investing in a new USB wireless adapter might solve the issue?

 

[YakSipper]

Try the driver I pointed to first, then if still no good, visit Linksys for a driver.

Definitely a new adapter will fix it, but so will the right driver with your current one. I have reason to believe the one I pointed you to will be good for ya.

What specific model is it anyhow?

 

[Nickvio0294]

Try the driver I pointed to first, then if still no good, visit Linksys for a driver.

Definitely a new adapter will fix it, but so will the right driver with your current one. I have reason to believe the one I pointed you to will be good for ya.

What specific model is it anyhow?

coming straight off the box
Wireless-G USB Network Adapter
Model No: WUSB54G
Compatible with Wireless-B (802.11b)
Wireless-G (802.11g)

also can i just install the driver u want me to without uninstalling the current one i have?

 

[YakSipper]

also can i just install the driver u want me to without uninstalling the current one i have?

yes

 

[Nickvio0294]

also can i just install the driver u want me to without uninstalling the current one i have?

yes

i got an error
VIA 1394 OHCI compliant host controller failed the driver software was not successfully installed.

 

[YakSipper]

1394 is for firewire.

What you want to do is extract the driver I pointed you to after downloading. Then open the device manager. Right click on the adapter under the network section. Choose update driver software. Browse my computer. Let me pick. Have disk. Browse.

Then find the extracted .inf and double click on it. Hit ok. Hit next and let it install. Reboot.

 

[Nickvio0294]

the .inf? i downloaded an exe not an inf file.
so far i got everything i just cant find the file u want me to select.

 

[YakSipper]

Yeah, run the .exe and let it extract first. Then after extraction, use device manager to do what I described.

 

[Nickvio0294]

Yeah, run the .exe and let it extract first. Then after extraction, use device manager to do what I described.

okay and where is the .inf file im in program files and found ralink but i cant find a .inf file
A file path to the file and a filename would help me greatly.

 

[jcgriff2]

For info to all assisting in this thread -

Windows 7 BSODs only in ARMA2? - Tech Support Forum

jcgriff2

.

 

[Nickvio0294]

I fixed the problem it was indeed the drivers i downloaded the one yak said to and it worked thanks to all who helped me = ] i added rep as needed