📎 AI Summary:
The thread discusses a Windows 7 reinstallation issue where the user encounters blue screens with the IRQL less or not equal error. The second poster analyzes dump files, suggesting possible causes like faulty RAM, drivers, or BIOS issues, and recommends updating drivers and testing RAM with Memtest86 if problems persist. Overall, the guidance emphasizes troubleshooting hardware components and software updates to resolve the BSOD errors.

adolfin

New Member
Member details
Joined
Jul 18, 2014
Messages
1
Thread Author #1
hey this is my first post and i have recently re installed windows 7 bit i keep getting blue screens of death with the code of IRQL less or not equal. if anyone has a chance to look though them it would be amazing
 

Attachments

Solution
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa980608d220, 2, 1, fffff800028e6150}

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

Followup: MachineOwner
Hi,
all your dump files are the same Bugcheck as the above and errors which produce this type of Bugcheck range from faulty RAM...

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa980608d220, 2, 1, fffff800028e6150}

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

Followup: MachineOwner
Hi,
all your dump files are the same Bugcheck as the above and errors which produce this type of Bugcheck range from faulty RAM, faulty device drivers, incorrect Bios and faulty system software. Most of the dumps blamed the system kernel apart from two, one of which is above, which blamed memory corruption.
I see that your motherboard is this:
http://www.gigabyte.com/products/product-page.aspx?pid=4815#bios (ensure I have the correct motherboard version or revision too. Either 1.0 or 1.1. or 1.2 you'll find it written on the actual motherboard)
Your Bios is the latest version.
BiosVersion = F7
BiosReleaseDate = 07/13/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = H61M-D2H-USB3


Looks like your missing one or two drivers too. If you follow the link above you will find the driver section. Please update where necessary.

netr7364.sys Wed Jun 17 10:18:51 2009: Ralink RT2501/RT2573/T2601/RT2671 Wireless Adapter (might be different manufacturer) please update:
Link Removed

If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Post any new dump files.
 

Solution