Freezing then crashing into BS. Suggest please

Page 1 of 2 12 LastLast

  1. Posts : 8
    Win 7
       #1

    Freezing then crashing into BS. Suggest please


    Hello everybody!
    I want to ask you for help. Why is my PC always crashes after 10-15 minutes of playing but when i'm not playing - it is good - never crashed during common using.
    After the freezing it shows a blue screen.

    Please help me understand what is wrong with my PC? It is so much annoying when you want to have some "relax time", play your favorite game and then this situation destroys my mood.


    Those who can help in analyzing information from a file - revoke, please help!
    Here is the info within .dmp file that created after the crash:


    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 
    Copyright (c) Microsoft Corporation. All rights reserved. 
     
     
    Loading Dump File [C:\Windows\Minidump\102511-19422-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`03259000 PsLoadedModuleList = 0xfffff800`0349e650 
    Debug session time: Tue Oct 25 18:58:59.589 2011 (UTC + 4:00) 
    System Uptime: 0 days 1:40:03.774 
    ********************************************************************* 
    * 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 
    ...... 
    *** WARNING: Unable to verify timestamp for hal.dll 
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll 
    ******************************************************************************* 
    * * 
    * Bugcheck Analysis * 
    * * 
    ******************************************************************************* 
     
    Use !analyze -v to get detailed debugging information. 
     
    BugCheck 9C, {0, fffff80000ba8bb0, 0, 0} 
     
    ***** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 : ntoskrnl.exe ( nt+7fd00 ) 
     
    Followup: MachineOwner 
    --------- 
     
    0: kd> !analyze -v 
    ******************************************************************************* 
    * * 
    * Bugcheck Analysis * 
    * * 
    ******************************************************************************* 
     
    MACHINE_CHECK_EXCEPTION (9c) 
    A fatal Machine Check Exception has occurred. 
    KeBugCheckEx parameters; 
    x86 Processors 
    If the processor has ONLY MCE feature available (For example Intel 
    Pentium), the parameters are: 
    1 - Low 32 bits of P5_MC_TYPE MSR 
    2 - Address of MCA_EXCEPTION structure 
    3 - High 32 bits of P5_MC_ADDR MSR 
    4 - Low 32 bits of P5_MC_ADDR MSR 
    If the processor also has MCA feature available (For example Intel 
    Pentium Pro), the parameters are: 
    1 - Bank number 
    2 - Address of MCA_EXCEPTION structure 
    3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 
    4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error 
    IA64 Processors 
    1 - Bugcheck Type 
    1 - MCA_ASSERT 
    2 - MCA_GET_STATEINFO 
    SAL returned an error for SAL_GET_STATEINFO while processing MCA. 
    3 - MCA_CLEAR_STATEINFO 
    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 
    4 - MCA_FATAL 
    FW reported a fatal MCA. 
    5 - MCA_NONFATAL 
    SAL reported a recoverable MCA and we don't support currently 
    support recovery or SAL generated an MCA and then couldn't 
    produce an error record. 
    0xB - INIT_ASSERT 
    0xC - INIT_GET_STATEINFO 
    SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 
    0xD - INIT_CLEAR_STATEINFO 
    SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 
    0xE - INIT_FATAL 
    Not used. 
    2 - Address of log 
    3 - Size of log 
    4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO 
    AMD64 Processors 
    1 - Bank number 
    2 - Address of MCA_EXCEPTION structure 
    3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 
    4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error 
    Arguments: 
    Arg1: 0000000000000000 
    Arg2: fffff80000ba8bb0 
    Arg3: 0000000000000000 
    Arg4: 0000000000000000 
     
    Debugging Details: 
    ------------------ 
     
    ***** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 *** 
    *** *** 
    ************************************************************************* 
    ************************************************************************* 
    *** *** 
    *** *** 
    *** 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 *** 
    *** *** 
    ************************************************************************* 
     
    ADDITIONAL_DEBUG_TEXT: 
    Use '!findthebuild' command to search for the target build information. 
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. 
     
    MODULE_NAME: nt 
     
    FAULTING_MODULE: fffff80003259000 nt 
     
    DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd5b 
     
    BUGCHECK_STR: 0x9C_GenuineIntel 
     
    CUSTOMER_CRASH_COUNT: 1 
     
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT 
     
    CURRENT_IRQL: 0 
     
    LAST_CONTROL_TRANSFER: from fffff80003222818 to fffff800032d8d00 
     
    STACK_TEXT: 
    fffff800`00ba8b78 fffff800`03222818 : 00000000`0000009c 00000000`00000000 fffff800`00ba8bb0 00000000`00000000 : nt+0x7fd00 
    fffff800`00ba8b80 00000000`0000009c : 00000000`00000000 fffff800`00ba8bb0 00000000`00000000 00000000`00000000 : hal+0x12818 
    fffff800`00ba8b88 00000000`00000000 : fffff800`00ba8bb0 00000000`00000000 00000000`00000000 00000000`00000000 : 0x9c 
     
     
    STACK_COMMAND: kb 
     
    FOLLOWUP_IP: 
    nt+7fd00 
    fffff800`032d8d00 48894c2408 mov qword ptr [rsp+8],rcx 
     
    SYMBOL_STACK_INDEX: 0 
     
    SYMBOL_NAME: nt+7fd00 
     
    FOLLOWUP_NAME: MachineOwner 
     
    IMAGE_NAME: ntoskrnl.exe 
     
    BUCKET_ID: WRONG_SYMBOLS 
     
    Followup: MachineOwner 
    --------- 
     
    0: kd> lmvm nt 
    start end module name 
    fffff800`03259000 fffff800`03842000 nt T (no symbols) 
    Loaded symbol image file: ntoskrnl.exe 
    Image path: ntoskrnl.exe 
    Image name: ntoskrnl.exe 
    Timestamp: Sat Apr 09 08:15:23 2011 (4D9FDD5B) 
    CheckSum: 0054E319 
    ImageSize: 005E9000 
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Regards, Sam!
    Last edited by Brink; 26 Oct 2011 at 11:58. Reason: code box
      My Computer


  2. Posts : 26,863
    Windows 11 Pro
       #2

    Hello Zimm and welcome to seven forums. The first thing to do is fill in your complte system specs so we know the hardware we are dealing with. In the bottom left of your post click system specs then click update. Update your graphics driver by going to AMD and make sure the driver is current. Keep a close watch on your graphics and CPU temps. Open an elevated command prompt ( click the start button, type cmd in the search box, right ckick on the entry that comes up and select run as administrator, in the command window copy/paste this sfc /scannow then press enter. It is a system file checker and will try to verify and fix any wrong system files. If it finds errors make note of the location of the log files and attach them in a zip file to your next post.. You may like to make a thread in the Crashes and Debugging section of this forum. but first read these instructions to provide them with the info they need. The mini dump and log files you can copy/paste onto your desktop, then right click them and select send to compressed/zip folder and attach the zip folder to your post.
      My Computer


  3. Posts : 8
    Win 7
    Thread Starter
       #3

    Greetings!

    I've attached 3 logs from minidump folder in one archive and the Windows_NT6_BSOD_jcgriff2 folder + PERFMON log in another archive.
    Last edited by zemm; 26 Oct 2011 at 15:48. Reason: Windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML file were added
      My Computer


  4. Posts : 26,863
    Windows 11 Pro
       #4

    Sorry, but I am not qualified to read dump files. Please read this tutorial and attach those files along with your CBS and Dump files in a post to the Crashes and debugging section. Those guys are very good and can provide more help than me.
      My Computer


  5. Posts : 8
    Win 7
    Thread Starter
       #5

    Advice please!!!
      My Computer


  6. Posts : 8
    Win 7
    Thread Starter
       #6

    Guys, what's wrong with my log files?
    I've done everything that is said in the Instruction.
    Really need your help and advice!
      My Computer


  7. Posts : 1,781
    Windows 7 Professional SP1 32-bit
       #7

    Please re-read what essenbe told you 13 hours ago.

    https://www.sevenforums.com/crashes-d...ml#post1631295
      My Computer


  8. Posts : 8
    Win 7
    Thread Starter
       #8

    I've already done everything that wrote essenbe, still freezes and reboots. Only this time, without dump logs.
    What could it be?
      My Computer


  9. Posts : 5,405
    Windows 7 Ultimate 64bit SP1
       #9

    Sorry to interrupt


    OP is good idea to remove Panda Security for diagnostic purposes.


    For a.v. can download and install Microsoft Security Essentials
      My Computer


  10. Posts : 8
    Win 7
    Thread Starter
       #10

    Hello, panais! You're not interrupting at all. I've installed panda 3-4 days ago. Freezing and crashing started to annoy much earlier.
    But i will remove it as you advice - for diagnostic purposes.

    Pardon me, but is that all that my logs say? That Panda may cause BSOD?
      My Computer


 
Page 1 of 2 12 LastLast

  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 18:24.
Find Us