BSOD after reformatting

Kaldin · 01 Aug 2010

I have a Dell studio XPS Windows 7 64-bit and I have somewhat recently gained a rather uncontrollable amount of viruses. I followed the manual to reformat the computer, yet the manual led me to an option that did not exist. In an alternative method, I reinstalled Windows 7.

Now the virus is gone, but a BSOD is there instead. I get the BSOD either when downloading, google searching, google image searching, or watching a youtube video. When it happens in those situations seems random yet its very common.

My BSOD is an automatic reboot and I'm sick of it. I've tried many things even including calling Dell and updating my drivers. No luck so far.

Can anyone help me in this? I would very greatly appreciate it :)

I am also having troubles sending the dmp. files. my computer wont let me send them individually because I need permission even though I am the admin, and when i try to compress the files i get an error saying "file not found or no read permission."

wow I'm a mess

any advice?

JMH · 01 Aug 2010

Kaldin said:

I have a Dell studio XPS Windows 7 64-bit and I have somewhat recently gained a rather uncontrollable amount of viruses. I followed the manual to reformat the computer, yet the manual led me to an option that did not exist. In an alternative method, I reinstalled Windows 7.

Now the virus is gone, but a BSOD is there instead. I get the BSOD either when downloading, google searching, google image searching, or watching a youtube video. When it happens in those situations seems random yet its very common.

My BSOD is an automatic reboot and I'm sick of it. I've tried many things even including calling Dell and updating my drivers. No luck so far.

Can anyone help me in this? I would very greatly appreciate it :)

I am also having troubles sending the dmp. files. my computer wont let me send them individually because I need permission even though I am the admin, and when i try to compress the files i get an error saying "file not found or no read permission."

wow I'm a mess

any advice?

Kaldin hi and welcome

We really need the DMP files. Please use the following instructions to find and upload them to us. If you are experiencing "permissions problems" chances are you need to drag the files to the desktop first.

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Let us know if you need further assistance

Jan

Kaldin · 02 Aug 2010

Not quite sure why it was so difficult to get those dumps, but I finally got them.

Anyway, over the past few days I have been getting a blue screen on most applications at a seemingly random rate. The BSOD started happening after I reinstalled windows 7 to remove a virus. The BSOD appears to occur mainly on google, google images, youtube, and on occasion just normal applications on my computer (however that is rare).

I have called dell and was assisted through dellconnect. They updated my Bios and my drivers, however that did not fix my problem.

With these dumps hopefully someone can give me an idea on what's wrong?

thank you

and thank you, Jan, for your assistance.

Lordbob75 · 02 Aug 2010

All your dumps were exactly the same, Bugcheck 1E, caused by WUSB54Gv4x64.sys, which is your Linksys Wireless adapter driver.

If possible, update the driver from Dell's website, or from Intel's, and you should be ok.

Code:

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


