Constant BSOD's, all different error codes. 0x0000000a

[Arecks]

I've had this custom PC for a little while, since the Christmas before last, and for a while it had been working fine. But around January of this year I started getting BSOD's all over the place, most of the time them all with different error codes. The only thing that's the same about them is they all point to ntoskrnl.exe being the failure. I'm not sure what that's supposed to mean, so I'd like to get some support on this issue. The most recent crash that happened about 10 minutes ago was:

IRQL_NOT_LESS_OR_EQUAL.
0x0000000a
fffff683`ff738be0
00000000`00000000
00000000`00000000
fffff800`030955b7

 

[koolkat77]

Overclocking
If you are overclocking any hardware, STOP. Reset any changed values back to default.

Basic checks:
Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Check for a BIOS update.

BIOS Version/Date	American Megatrends Inc. 5.16, 6/3/2010

If you continue to get BSOD's run driver verifier.
Driver Verifier
Let's run driver verifier and see if it catches any misbehaving drivers: Driver Verifier - Enable and Disable

 

[Faladu]

NTOSKRNL.EXE is the MAIN engine program of Windows 7, if that is having fits, your problems are MAJOR as far as the OS is concerned.

ok so that A BSOD code was last, but before that you have a 7e on dxgmms1.sys

One thing for that particular error is this: [a Windows update, get the one for 64 or 32bit whichever variant u run]

The October 2009 stability and reliability update for Windows 7 and Windows Server 2008 R2 is available.

I would reinstall Direct-X also.

Some replaced their video cards to fix it, a bit extreme.

You have scanned for viruses and registry errors?

Start by doing all that stuff that koolkat said though.

Recommendations included all latest drivers: video, motherboard chipset, look at BIOS firmware update also. (get these from the manufacturer's website of the video card/motherboard, not generic ones from intel or amd, FIRST!)

Get CPU-Z and GPU-Z from cpuid.com and run them [+ msinfo32.exe built into windows will give you some info as well.]
You need the specific chipset (Mainboard tab on CPU-Z) if running the wrong mobo chipset, issues would be plentiful, chipset includes southbridge found in CPU-Z, just FYI.

 

[Faladu]

BSOD's usually caused by:

RAM gone bad (Video or main)
drivers (so many, and using a wrong one )
file corruption (volatile environment are computers and their operating systems) [includes HD/Power failures]
viruses (pure evil)

That's a lot of ground to troubleshoot, patience is a virtue for a reason.