Need some help with 0x0000001e BSOD


  1. Lex
    Posts : 2
    64 BIT
       New #1

    Need some help with 0x0000001e BSOD


    I bought my computer from novatech with vista and upgraded to windows 7. Ever since then i have experienced BSOD's with the code 0x0000001e ... I took the machine back to novatech and they 'stress tested' it claiming it was fine, they said it could be dust. I took it home and the next day experienced a memory dump again!!

    I have searched around and used 'whocrashed' to analyse what the problem could be its says it could be ntoskrnl.exe but also i found out that it could be due to my Linksys WUSB54Gv4.

    But what i do now i don't really know!
    Please find attached my memory dump file.

    Can anyone help?
      My Computer
    Quote Quote

  3. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       New #2

    Lex said:
    I bought my computer from novatech with vista and upgraded to windows 7. Ever since then i have experienced BSOD's with the code 0x0000001e ... I took the machine back to novatech and they 'stress tested' it claiming it was fine, they said it could be dust. I took it home and the next day experienced a memory dump again!!

    I have searched around and used 'whocrashed' to analyse what the problem could be its says it could be ntoskrnl.exe but also i found out that it could be due to my Linksys WUSB54Gv4.

    But what i do now i don't really know!
    Please find attached my memory dump file.
    Can anyone help?
    Lex you are probably correct - Please refer report below.
    Suggest you install a fresh copy of the USB Driver asap.
    Please report back with your results.
    Jan.






    Code:
     
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\JMH\Desktop\032910-21964-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`03094e50
Debug session time: Tue Mar 30 05:34:41.759 2010 (GMT+11)
System Uptime: 0 days 0:29:04.446
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: 
+0
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:  fffff80000b9c578 -- (.exr 0xfffff80000b9c578)
ExceptionAddress: fffff880026447cf (WUSB54Gv4x64+0x000000000002d7cf)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME:  fffff80000b9c620 -- (.trap 0xfffff80000b9c620)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=a5bf1400fae02090 rbx=0000000000000000 rcx=fffffa8007c2eff0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880026447cf rsp=fffff80000b9c7b0 rbp=0000000000000000
 r8=fffffa8007b1a900  r9=0000000000000000 r10=fffffa80074fde70
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
WUSB54Gv4x64+0x2d7cf:
fffff880`026447cf ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ec0c2e to fffff80002ec8ed0
STACK_TEXT:  
fffff800`00b9b658 fffff800`02ec0c2e : fffffa80`04663030 fffffa80`04663030 fffff800`00b9bdd0 fffff800`02ef5e28 : nt!KeBugCheck
fffff800`00b9b660 fffff800`02eeebed : fffff800`030d5c24 fffff800`0300ea3c fffff800`02e57000 fffff800`00b9c578 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b690 fffff800`02ef6250 : fffff800`03016b5c fffff800`00b9b708 fffff800`00b9c578 fffff800`02e57000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b6c0 fffff800`02f031b5 : fffff800`00b9c578 fffff800`00b9bdd0 fffff800`00000000 fffffa80`074fde70 : nt!RtlDispatchException+0x410
fffff800`00b9bda0 fffff800`02ec8542 : fffff800`00b9c578 fffffa80`039d9bf0 fffff800`00b9c620 fffffa80`05de6780 : nt!KiDispatchException+0x135
fffff800`00b9c440 fffff800`02ec6e4a : fffffa80`00000000 00000000`00000001 fffffa80`08485010 fffff880`02773808 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c620 fffff880`026447cf : fffffa80`07c2f000 fffff800`00b9c860 fffffa80`074fde70 fffffa80`039d9bf0 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c7b0 fffffa80`07c2f000 : fffff800`00b9c860 fffffa80`074fde70 fffffa80`039d9bf0 fffffa80`07c2f000 : WUSB54Gv4x64+0x2d7cf
fffff800`00b9c7b8 fffff800`00b9c860 : fffffa80`074fde70 fffffa80`039d9bf0 fffffa80`07c2f000 fffffa80`076f5850 : 0xfffffa80`07c2f000
fffff800`00b9c7c0 fffffa80`074fde70 : fffffa80`039d9bf0 fffffa80`07c2f000 fffffa80`076f5850 00000000`07985c01 : 0xfffff800`00b9c860
fffff800`00b9c7c8 fffffa80`039d9bf0 : fffffa80`07c2f000 fffffa80`076f5850 00000000`07985c01 a5bf1400`fae02090 : 0xfffffa80`074fde70
fffff800`00b9c7d0 fffffa80`07c2f000 : fffffa80`076f5850 00000000`07985c01 a5bf1400`fae02090 fffffa80`074fde70 : 0xfffffa80`039d9bf0
fffff800`00b9c7d8 fffffa80`076f5850 : 00000000`07985c01 a5bf1400`fae02090 fffffa80`074fde70 fffff880`02644a1a : 0xfffffa80`07c2f000
fffff800`00b9c7e0 00000000`07985c01 : a5bf1400`fae02090 fffffa80`074fde70 fffff880`02644a1a fffffa80`07c1b000 : 0xfffffa80`076f5850
fffff800`00b9c7e8 a5bf1400`fae02090 : fffffa80`074fde70 fffff880`02644a1a fffffa80`07c1b000 fffffa80`076e6b90 : 0x7985c01
fffff800`00b9c7f0 fffffa80`074fde70 : fffff880`02644a1a fffffa80`07c1b000 fffffa80`076e6b90 fffffa80`07985c01 : 0xa5bf1400`fae02090
fffff800`00b9c7f8 fffff880`02644a1a : fffffa80`07c1b000 fffffa80`076e6b90 fffffa80`07985c01 00000000`00000000 : 0xfffffa80`074fde70
fffff800`00b9c800 fffffa80`07c1b000 : fffffa80`076e6b90 fffffa80`07985c01 00000000`00000000 fffffa80`074fde70 : WUSB54Gv4x64+0x2da1a
fffff800`00b9c808 fffffa80`076e6b90 : fffffa80`07985c01 00000000`00000000 fffffa80`074fde70 fffff880`0264496a : 0xfffffa80`07c1b000
fffff800`00b9c810 fffffa80`07985c01 : 00000000`00000000 fffffa80`074fde70 fffff880`0264496a fffffa80`07c1b000 : 0xfffffa80`076e6b90
fffff800`00b9c818 00000000`00000000 : fffffa80`074fde70 fffff880`0264496a fffffa80`07c1b000 fffffa80`07589ac0 : 0xfffffa80`07985c01
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
WUSB54Gv4x64+2d7cf
fffff880`026447cf ??              ???
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> lmvm WUSB54Gv4x64
start             end                 module name
fffff880`02617000 fffff880`02669000   WUSB54Gv4x64 T (no symbols)           
    Loaded symbol image file: WUSB54Gv4x64.sys
    Image path: \SystemRoot\system32\DRIVERS\WUSB54Gv4x64.sys
    Image name: WUSB54Gv4x64.sys
    Timestamp:        Wed Dec 27 20:41:31 2006 (45923FCB)
    CheckSum:         00053254
    ImageSize:        00052000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer
    Quote Quote

  4. Lex
    Posts : 2
    64 BIT
    Thread Starter
       New #3

    Success!! I uninstalled and reinstalled the driver for wireless linksys and have had no memory dumps since!!
    thank you
      My Computer
    Quote Quote

  6. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       New #4

    Lex said:
    Success!! I uninstalled and reinstalled the driver for wireless linksys and have had no memory dumps since!!
    thank you
    Lex,
    Great news, I am so pleased for you. :)
    Enjoy Win 7. Safe surfing.
    Jan.
      My Computer
    Quote Quote

 

  Related Discussions
