Windows 7 blue screen BCCode:1000007e


  1. Posts : 4
    Windows 7 64bit
       #1

    Windows 7 blue screen BCCode:1000007e


    My computer (acer aspire x3900) keeps getting the blue screen of death. The error message tells me this.

    Probleemhandtekening:
    Gebeurtenisnaam van probleem: BlueScreen
    Versie van besturingssysteem: 6.1.7600.2.0.0.768.3
    Landinstelling-id: 2067
    Aanvullende informatie over dit probleem:
    BCCode: 1000007e
    BCP1: FFFFFFFFC0000005
    BCP2: FFFFF88002685BA1
    BCP3: FFFFF880047A29D8
    BCP4: FFFFF880047A2240
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1
    Bestanden die helpen bij het beschrijven van het probleem:
    C:\Windows\Minidump\102110-14976-01.dmp
    C:\Users\robbe.robbe-PC\AppData\Local\Temp\WER-27752-0.sysdata.xml
    Lees de onlineprivacyverklaring:
    Windows 7 Privacy Statement - Microsoft Windows
    Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
    C:\Windows\system32\nl-NL\erofflps.txt


    I'm kinda new to all this so any help would be very thankfull.
    Last edited by FooFighterken; 21 Oct 2010 at 14:20.
      My Computer


  2. Posts : 2,493
    Windows 7 64Bit
       #2
      My Computer


  3. Posts : 4
    Windows 7 64bit
    Thread Starter
       #3

    I attached the extra info :). if anyone could plz help.
      My Computer


  4. Posts : 4
    Windows 7 64bit
    Thread Starter
       #4

    bump
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #5

    Hi, I will take a look and be right back.
    Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`01c56000 PsLoadedModuleList = 0xfffff800`01e93e50
    Debug session time: Thu Oct 21 10:01:01.337 2010 (GMT-4)
    System Uptime: 0 days 3:44:41.430
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ...............
    Unable to load image \SystemRoot\System32\Drivers\L6UX264.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for L6UX264.sys
    *** ERROR: Module load completed but symbols could not be loaded for L6UX264.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88004a9bba1, fffff880047b39d8, fffff880047b3240}
    
    Probably caused by : L6UX264.sys ( L6UX264+19ba1 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88004a9bba1, The address that the exception occurred at
    Arg3: fffff880047b39d8, Exception Record Address
    Arg4: fffff880047b3240, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    L6UX264+19ba1
    fffff880`04a9bba1 66814b0a0020    or      word ptr [rbx+0Ah],2000h
    
    EXCEPTION_RECORD:  fffff880047b39d8 -- (.exr 0xfffff880047b39d8)
    ExceptionAddress: fffff88004a9bba1 (L6UX264+0x0000000000019ba1)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 000000000000000a
    Attempt to write to address 000000000000000a
    
    CONTEXT:  fffff880047b3240 -- (.cxr 0xfffff880047b3240)
    rax=fffffa800422a3b0 rbx=0000000000000000 rcx=fffffa800727d3a8
    rdx=0000000000000000 rsi=fffffa800422a3b0 rdi=fffffa800727d0b8
    rip=fffff88004a9bba1 rsp=fffff880047b3c10 rbp=fffff88009ae3750
     r8=fffffa800407e100  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=fffffa8007f17790 r13=0000000000000000
    r14=0000000000000000 r15=fffff88001cd0f40
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00210282
    L6UX264+0x19ba1:
    fffff880`04a9bba1 66814b0a0020    or      word ptr [rbx+0Ah],2000h ds:002b:00000000`0000000a=????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000001
    
    EXCEPTION_PARAMETER2:  000000000000000a
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001efe0e0
     000000000000000a 
    
    FOLLOWUP_IP: 
    L6UX264+19ba1
    fffff880`04a9bba1 66814b0a0020    or      word ptr [rbx+0Ah],2000h
    
    BUGCHECK_STR:  0x7E
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    LAST_CONTROL_TRANSFER:  from fffffa8008abc490 to fffff88004a9bba1
    
    STACK_TEXT:  
    fffff880`047b3c10 fffffa80`08abc490 : fffff880`09ae3750 fffffa80`03f455a0 fffffa80`0727d0b8 fffff880`047b3c40 : L6UX264+0x19ba1
    fffff880`047b3c18 fffff880`09ae3750 : fffffa80`03f455a0 fffffa80`0727d0b8 fffff880`047b3c40 fffffa80`07f03680 : 0xfffffa80`08abc490
    fffff880`047b3c20 fffffa80`03f455a0 : fffffa80`0727d0b8 fffff880`047b3c40 fffffa80`07f03680 fffffa80`000001b9 : 0xfffff880`09ae3750
    fffff880`047b3c28 fffffa80`0727d0b8 : fffff880`047b3c40 fffffa80`07f03680 fffffa80`000001b9 00000000`00000000 : 0xfffffa80`03f455a0
    fffff880`047b3c30 fffff880`047b3c40 : fffffa80`07f03680 fffffa80`000001b9 00000000`00000000 00000000`00000000 : 0xfffffa80`0727d0b8
    fffff880`047b3c38 fffffa80`07f03680 : fffffa80`000001b9 00000000`00000000 00000000`00000000 fffff800`01ccfcff : 0xfffff880`047b3c40
    fffff880`047b3c40 fffffa80`000001b9 : 00000000`00000000 00000000`00000000 fffff800`01ccfcff fffff880`01cd0f40 : 0xfffffa80`07f03680
    fffff880`047b3c48 00000000`00000000 : 00000000`00000000 fffff800`01ccfcff fffff880`01cd0f40 00000000`00000000 : 0xfffffa80`000001b9
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  L6UX264+19ba1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: L6UX264
    
    IMAGE_NAME:  L6UX264.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4963e541
    
    STACK_COMMAND:  .cxr 0xfffff880047b3240 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_L6UX264+19ba1
    
    BUCKET_ID:  X64_0x7E_L6UX264+19ba1
    
    Followup: MachineOwner
    ---------
    To begin your troubleshooting, please uninstall all McAfee software using this removal tool: Tool. McAfee is known to cause BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on. McAfee is indicated as being part of the crash in your dump.

    You have some outdated drivers on your system. Old drivers can and do cause memory corruption and BSOD's. The first driver listed below was directly blamed for the crashes in three of your dumps.
    L6UX264.sys Tue Jan 06 18:12:01 2009 - Line 6 TonePort UX1 Driver. Line 6 :: Software. Update this driver or uninstall the software.

    mwlPSDFilter.sys Tue Jun 02 06:07:30 2009 - PSD Filter Driver is a driver file from Egis Technology Inc. belonging to EgisTec PrivateSafe Driver. Update this driver or uninstall the software.

    mwlPSDNServ.sys Tue Jun 02 06:07:39 2009 - See above

    mwlPSDVDisk.sys Tue Jun 02 06:15:29 2009 - See above

    netr28x.sys Fri Jun 19 03:56:06 2009 - Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)Ralink corp.. Update your LAN drivers.

    NTIDrvr.sys Tue Mar 24 23:09:39 2009 - NTI CD-ROM Filter Driver by NewTech Infosystems (likely a part of Acer Empowering Technology)OEM none at NTI - Support - OEM Resources - DVD Burning Software, Data Backup Software, CD Burning, Blu-ray Burning Software - Official Site. Update the driver or uninstall the utility.

    UBHelper.sys Mon Apr 27 04:48:19 2009 - NTI CD & DVD-Maker or NTI Backup NOW! or NTI CD-Maker by NewTech Infosystems (usually in Acer Empowering Technology) OEM none at NTI - Support - OEM Resources - DVD Burning Software, Data Backup Software, CD Burning, Blu-ray Burning Software - Official Site. See above.
    How to find drivers:
    - I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.


    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
    Uninstall McAfee, take care of the above drivers and let's see how your system does. If you get another BSOD, upload the dump file. If your system runs smoothly, please post back and let us know. If you need help with the drivers, please ask.
    Last edited by CarlTR6; 21 Oct 2010 at 17:21.
      My Computer


  6. Posts : 11,840
    64-bit Windows 8.1 Pro
       #6

    Your .dmp file is blaming L6UX264.sys as the reason for your crash... I couldn't find which specific program its associated with, but it's a Line6 product. Check Line 6 | Guitar Amplifiers, Effects Pedals, Wireless Microphones, Recording Software to see if there is a version that is supported by Windows 7...
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88004a9bba1, fffff880047b39d8, fffff880047b3240}
    
    Probably caused by : L6UX264.sys ( L6UX264+19ba1 )
    
    Followup: MachineOwner
    ---------
    
    
    SYMBOL_NAME:  L6UX264+19ba1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: L6UX264
    
    IMAGE_NAME:  L6UX264.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4963e541
    
    STACK_COMMAND:  .cxr 0xfffff880047b3240 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_L6UX264+19ba1
    
    BUCKET_ID:  X64_0x7E_L6UX264+19ba1
    
    Followup: MachineOwner
    ---------
    This driver is for Vista and should be updated, or uninstall the associated program

    Code:
    fffff880`04a82000 fffff880`04b4cd00   L6UX264  L6UX264.sys  Tue Jan 06 18:12:01 2009 (4963E541)
      My Computer


  7. Posts : 4
    Windows 7 64bit
    Thread Starter
       #7

    yea, I have line 6 pod farm installed on my computer. that's where the driver comes from. i'll look for a windows 7 update on their site. thank you very much already.
      My Computer


  8. Posts : 11,840
    64-bit Windows 8.1 Pro
       #8

    Let us know how it comes out..
      My Computer


  9. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #9

    Don't forget to update your other outdated drivers and McAfee. Mcafee was also indicated in your dumps.
      My Computer


 

  Related Discussions
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 05:25.
Find Us