BSOD when watching videos on laptop


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    BSOD when watching videos on laptop


    Hello, everybody!
    I've had a BSOD just a while ago when I was watching clips online and offline using Media Classic at the same time. Here's what I get from debugging the dump file:

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\123014-47346-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`03254e90
    Debug session time: Tue Dec 30 11:11:02.169 2014 (UTC + 7:00)
    System Uptime: 0 days 4:17:12.636
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffff98013588e60, 2, 0, fffff88008dca0e9}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Unable to load image L1C62x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for L1C62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sys
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : L1C62x64.sys ( L1C62x64+70e9 )

    Followup: MachineOwner
    ---------

    Can anyone tell me what should be done? Thank you in advance.

    Also, English is not my mother tongue so please don't criticize me heavily if I make mistakes in grammar and spelling.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\USER\Downloads\Compressed\USER-PC-30_12_14_132928,92\123014-47346-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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`03254e90
    Debug session time: Tue Dec 30 10:11:02.169 2014 (UTC + 6:00)
    System Uptime: 0 days 4:17:12.636
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff98013588e60, 2, 0, fffff88008dca0e9}
    
    *** WARNING: Unable to verify timestamp for L1C62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sys
    Probably caused by : L1C62x64.sys ( L1C62x64+70e9 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff98013588e60, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88008dca0e9, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c00e8
    GetUlongFromAddress: unable to read from fffff800032c0198
     fffff98013588e60 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    L1C62x64+70e9
    fffff880`08dca0e9 4d8b36          mov     r14,qword ptr [r14]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  chrome.exe
    
    TRAP_FRAME:  fffff8800bf6d1a0 -- (.trap 0xfffff8800bf6d1a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000282
    rdx=fffffa80059e2e01 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008dca0e9 rsp=fffff8800bf6d330 rbp=fffff98002eb4fb0
     r8=0000000000000000  r9=0000000000000000 r10=fffff800035404c0
    r11=fffffa80047c72d0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    L1C62x64+0x70e9:
    fffff880`08dca0e9 4d8b36          mov     r14,qword ptr [r14] ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000308ebe9 to fffff8000308f640
    
    STACK_TEXT:  
    fffff880`0bf6d058 fffff800`0308ebe9 : 00000000`0000000a fffff980`13588e60 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0bf6d060 fffff800`0308d860 : fffffa80`03af0c30 fffffa80`0497fd00 00000000`00000000 fffffa80`06428a20 : nt!KiBugCheckDispatch+0x69
    fffff880`0bf6d1a0 fffff880`08dca0e9 : fffffa80`059ad1a0 fffffa80`06428a20 fffff980`02eb4fb0 fffff980`02eb4fb0 : nt!KiPageFault+0x260
    fffff880`0bf6d330 fffffa80`059ad1a0 : fffffa80`06428a20 fffff980`02eb4fb0 fffff980`02eb4fb0 fffffa80`06495780 : L1C62x64+0x70e9
    fffff880`0bf6d338 fffffa80`06428a20 : fffff980`02eb4fb0 fffff980`02eb4fb0 fffffa80`06495780 fffff880`000001c0 : 0xfffffa80`059ad1a0
    fffff880`0bf6d340 fffff980`02eb4fb0 : fffff980`02eb4fb0 fffffa80`06495780 fffff880`000001c0 00000000`00000000 : 0xfffffa80`06428a20
    fffff880`0bf6d348 fffff980`02eb4fb0 : fffffa80`06495780 fffff880`000001c0 00000000`00000000 00000000`00000000 : 0xfffff980`02eb4fb0
    fffff880`0bf6d350 fffffa80`06495780 : fffff880`000001c0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff980`02eb4fb0
    fffff880`0bf6d358 fffff880`000001c0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff980`13588e60 : 0xfffffa80`06495780
    fffff880`0bf6d360 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff980`13588e60 fffff980`13588d30 : 0xfffff880`000001c0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    L1C62x64+70e9
    fffff880`08dca0e9 4d8b36          mov     r14,qword ptr [r14]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  L1C62x64+70e9
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: L1C62x64
    
    IMAGE_NAME:  L1C62x64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51e4eeac
    
    FAILURE_BUCKET_ID:  X64_0xD1_L1C62x64+70e9
    
    BUCKET_ID:  X64_0xD1_L1C62x64+70e9
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm L1C62x64
    start             end                 module name
    fffff880`08dc3000 fffff880`08de5000   L1C62x64 T (no symbols)           
        Loaded symbol image file: L1C62x64.sys
        Image path: L1C62x64.sys
        Image name: L1C62x64.sys
        Timestamp:        Tue Jul 16 12:56:44 2013 (51E4EEAC)
        CheckSum:         0002912C
        ImageSize:        00022000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    MSINFO32:

    • Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter.
    • Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
    • Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).
      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 03:20.
Find Us