BSOD 0x0000001E
in BSOD Help and Support

Hello friends of SevenForums, My laptop is lately showing up BSOD's with error code 0x0000001E, I could really use some help with this. I included the dumpfiles as shown in this thread. Thanks in advance. Sincerely, Roald
BSOD 0x0000001e
in BSOD Help and Support

Hello ! First, sorry if my english is bad. I'm french but I'll try to do my best. So, I've got some troubles with my dell studio 1557. Generally after a random time it crashed with a beautiful BSOD ( error code : 0x0000001e ). Sometimes it freezes and I can't do anything and sometimes I have...
BSOD - 0x0000001e
in BSOD Help and Support

Hi, I've recently re-installed my PC, since it was giving me quite a few BSoD's while playing games. The BSoD's when gaming are gone, but if I leave it overnight, it seems to crash. Now, I am aware that 0x1e can relate to device drivers, so it might be a driver-update is needed, but I can't...
Always 0x0000001e BSOD
in BSOD Help and Support

Hello, i have the BSOD 0x0000001e quite everyday. Can you help me? - x86 (32-bit) or x64 ? X64 - the original installed OS on the system? Windows 7 - an OEM or full retail version? Full retail - What is the age of system (hardware)? 2years - What is the age of OS installation (have you...
BSOD 0x0000001E - please help me :'(
in BSOD Help and Support

Hi, i'm constantly getting this BSOD - even on my first attempt to post this thread oO It seems to occur pretty randomly, mostly while i'm playing (which consumes most of my pc time ^^). I attached the Minidump File, hopefully someone can help me out with that issue :) Thanks a lot in advance...
Our Sites
Site Links
About 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:58.
Find Us