Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Daily BSODs due to Unknown Hardware Failure


09 May 2011   #1

Windows 7 Home Premium x64
 
 
Daily BSODs due to Unknown Hardware Failure

My system has been having BSODs more and more frequently since I built the computer. It originally occurred once a week like clockwork however now it happens twice a day usually. I have run a Debug test using the WinDbg Tool and received the following results from the one today.

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

Loading Dump File [C:\Windows\Minidump\050911-22963-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 \SystemRoot\system32\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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03259000 PsLoadedModuleList = 0xfffff800`03496e50
Debug session time: Mon May 9 03:18:53.872 2011 (UTC - 4:00)
System Uptime: 0 days 12:51:27.106
*********************************************************************
* 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 \SystemRoot\system32\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 124, {0, fffffa800c2c7028, be000000, 300136}
***** 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 \SystemRoot\system32\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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware
Followup: MachineOwner
---------

I am unsure as to how to procede and what may be the issue. I thought it could have been caused by my old Wireless-G PCI Adapter that was not certified for Windows 7 so I replaced the card with a N150 Wireless USB Adapter. It seems to happen the most frequently while I am watching Netflix or playing an online game but it also occurs in the middle of the night when I am sleeping too. Any advice on what I should do next would help quite a bit. Thank You!

My System SpecsSystem Spec
.

09 May 2011   #2

Windows 7 Home Premium x64
 
 

Here's the resources report and DMP files also.
My System SpecsSystem Spec
10 May 2011   #3

Windows 7 Home Premium x64
 
 

Could really use some help here. It's happened two more times tonight and I still have not had any response about what might be causing the issue. I've just tried using an XMP profile for my memory and instructing CMOS not to Halt on Errors. I'm including another zip file with the new DMP files. Will repost if anything improves with the new memory profile.
My System SpecsSystem Spec
.


10 May 2011   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64bit
 
 

I ran all 35 dumps. All but two were STOP 0x124
Stop 0x124 - what it means and what to try

It shows that your CPU is overclocked. Overclocking can cause the STOP 0x124 error. I would set everything to stock and see if the crashes continue. Please also remove the XMP profile for your memory.

Code:
Event[92]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2011-05-10T02:11:07.931
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Adam-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\THRM has been enumerated.             
_PSV = 323K             
_TC1 = 4             
_TC2 = 3             
_TSP = 6000ms             
_AC0 = 323K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 6553K <-- That would be over 11,000 degrees Fahrenheit!         
_HOT = 0K             
_PSL - see event data.

Event[93]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2011-05-10T02:11:07.744
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Adam-PC
  Description: 
Processor 1 in group 0 exposes the following:

1 idle state(s)
0 performance state(s)
0 throttle state(s)

Event[94]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2011-05-10T02:11:07.744
  Event ID: 35
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Adam-PC
  Description: 
Performance power management features on processor 1 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.

Event[95]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2011-05-10T02:11:07.744
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Adam-PC
  Description: 
Processor 5 in group 0 exposes the following:

1 idle state(s)
0 performance state(s)
0 throttle state(s)

Event[96]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2011-05-10T02:11:07.744
  Event ID: 35
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Adam-PC
  Description: 
Performance power management features on processor 5 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.
Looking through your event logs, it appears that you need to update your BIOS. Download the latest BIOS and install it using one of the methods listed below

information   Information

INSTRUCTIONS: BIOS updating can be accomplished VIA one of the below methods:
CD Method (Blank CD and CD Rewritable Drive Required)
  • Download the following .iso file: E767_82.iso
  • Use CD Burning software to burn the .iso image onto a blank CD (Nero, Alochol 120%, MagicISO etc.)
  • After it has burned, insert CD and restart the machine, go into the BIOS and load defaults, save and exit.
  • Now set the CD Drive as the primary boot device, or press escape while the system is booting to select CD as the bootable device.
  • After flash remove the CD, and power off PC Completely.
  • Turn on the PC and load defaults in BIOS
USB Flash Drive Installation
  • Download E76882.bin.
  • Visit this thread and follow the installation instructions. (thanks 30h6).

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests


BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue May 10 02:06:34.257 2011 (UTC - 4:00)
System Uptime: 0 days 1:18:01.490
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue May 10 00:47:36.227 2011 (UTC - 4:00)
System Uptime: 0 days 21:27:21.461
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon May  9 03:18:53.872 2011 (UTC - 4:00)
System Uptime: 0 days 12:51:27.106
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  8 14:26:08.169 2011 (UTC - 4:00)
System Uptime: 0 days 15:58:41.402
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat May  7 22:26:04.877 2011 (UTC - 4:00)
System Uptime: 0 days 3:31:05.110
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat May  7 18:54:10.314 2011 (UTC - 4:00)
System Uptime: 1 days 12:02:18.547
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri May  6 06:50:50.228 2011 (UTC - 4:00)
System Uptime: 0 days 13:49:34.335
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu May  5 16:59:55.996 2011 (UTC - 4:00)
System Uptime: 0 days 12:09:43.230
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu May  5 04:49:22.946 2011 (UTC - 4:00)
System Uptime: 1 days 5:24:43.992
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  1 06:54:10.532 2011 (UTC - 4:00)
System Uptime: 0 days 1:11:09.562
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  1 05:41:26.757 2011 (UTC - 4:00)
System Uptime: 0 days 2:55:30.787
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun May  1 02:44:59.717 2011 (UTC - 4:00)
System Uptime: 1 days 9:58:11.064
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 29 16:45:17.364 2011 (UTC - 4:00)
System Uptime: 0 days 2:30:30.394
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 29 14:13:25.369 2011 (UTC - 4:00)
System Uptime: 0 days 14:31:05.399
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Apr 28 23:41:00.926 2011 (UTC - 4:00)
System Uptime: 0 days 20:11:41.956
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr 27 08:06:23.110 2011 (UTC - 4:00)
System Uptime: 0 days 11:30:54.140
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr 26 20:34:15.328 2011 (UTC - 4:00)
System Uptime: 1 days 20:16:20.248
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Apr 22 21:28:55.823 2011 (UTC - 4:00)
System Uptime: 1 days 5:24:05.040
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Apr 21 16:03:41.576 2011 (UTC - 4:00)
System Uptime: 4 days 1:05:25.793
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  coreServiceShe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr 17 14:57:11.862 2011 (UTC - 4:00)
System Uptime: 0 days 2:22:46.080
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr 17 12:33:24.283 2011 (UTC - 4:00)
System Uptime: 0 days 21:12:51.150
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr 16 00:40:18.731 2011 (UTC - 4:00)
System Uptime: 2 days 3:48:48.948
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Apr  6 07:21:11.026 2011 (UTC - 4:00)
System Uptime: 1 days 2:03:49.244
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Apr  5 05:16:03.215 2011 (UTC - 4:00)
System Uptime: 0 days 1:14:54.433
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 05:27:24.766 2011 (UTC - 4:00)
System Uptime: 0 days 4:27:44.448
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 00:58:31.853 2011 (UTC - 4:00)
System Uptime: 4 days 23:20:19.883
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Mar 25 07:48:15.933 2011 (UTC - 4:00)
System Uptime: 1 days 12:31:51.151
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  CivilizationV_
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar 23 19:15:33.299 2011 (UTC - 4:00)
System Uptime: 0 days 19:34:09.330
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  CivilizationV_
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar 19 10:43:21.032 2011 (UTC - 4:00)
System Uptime: 1 days 12:59:08.139
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+297 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VidSchiUpdateContextStatus+297
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar 17 21:43:07.574 2011 (UTC - 4:00)
System Uptime: 2 days 6:29:25.604
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 15 00:11:31.340 2011 (UTC - 4:00)
System Uptime: 2 days 0:02:02.228
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Mar 13 00:08:35.420 2011 (UTC - 4:00)
System Uptime: 3 days 17:58:21.638
*** WARNING: Unable to verify timestamp for tmcomm.sys
*** ERROR: Module load completed but symbols could not be loaded for tmcomm.sys
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  SearchFilterHo
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  9 06:09:24.443 2011 (UTC - 4:00)
System Uptime: 9 days 23:40:49.758
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 27 06:28:08.791 2011 (UTC - 4:00)
System Uptime: 6 days 9:09:14.822
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 20 21:16:16.770 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:34.689
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
CPUID:        "Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3591
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
Reply

 Daily BSODs due to Unknown Hardware Failure




Thread Tools



Similar help and support threads for2: Daily BSODs due to Unknown Hardware Failure
Thread Forum
Daily BSODs. Can't figure out if its GPU or RAM. Please help. BSOD Help and Support
Repeats daily BSODs BSOD Help and Support
Daily BSODs, Need Help BSOD Help and Support
Daily BSODs BSOD Help and Support
Multiple Different BSODs Daily BSOD Help and Support
New Build - Daily BSODs BSOD Help and Support
Daily BSODs BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 10:59 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33