 | |
| |
| 21 Jan 2010 | #1 |
| | BSOD After fresh install I recently installed Windows 7 Ultimate 64 Bit onto a partition on my harddrive. I didn't do a clean install due to needing a few things from a beta install of Windows 7 32 bit on another partition. Currently, the computer runs fine, other than when running flash (through youtube) or bitlord it seems to get the bsod. I'm currently only using firefox with the newest flash plugins installed due to no 64 bit support yet. I've only installed the drivers that windows 7 has given me along with: Adobe Creative Suite Aim 7 K-Lite Codec Magic Disc Magic Iso Maker Microsoft Office Enterprise Mozilla Firefox VLC Media Player |
My System Specs | |
| 21 Jan 2010 | #2 |
| | 
Quote: Originally Posted by Seraphinax  I recently installed Windows 7 Ultimate 64 Bit onto a partition on my harddrive. I didn't do a clean install due to needing a few things from a beta install of Windows 7 32 bit on another partition. Currently, the computer runs fine, other than when running flash (through youtube) or bitlord it seems to get the bsod. I'm currently only using firefox with the newest flash plugins installed due to no 64 bit support yet. I've only installed the drivers that windows 7 has given me along with: Adobe Creative Suite Aim 7 K-Lite Codec Magic Disc Magic Iso Maker Microsoft Office Enterprise Mozilla Firefox VLC Media Player this crash was probably caused by your wifi driver wusb54gv4x64,sys. It is from 2006 and needs to be updaged Ken J+ 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\012110-36000-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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02ca5e50
Debug session time: Thu Jan 21 10:46:42.329 2010 (GMT-5)
System Uptime: 0 days 16:14:38.938
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
---------
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: 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:
+5d04952f02a1dd34
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: fffff88002d1b5b8 -- (.exr 0xfffff88002d1b5b8)
ExceptionAddress: fffff88001c817cf (WUSB54Gv4x64+0x000000000002d7cf)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002d1b660 -- (.trap 0xfffff88002d1b660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=419c250022b011f2 rbx=0000000000000000 rcx=fffffa800505bff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001c817cf rsp=fffff88002d1b7f0 rbp=0000000000000000
r8=fffffa8005331000 r9=0000000000000000 r10=fffffa8004b95010
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`01c817cf ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ad1c2e to fffff80002ad9ed0
STACK_TEXT:
fffff880`02d1a698 fffff800`02ad1c2e : fffffa80`04e991a0 fffffa80`03c1f510 fffff880`02d1ae10 fffff800`02b06e28 : nt!KeBugCheck
fffff880`02d1a6a0 fffff800`02affbed : fffff800`02ce6c24 fffff800`02c1fa3c fffff800`02a68000 fffff880`02d1b5b8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02d1a6d0 fffff800`02b07250 : fffff800`02c27b5c fffff880`02d1a748 fffff880`02d1b5b8 fffff800`02a68000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02d1a700 fffff800`02b141b5 : fffff880`02d1b5b8 fffff880`02d1ae10 fffff880`00000000 fffffa80`04b95010 : nt!RtlDispatchException+0x410
fffff880`02d1ade0 fffff800`02ad9542 : fffff880`02d1b5b8 fffffa80`05104da0 fffff880`02d1b660 fffffa80`04baac40 : nt!KiDispatchException+0x135
fffff880`02d1b480 fffff800`02ad7e4a : fffffa80`00000000 fffff800`02a2e674 fffffa80`0559f010 fffff800`02a2e674 : nt!KiExceptionDispatch+0xc2
fffff880`02d1b660 fffff880`01c817cf : fffffa80`0505c000 00000000`00000002 fffffa80`04b95010 fffffa80`05104da0 : nt!KiGeneralProtectionFault+0x10a
fffff880`02d1b7f0 fffffa80`0505c000 : 00000000`00000002 fffffa80`04b95010 fffffa80`05104da0 fffffa80`0505c000 : WUSB54Gv4x64+0x2d7cf
fffff880`02d1b7f8 00000000`00000002 : fffffa80`04b95010 fffffa80`05104da0 fffffa80`0505c000 fffffa80`051073e0 : 0xfffffa80`0505c000
fffff880`02d1b800 fffffa80`04b95010 : fffffa80`05104da0 fffffa80`0505c000 fffffa80`051073e0 00000000`00000001 : 0x2
fffff880`02d1b808 fffffa80`05104da0 : fffffa80`0505c000 fffffa80`051073e0 00000000`00000001 419c2500`22b011f2 : 0xfffffa80`04b95010
fffff880`02d1b810 fffffa80`0505c000 : fffffa80`051073e0 00000000`00000001 419c2500`22b011f2 fffffa80`0404e100 : 0xfffffa80`05104da0
fffff880`02d1b818 fffffa80`051073e0 : 00000000`00000001 419c2500`22b011f2 fffffa80`0404e100 fffff880`01c81a1a : 0xfffffa80`0505c000
fffff880`02d1b820 00000000`00000001 : 419c2500`22b011f2 fffffa80`0404e100 fffff880`01c81a1a fffffa80`05048000 : 0xfffffa80`051073e0
fffff880`02d1b828 419c2500`22b011f2 : fffffa80`0404e100 fffff880`01c81a1a fffffa80`05048000 00000000`00000000 : 0x1
fffff880`02d1b830 fffffa80`0404e100 : fffff880`01c81a1a fffffa80`05048000 00000000`00000000 fffffa80`03b3d610 : 0x419c2500`22b011f2
fffff880`02d1b838 fffff880`01c81a1a : fffffa80`05048000 00000000`00000000 fffffa80`03b3d610 00000000`00000000 : 0xfffffa80`0404e100
fffff880`02d1b840 fffffa80`05048000 : 00000000`00000000 fffffa80`03b3d610 00000000`00000000 fffffa80`03b3d773 : WUSB54Gv4x64+0x2da1a
fffff880`02d1b848 00000000`00000000 : fffffa80`03b3d610 00000000`00000000 fffffa80`03b3d773 fffff880`01c8196a : 0xfffffa80`05048000
STACK_COMMAND: kb
FOLLOWUP_IP:
WUSB54Gv4x64+2d7cf
fffff880`01c817cf ?? ???
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
--------- |
| My System Specs |
| 21 Jan 2010 | #3 |
| | WUSB54Gv4x64.sys That's your culprit... zzz2496 Edit: Urgh, I need to type faster... |
| My System Specs |
| . |
| |
| 21 Jan 2010 | #4 |
| | Once I get off work, I'll be sure to uninstall it. Though, how do I update it after uninstalling it without a direct connection to the internet? Or do I just update it through windows 7? And you people are faster than WoW forums~ |
| My System Specs |
| 21 Jan 2010 | #5 |
| | Some of us are keeping an eye (or a monitor + a browser window) to this forum...  |
| My System Specs |
 |
BSOD After fresh install problems?
| Thread Tools | |
| Similar help and support threads for: BSOD After fresh install | ||||
| Thread | Forum | |||
| BSOD playing Guild Wars 2, recent SSD install and fresh install of W7 | BSOD Help and Support | |||
 BSOD on fresh install when install updates, misc error codes | BSOD Help and Support | |||
| Often BSOD since fresh install 7 64x ult... | BSOD Help and Support | |||
| BSOD crashes after fresh install of 7 64bit install | BSOD Help and Support | |||
| Random BSOD - Fresh install, fresh system | BSOD Help and Support | |||
All times are GMT -5. The time now is 06:14 AM.