Loading Dump File [C:\Users\David\AppData\Local\Temp\Temp7_minidump.zip\New folder\080110-20529-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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Sun Aug  1 15:46:26.706 2010 (UTC - 7:00)
System Uptime: 0 days 0:05:52.188
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: 
+3866303438623663
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:  explorer.exe

CURRENT_IRQL:  2

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

TRAP_FRAME:  fffff880009b0890 -- (.trap 0xfffff880009b0890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f405150066e0202c rbx=0000000000000000 rcx=fffffa800717fff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004c6a7cf rsp=fffff880009b0a20 rbp=0000000000000000
 r8=fffffa80071b2a00  r9=0000000000000000 r10=fffffa800712cd00
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`04c6a7cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc432e to fffff80002ccc5d0

STACK_TEXT:  
fffff880`009af8d8 fffff800`02cc432e : fffff880`009af960 fffff880`04d9300f fffff880`009b0050 fffff800`02cf9524 : nt!KeBugCheck
fffff880`009af8e0 fffff800`02cf22ed : fffff800`02edab88 fffff800`02e13a40 fffff800`02c5c000 fffff880`009b07e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009af910 fffff800`02cf9950 : fffff800`02e1ba50 fffff880`009af988 fffff880`009b07e8 fffff800`02c5c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009af940 fffff800`02d068df : fffff880`009b07e8 fffff880`009b0050 fffff880`00000000 fffffa80`0712cd00 : nt!RtlDispatchException+0x410
fffff880`009b0020 fffff800`02ccbc42 : fffff880`009b07e8 fffffa80`071422a0 fffff880`009b0890 fffffa80`070cee40 : nt!KiDispatchException+0x16f
fffff880`009b06b0 fffff800`02cca54a : fffffa80`00000000 00000000`00000001 fffffa80`07fd6010 fffff880`04d96808 : nt!KiExceptionDispatch+0xc2
fffff880`009b0890 fffff880`04c6a7cf : fffffa80`07180000 fffff880`009b0ad0 fffffa80`0712cd00 fffffa80`071422a0 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0a20 fffffa80`07180000 : fffff880`009b0ad0 fffffa80`0712cd00 fffffa80`071422a0 fffffa80`07180000 : WUSB54Gv4x64+0x2d7cf
fffff880`009b0a28 fffff880`009b0ad0 : fffffa80`0712cd00 fffffa80`071422a0 fffffa80`07180000 fffffa80`07129580 : 0xfffffa80`07180000
fffff880`009b0a30 fffffa80`0712cd00 : fffffa80`071422a0 fffffa80`07180000 fffffa80`07129580 00000000`05552301 : 0xfffff880`009b0ad0
fffff880`009b0a38 fffffa80`071422a0 : fffffa80`07180000 fffffa80`07129580 00000000`05552301 f4051500`66e0202c : 0xfffffa80`0712cd00
fffff880`009b0a40 fffffa80`07180000 : fffffa80`07129580 00000000`05552301 f4051500`66e0202c fffffa80`0712cd00 : 0xfffffa80`071422a0
fffff880`009b0a48 fffffa80`07129580 : 00000000`05552301 f4051500`66e0202c fffffa80`0712cd00 fffff880`04c6aa1a : 0xfffffa80`07180000
fffff880`009b0a50 00000000`05552301 : f4051500`66e0202c fffffa80`0712cd00 fffff880`04c6aa1a fffffa80`0716c000 : 0xfffffa80`07129580
fffff880`009b0a58 f4051500`66e0202c : fffffa80`0712cd00 fffff880`04c6aa1a fffffa80`0716c000 fffffa80`07142020 : 0x5552301
fffff880`009b0a60 fffffa80`0712cd00 : fffff880`04c6aa1a fffffa80`0716c000 fffffa80`07142020 fffffa80`071fb000 : 0xf4051500`66e0202c
fffff880`009b0a68 fffff880`04c6aa1a : fffffa80`0716c000 fffffa80`07142020 fffffa80`071fb000 00000000`00000000 : 0xfffffa80`0712cd00
fffff880`009b0a70 fffffa80`0716c000 : fffffa80`07142020 fffffa80`071fb000 00000000`00000000 fffffa80`0712cd00 : WUSB54Gv4x64+0x2da1a
fffff880`009b0a78 fffffa80`07142020 : fffffa80`071fb000 00000000`00000000 fffffa80`0712cd00 fffff880`04c6a96a : 0xfffffa80`0716c000
fffff880`009b0a80 fffffa80`071fb000 : 00000000`00000000 fffffa80`0712cd00 fffff880`04c6a96a fffffa80`0716c000 : 0xfffffa80`07142020
fffff880`009b0a88 00000000`00000000 : fffffa80`0712cd00 fffff880`04c6a96a fffffa80`0716c000 fffffa80`071016f0 : 0xfffffa80`071fb000


STACK_COMMAND:  kb

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

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_0_WUSB54Gv4x64+2d7cf

BUCKET_ID:  X64_0x1E_0_WUSB54Gv4x64+2d7cf

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

~Lordbob

Jonathan_King · 02 Aug 2010

Your Ralink 802.11 USB Wireless Adapter drivers are blamed as the cause. Dated 2006, they are not compatible with Windows 7 RTM.

If you can't find an updated version of the drivers, it would be best to purchase a wireless adapter that is compatible with Windows 7.

Your nVidia graphics drivers are also blamed. They are outdated by about 2 months, so please install the latest version: Drivers - Download NVIDIA Drivers

Now, besides a bad driver (which is very likely), another cause of network-related BSODs is anti-virus. McAfee is well-known for causing BSODs, as well as slowing down your computer. Fortunately, there is a free, lightweight, stable alternative.

Here is the McAfee removal tool: http://download.mcafee.com/products/...tches/MCPR.exe

Here is the best free alternative, Microsoft Security Essentials: http://www.microsoft.com/security_essentials

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug  1 18:39:59.475 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:28.173
BugCheck 1E, {0, 0, 0, 0}
*** 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 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug  1 18:46:26.706 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:52.188
BugCheck 1E, {0, 0, 0, 0}
*** 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 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 01:31:28.570 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:58.053
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Aug  1 20:40:25.685 2010 (UTC - 4:00)
System Uptime: 0 days 0:21:14.168
BugCheck 1E, {0, 0, 0, 0}
*** 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 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  Mcshield.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 01:26:52.166 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:35.274
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Aug  1 13:56:30.135 2010 (UTC - 4:00)
System Uptime: 0 days 1:47:07.316
BugCheck 1E, {0, 0, 0, 0}
*** 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 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 01:10:44.765 2010 (UTC - 4:00)
System Uptime: 0 days 4:29:44.248
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for WUSB54Gv4x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WUSB54Gv4x64.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : WUSB54Gv4x64.sys ( WUSB54Gv4x64+2d7cf )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Kaldin · 04 Aug 2010

I've waited about 24 hours now and no problems =) I reinstalled my Linksys wireless adaptor with it unplugged from the USB port, and plugged it back in when finished. I then updated the driver and everything seems fine now.

The graphics card was updated as well when i spoke to Dell before I even posted here.

I greatly appreciate the help, since it would take sooo much longer to find out what my problem was without it. thank you =)

Jonathan_King · 05 Aug 2010

Thanks for the report! I'm glad to hear it.

If you need anything else, don't hesitate to post.