BSOD tylko podczas grania Windows 7 64 bit

Page 1 of 3 123 LastLast

  1. Posts : 25
    Windows 7 Ultimate 65bit
       #1

    BSOD tylko podczas grania Windows 7 64 bit


    Hi just while playing gets blue screen looks like this that I play suddenly gray screen with stripes humming sound and restart pc. At first I thought it was caused OCZ reboot because they were damaged, but unfortunately the problem has returned, tested the program, Burn In Test "tab graphics, disk, RAM all PASSED. All discharges from the minidump please and to analyze these errors and am waiting for your help
    Zippyshare.com - Minidump.rar

    new bios
    new drivers
    bones 100% working tested
    Drive tested positive
    cleaned registry programs did not help
    Power was also altered, nothing could
    I have no more ideas! I ask you for help I can se no longer handle that more than half a year; (
      My Computer


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

    Hi.

    You have the error Stop 0x124.

    Stop 0x124 - what it means and what to try
      My Computer


  3. Posts : 25
    Windows 7 Ultimate 65bit
    Thread Starter
       #3

    I read about it did not help; (

    NEXT BSOD !....

    Code:
     
    Loading Dump File [C:\Windows\Minidump\010412-27783-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 (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e9c670
    Debug session time: Wed Jan 4 15:40:52.975 2012 (UTC + 1:00)
    System Uptime: 0 days 0:00:06.318
    *********************************************************************
    * 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
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck 124, {0, fffffa8004acb038, 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    Unable to load image PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 : hardware
     
    Followup: MachineOwner
    ---------
     
    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
     
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004acb038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
     
    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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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.
     
    FAULTING_MODULE: fffff80002c57000 nt
     
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
     
    BUGCHECK_STR: 0x124_AuthenticAMD
     
    CUSTOMER_CRASH_COUNT: 1
     
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
     
    CURRENT_IRQL: 0
     
    STACK_TEXT: 
    fffff880`02fe86f0 fffffa80`04acb038 : 00000000`00000001 00000000`00000000 fffff800`02c1d768 fffffa80`04acb038 : nt+0x4b16cc
    fffff880`02fe86f8 00000000`00000001 : 00000000`00000000 fffff800`02c1d768 fffffa80`04acb038 00000000`00000000 : 0xfffffa80`04acb038
    fffff880`02fe8700 00000000`00000000 : fffff800`02c1d768 fffffa80`04acb038 00000000`00000000 00000000`00000000 : 0x1
     
     
    STACK_COMMAND: kb
     
    FOLLOWUP_NAME: MachineOwner
     
    MODULE_NAME: hardware
     
    IMAGE_NAME: hardware
     
    BUCKET_ID: WRONG_SYMBOLS
     
    Followup: MachineOwner
    ---------
     
    1: kd> lmvm nt
    start end module name
    fffff800`02c57000 fffff800`03240000 nt T (no symbols) 
    Loaded symbol image file: ntoskrnl.exe
    Image path: ntoskrnl.exe
    Image name: ntoskrnl.exe
    Timestamp: Thu Jun 23 04:53:23 2011 (4E02AAA3)
    CheckSum: 0055C228
    ImageSize: 005E9000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mini Kernel Dump does not contain unloaded driver list
    1: kd> lmvm hardware
    start end module name
    Mini Kernel Dump does not contain unloaded driver list
    Last edited by Brink; 05 Jan 2012 at 09:43. Reason: code box
      My Computer


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

    Write here all your system specs,ram,cpu,gpu,psu......everything!

    You had\have a hardware crash\bsod,so the best thing you can do is to check all the hardware's,especially cpu.

    Try,

    Run RAM - Test with Memtest86+ with the right way following the specific tutorial.

    Clean everything inside the case especially cooling fans.

    Download,instal http://www.piriform.com/speccy/download/standard to check temperatures.

    Set bios to default settings.

    Set everything to default settings.

    Update software\drivers.

    Update windows.

    Run 2-3 times SFC /SCANNOW Command - System File Checker

    Run Hardware - Stress Test With Prime95 have always in mind the temperatures.

    Remove ram dimm,leave and work with only one,do this with all the dimms.

    Download and install
    the new version of Driver Sweeper.


    Download the most recent software\driver for your gpu.


    Uninstall gpu software\driver,restart in safe mode,run driver sweeper,choose only Display and clean,restart in normal mode.


    Install the new gpu software\driver,restart.

    Update
    DirectX


    Read carefully the instructions and run
    NVIDIA/AMD Video Card - Test with OCCT
      My Computer


  5. Posts : 25
    Windows 7 Ultimate 65bit
    Thread Starter
       #5

    OCCT has already tested the program and nothing pokazał.Bios was already set to the default but add a link to all temperatures, bios, and various archive your photos and give a link!)
      My Computer


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

    Take a snip\screenshot from the summary of speccy and upload it here using the attachment clip.

    Run Hardware - Stress Test With Prime95 have always in mind the temperatures.
      My Computer


  7. Posts : 25
    Windows 7 Ultimate 65bit
    Thread Starter
       #7

    Just beyond this come from Polish and I will try as far as all the screen to give
    Program already scanning the HD tune and OCCT and all is well and I'm sure the frame also 100%
    I have great hope that you help me solve my problem!)


    Here is a picture I packed it all:

    Zippyshare.com - screen.rar
      My Computer


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

    The file you uploaded in zippyshare is 54MB.

    Please upload only the necessary files here.

    Just follow these simple steps,

    A)Again write here all your system specs,ram,cpu,gpu,psu......everything!

    B) >---> permalink

    C) Run Run Prime95 have always in mind the temperatures and see if you get any errors.
      My Computer


  9. Posts : 25
    Windows 7 Ultimate 65bit
    Thread Starter
       #9

    DualCore AMD Phenom II X2 Black Edition 560, 3149 MHz (16.5 x 191)
    MSI 770-C35/C45 (MS-7599)
    Corsair 430w
    DIMM1: Kingston 9905471-001.A01LF
    DIMM4: SpecTek ZC256M6408V79BD2J-
    Karta Graficzna ATI Radeon HD 5700 Series
    SAMSUNG HD502HJ (500 GB)
      My Computer


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

    You have 2 different models of memory ram?
      My Computer


 
Page 1 of 3 123 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 04:55.
Find Us