I usually avoid to post in stop 0x101 threads as some of the other members have deeper insight about it than me.
Anyway, Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
Code:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows
BTW, the three of your recent BSODs found in the zip are not any stop 0x101. Two are stop 0x50 and one is stop 0x124.
An old BIOS can cause stop 0x124.
Code:
BiosVersion = V3.6
BiosReleaseDate = 07/14/2009
Plan to update it to version 3.9 dated 2011-01-28; from MSI Global ? Motherboard - X58 Platinum SLI
Are you overclocking?
Code:
CPUID: "Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz"
MaxSpeed: 2670
CurrentSpeed: 2673
As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Stress test the CPU.
Hardware - Stress Test With Prime95
Let us know when all are done, and supply the speccy screenshot as soon as possible. It may take a determining role there.
_________________________________________________________________________________________________
Code:
BugCheck 50, {fffff900c0811030, 0, fffff9600033260d, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
Followup: MachineOwner
-------------------------------------------------------------------------------------
BugCheck 50, {fffff900c1e798e0, 0, fffff9600035260d, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d )
Followup: MachineOwner
--------------------------------------------------------------------------------------
BugCheck 124, {0, fffffa8006316028, fe000000, 5000152}
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
Quote