BSOD after upgrading to W7

skeets said:

Hey, the other day I upgraded my XP system to windows 7 home premium (see system specs below). Anyways everything went fine or atleast it seemed I installed most of my drivers and applications the only driver I had an issue with was my motherboard drivers.... apparently gigabyte has not released W7 drivers for it yet... so I went ahead and installed the 64bit vista drivers.

Anyways now occasionally when i'm loading new applications or even youtube videos i'll get a BSOD (STOP 0x0000001E) I have reinstalled all the drivers, changed anti virus software from avast to AVG pretty much everything I can think of so I need some help.

edit: also fairly often for no reason that I can tell programs stop responding for short periods of time then go right back to normal.

Minidump file: Download Minidump.zip

CPU-Z screenshots:

CPU: http://img85.imageshack.us/img85/1608/cpue.png
Cache: http://img17.imageshack.us/img17/9081/cachej.png
Memory: http://img191.imageshack.us/img191/4866/memoryt.png
SPD: http://img85.imageshack.us/img85/4448/spd.png
Motherboard: http://img199.imageshack.us/img199/560/motherboard.png

Video card is a GTX 260

anyways help would be great if anyone needs any more info id be happy to supply it.

this one probably caused by your wifi driver WUSB54Gv4x64.sys,.

I would udate it and run a system file check ti verify and repair you system files
typc cmd in search>right click and run as admin>sfc /scannow

also since your dmps show kernal mode exection dl memtestx86 and run it for 5 passes at least.


Ken J+

Code:

122609-12230-01.dmp    12/26/2009 10:58:02 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122609-17768-01.dmp    12/26/2009 5:31:42 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122609-17986-01.dmp    12/26/2009 8:47:10 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122609-20685-01.dmp    12/26/2009 9:21:16 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122709-12058-01.dmp    12/27/2009 7:46:50 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    nwifi.sys    nwifi.sys+a643                    
122709-12573-01.dmp    12/27/2009 2:47:32 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    tcpip.sys    tcpip.sys+16b9a0                    
122709-12745-01.dmp    12/27/2009 6:19:52 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122709-12745-02.dmp    12/27/2009 8:01:56 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122809-13572-01.dmp    12/28/2009 3:30:24 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    nwifi.sys    nwifi.sys+6800                    
122809-14508-01.dmp    12/28/2009 6:28:30 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122809-16645-01.dmp    12/28/2009 5:20:34 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0                    
122809-17487-01.dmp    12/28/2009 3:01:34 PM    KMODE_EXCEPTION_NOT_HANDLED    0x0000001e    00000000`00000000    00000000`00000000    00000000`00000000    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71ed0

Code:

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


Loading Dump File [C:\Users\K\Desktop\Minidump\122809-13572-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
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`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Mon Dec 28 17:28:41.782 2009 (GMT-5)
System Uptime: 0 days 0:27:32.717
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
---------

Ok you were right, the BSOD was caused by the old usb wireless card drivers.... unfortunately linksys doesnt have upgraded drivers so I pulled another PCI card out of another pc, it also doesnt have upgraded drivers but the ones I did find atleast dont cause BSOD.... but instead I have massive latency = /.

So im prob going to end up buying a new card or a really long cable -.-

anyways thanks again at least now i know what my problem is.