multiple BSOD (IRQL_NOT_LESS_OR_EQUAL 0x0000000a)

Lets run SFC

Click on the - type cmd in Search Box -> CMD find at top and RIGHT CLICK - RUN AS ADMIN

Enter this at the prompt -

Code:

sfc /scannow

How to Repair Windows 7 System Files with System File Checker

SFC /SCANNOW Command - System File Checker

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffc00051b50c0, 2, 1, fffff80002cf8240}

	
Code:
	
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

Followup: MachineOwner
--------------------------------------------------------------------------------------------------------------
BugCheck 1000007E, {ffffffffc0000005, fffff88004578b55, fffff88009794898, fffff880097940f0}

	
Code:
	
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
-------------------------------------------------------------------------------------------------------------
Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a802d243b0, 0, fffff880053ced38, 5}

	
Code:
	
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+1c )

Followup: MachineOwner
-------------------------------------------------------------------------------------------------------------

These are the three stopcodes you are getting. These are not specifying anything unfortunately, but gives us a prima facie conception about the probable cause. You do the following:

• 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.
• Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
  Download, install and update those, and then run full system scans with both of them, one by one.
• Update your ATI/AMD display driver.
  You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.
  
  
  During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.
• Try to Update the BIOS
  
  Code:

  BIOS-versie/datum    American Megatrends Inc. P2.80, 31-10-2011

Let us know the results.

Did all the above.

Removed avast and installed MSE en MBAM, run the test, gave no warnings
Updated the ATI drivers to the latest 13.1
Bios was already the newest version 2.80

Did the memtest, 7 passes, 10 hours testing, non errors

What about my BIOS settings? can that trigger an BSOD? Maybe my memory settings are not right?

Keep you informed.

Edit:

After restart got multiple BSOD again.
Did removed the Catalys ATI drivers and worked with the standard vga driver. No BSOD after this.
I supose the fauls are due the videodrivers? I have 2 videocards (crossfire).
Is it possible that one of the card or both has an defect? Or is it more likely that is is because of an faulty driver?

Edit 2:

Also in this mode without the ATI drivers i get an BSOD after 10 minutes

I framed an idea after seeing your data for the first time (no expressed though, as those are hard to say from the part of a remote debugger), but want to see the newer ones. I expect the same random bugchecks there, too.

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

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.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Well i think it is officialy solved. Started my pc today and no BSOD at all. Did an burn-in test for about 15 minuts and no errors.
"normaly" the first startup BSOD always on me. Happy that is it solved but verry curios what the problem was.

I did an complete memtest serveral times and no errors there. So i think the memory was fine but when i used 3x2gb instead of 4 x 2gb the BSOD disapeared. I swapped this last added 1 x 2gb but did also did not changed, no BSODs. So the memory is fine but when installing to much memory it BSOD? Strange because bought he PC with x42gb and runned it faultless over 1,5 years?

Any users with an Asrock X58 extrem 3 who can explain this

Well officialy solved now. No BSOD anymore.
Removed MSE and istalled my old virus scanner again.
Runned memtest overnight no errors. Think the error was on the motherboard ram slot.