Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Repeating Locale ID 1033


11 May 2010   #1

Windows 7 Home Premium
 
 
BSOD Repeating Locale ID 1033

Hey I just built my own computer and this is what I have gotten.
It normally only happens when I am downloading large amounts of information.
The DXDiag is attached

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050610-22713-01.dmp
C:\Users\Allen\AppData\Local\Temp\WER-40170-0.sysdata.xml

My System SpecsSystem Spec
.

11 May 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Shadyfellow View Post
Hey I just built my own computer and this is what I have gotten.
It normally only happens when I am downloading large amounts of information.
The DXDiag is attached

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050610-22713-01.dmp
C:\Users\Allen\AppData\Local\Temp\WER-40170-0.sysdata.xml


These were all caused by your Linksys wireless driver. I would download a fresh copy and install it.

Let us know if you need help

Ken


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\New folder (3)\050610-16536-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c51e50
Debug session time: Thu May  6 21:28:53.170 2010 (GMT-4)
System Uptime: 0 days 0:11:48.325
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
---------

6: 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: 
+6445952f035ed900
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

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

TRAP_FRAME:  fffff88003128890 -- (.trap 0xfffff88003128890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=4c69230003e0d0ba rbx=0000000000000000 rcx=fffffa80077dbff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001e9b7cf rsp=fffff88003128a20 rbp=0000000000000000
 r8=fffffa8007975400  r9=0000000000000000 r10=fffffa8007457c80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WUSB54Gv4x64+0x2d7cf:
fffff880`01e9b7cf ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7dc2e to fffff80002a85ed0

STACK_TEXT:  
fffff880`031278c8 fffff800`02a7dc2e : fffffa80`f9e42ad2 00000006`08fd3db0 fffff880`03128040 fffff800`02ab2e28 : nt!KeBugCheck
fffff880`031278d0 fffff800`02aabbed : fffff800`02c92c24 fffff800`02bcba3c fffff800`02a14000 fffff880`031287e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03127900 fffff800`02ab3250 : fffff800`02bd3a88 fffff880`03127978 fffff880`031287e8 fffff800`02a14000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03127930 fffff800`02ac01b5 : fffff880`031287e8 fffff880`03128040 fffff880`00000000 fffffa80`07457c80 : nt!RtlDispatchException+0x410
fffff880`03128010 fffff800`02a85542 : fffff880`031287e8 fffffa80`0781ee70 fffff880`03128890 fffffa80`07772e40 : nt!KiDispatchException+0x135
fffff880`031286b0 fffff800`02a83e4a : fffffa80`00000000 00000000`00000001 fffffa80`08211010 fffff880`01f43808 : nt!KiExceptionDispatch+0xc2
fffff880`03128890 fffff880`01e9b7cf : fffffa80`077dc000 fffff880`03128ad0 fffffa80`07457c80 fffffa80`0781ee70 : nt!KiGeneralProtectionFault+0x10a
fffff880`03128a20 fffffa80`077dc000 : fffff880`03128ad0 fffffa80`07457c80 fffffa80`0781ee70 fffffa80`077dc000 : WUSB54Gv4x64+0x2d7cf
fffff880`03128a28 fffff880`03128ad0 : fffffa80`07457c80 fffffa80`0781ee70 fffffa80`077dc000 fffffa80`0780ca60 : 0xfffffa80`077dc000
fffff880`03128a30 fffffa80`07457c80 : fffffa80`0781ee70 fffffa80`077dc000 fffffa80`0780ca60 00000000`07454d01 : 0xfffff880`03128ad0
fffff880`03128a38 fffffa80`0781ee70 : fffffa80`077dc000 fffffa80`0780ca60 00000000`07454d01 4c692300`03e0d0ba : 0xfffffa80`07457c80
fffff880`03128a40 fffffa80`077dc000 : fffffa80`0780ca60 00000000`07454d01 4c692300`03e0d0ba fffffa80`07457c80 : 0xfffffa80`0781ee70
fffff880`03128a48 fffffa80`0780ca60 : 00000000`07454d01 4c692300`03e0d0ba fffffa80`07457c80 fffff880`01e9ba1a : 0xfffffa80`077dc000
fffff880`03128a50 00000000`07454d01 : 4c692300`03e0d0ba fffffa80`07457c80 fffff880`01e9ba1a fffffa80`077c8000 : 0xfffffa80`0780ca60
fffff880`03128a58 4c692300`03e0d0ba : fffffa80`07457c80 fffff880`01e9ba1a fffffa80`077c8000 fffffa80`0780dda0 : 0x7454d01
fffff880`03128a60 fffffa80`07457c80 : fffff880`01e9ba1a fffffa80`077c8000 fffffa80`0780dda0 00000000`00000000 : 0x4c692300`03e0d0ba
fffff880`03128a68 fffff880`01e9ba1a : fffffa80`077c8000 fffffa80`0780dda0 00000000`00000000 fffffa80`07454dc0 : 0xfffffa80`07457c80
fffff880`03128a70 fffffa80`077c8000 : fffffa80`0780dda0 00000000`00000000 fffffa80`07454dc0 fffffa80`07457c80 : WUSB54Gv4x64+0x2da1a
fffff880`03128a78 fffffa80`0780dda0 : 00000000`00000000 fffffa80`07454dc0 fffffa80`07457c80 fffff880`01e9b96a : 0xfffffa80`077c8000
fffff880`03128a80 00000000`00000000 : fffffa80`07454dc0 fffffa80`07457c80 fffff880`01e9b96a fffffa80`077c8000 : 0xfffffa80`0780dda0


STACK_COMMAND:  kb

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

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 SpecsSystem Spec
Reply

 BSOD Repeating Locale ID 1033




Thread Tools



Similar help and support threads for2: BSOD Repeating Locale ID 1033
Thread Forum
BSOD Locale ID 1033 BSOD Help and Support
BSOD Locale ID:1033 BSOD Help and Support
BSOD Locale ID 1033...when doing just about anything BSOD Help and Support
BSOD Locale 1033 BC 1a, 3b, 24, etc. BSOD Help and Support
BSOD repeating - local id 1033 BSOD Help and Support
BSOD Locale ID 1033 BSOD Help and Support
BSOD Locale ID 1033 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:41 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33