Hello !
I got my computer about five months and i have never got bluescreen before, but i changed my Hard month ago. So i try to play Call of duty 2 and my computer froze then i need to restart it . then I restart i get Error
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1063
Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004B886D8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\072710-26161-01.dmp
C:\Users\X\AppData\Local\Temp\WER-32869-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
There ya go zip
I got my computer about five months and i have never got bluescreen before, but i changed my Hard month ago. So i try to play Call of duty 2 and my computer froze then i need to restart it . then I restart i get Error
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1063
Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004B886D8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\072710-26161-01.dmp
C:\Users\X\AppData\Local\Temp\WER-32869-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
There ya go zip
Looks like hardware is the cause. Please see this link: Stop 0x124 - what it means and what to try
Download a copy of Memtest86 and burn the ISO to a CD using ISO Recorder. Boot from the CD and leave it running for at least 5 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
ISO Recorder v3
Download a copy of Memtest86 and burn the ISO to a CD using ISO Recorder. Boot from the CD and leave it running for at least 5 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
ISO Recorder v3
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 3 for Minidump.zip\Minidump\072610-23914-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 Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c97e50 Debug session time: Mon Jul 26 06:21:00.476 2010 (GMT-4) System Uptime: 0 days 0:00:06.162 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, fffffa8004bc2688, 0, 0} *** ERROR: Symbol file could not be found. Defaulted to export symbols 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 *** *** *** ************************************************************************* Probably caused by : hardware Followup: MachineOwner ---------
I download memtest and iso recorder . ISO recorder doesn't work on my pc shellexec stopped working it says. So how can i update my bios i download from Asus my bios and there is ROM file i dont know how to use it
Không có nhận xét nào:
Đăng nhận xét