BSOD and Lockups alot in win7

Im having issues with windows 7 x64 build 7600. Im getting alot of freezing all my fans will still be going but hard drive lights will stop. my bios is upto date, so are my chipset and graphic. Then happens mostly when i play games which is really what my pc is for, but i have had it happen just browsing the internet also, and watching video's.

Now ive only had it BSOD once maybe twice, most the time it just freezes and i have to use power button to restart it. Here is a few things from my error log.

I like 10 of these in event viewer.

Code:

 
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
 <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
 
 <EventID>41</EventID> 
 
 <Version>2</Version> 
 
 <Level>1</Level> 
 
 <Task>63</Task> 
 
 <Opcode>0</Opcode> 
 
 <Keywords>0x8000000000000002</Keywords> 
 
 <TimeCreated SystemTime="2009-10-17T04:10:39.591600000Z" /> 
 
 <EventRecordID>12864</EventRecordID> 
 
 <Correlation /> 
 
 <Execution ProcessID="4" ThreadID="8" /> 
 
 <Channel>System</Channel> 
 
 <Computer>Shane-PC</Computer> 
 
 <Security UserID="S-1-5-18" /> 
 
 </System>
 
 
- <EventData>
 <Data Name="BugcheckCode">0</Data> 
 
 <Data Name="BugcheckParameter1">0x0</Data> 
 
 <Data Name="BugcheckParameter2">0x0</Data> 
 
 <Data Name="BugcheckParameter3">0x0</Data> 
 
 <Data Name="BugcheckParameter4">0x0</Data> 
 
 <Data Name="SleepInProgress">false</Data> 
 
 <Data Name="PowerButtonTimestamp">0</Data> 
 
 </EventData>
 
 
 </Event>

I also have this show up in prof logs from time to time.

Code:

The Desktop Window Manager is experiencing heavy resource contention.
Reason : Graphics subsystem resources are over-utilized.
Diagnosis : A sharp degradation in Desktop Window Manager responsiveness was observed.
 
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
 <Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" /> 
 
 <EventID>501</EventID> 
 
 <Version>1</Version> 
 
 <Level>3</Level> 
 
 <Task>4006</Task> 
 
 <Opcode>42</Opcode> 
 
 <Keywords>0x8000000000010000</Keywords> 
 
 <TimeCreated SystemTime="2009-10-14T18:46:24.988400000Z" /> 
 
 <EventRecordID>414</EventRecordID> 
 
 <Correlation ActivityID="{00000100-0000-0000-0C88-55F18B4CCA01}" /> 
 
 <Execution ProcessID="1296" ThreadID="3988" /> 
 
 <Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel> 
 
 <Computer>Shane-PC</Computer> 
 
 <Security UserID="S-1-5-19" /> 
 
 </System>
 
 
- <EventData>
 <Data Name="Reason">2</Data> 
 
 <Data Name="Diagnosis">2</Data> 
 
 </EventData>
 
 
 </Event>

Ive been keeping an eye on my temp with gaming CPU is around 38-40c video 65-70c and HD 34-35c and system temp around 30-34c. So I know im not over heating. Ive also run seagte tools for windows no error, memtest for 8hr no errors. Never had any of these issues with vista x64.

I seen on here a few times people asking for minidumps, I would like to go ahead and throw up I have no idea what a minidump is or where to find it.

Ill also attach some of my data from hwmonitor.

sometimes AVs or firewalls clash with windows 7 stuff. Do you have an AV or firewall installed? If so try disabling windows firewall and defender.

Yes i have AVG i uninstalled it, 30 mins or so ago and was going to try out avast.

Minidumps, if there are any, are to be found in the \Windows\Minidump folder on your machine. Copy the contents of that folder to another location, zip it all up, and upload here.

The first event you posted is just a side-effect of the forced (power button) reboot. You can safely ignore that one for the purposes of this investigation. The second one is more interesting, but it's also unlikely to be the cause of the lockups/BSODs.

It would be a good idea to start with minidump analysis first.

Here is a few minidumps, all from Oct 3rd tho which is while ago. Ive had probley 10-20 freezes sence then. Few other things ive done but forgot to say in first post is, ive ran scf/ scannow thing. One other thing is a few times after then freeze and ive had to hit my reset button ive goten a red kernel screen with weird loader options you have to select ive always chosen default, happened 2 or 3 times.

shamus252 said:

Here is a few minidumps, all from Oct 3rd tho which is while ago. Ive had probley 10-20 freezes sence then. Few other things ive done but forgot to say in first post is, ive ran scf/ scannow thing. One other thing is a few times after then freeze and ive had to hit my reset button ive goten a red kernel screen with weird loader options you have to select ive always chosen default, happened 2 or 3 times.

Unfortunately, your minidumps suggest that the hardware has detected severe problems. Windows is merely passing along this message:

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.

If you're overclocking, that's a bad idea. Otherwise, if the machine is still under warranty, you might want to take it back, explain that the hardware is raising "machine check exceptions" (as per the minidumps), and let them sort it out on their own time - after they give you a new machine.

There's little point in troubleshooting freezes and other potential software problems on a machine with underlying hardware badness.

Sorry about the sub-optimal news

Well that sucks. I think then windows 7 might be killing some people computers cause i never had any issues in vista x64 this all start like 2 or 3 days after installing win 7.

And computer is custom build but most of my parts still have warranty.

shamus252 said:

Well that sucks. I think then windows 7 might be killing some people computers cause i never had any issues in vista x64 this all start like 2 or 3 days after installing win 7.

And computer is custom build but most of my parts still have warranty.

Different drivers "drive" in different ways. It's possible for a newer version of a (software) driver to expose an underlying flaw in hardware which was always there but never previously triggered. That doesn't mean the newer software zapped the hardware and damaged it, or anything like that.

To put it another way, just because the hardware is only now reporting problems doesn't mean they weren't always there to begin with.

You're not over-clocking, are you?