As I have posted before, since last summer, my client has been getting
random BSOD's, mostly pointing to memory corruption.

After eliminating everything else (memory, power supply, disk, swapping
memory between slots), a new motherboard (the oher was a ASRock ConRoe
1333-D667).

The morning after the new motherboard was fitted I got a BSOD
IRQL_NOT_LESS_OR_EQUAL, and yesterday DRIVER_IRQL_NOT_LESS_OR_EQUAL.

System specs

Intel 3.00GHz Celeron D Processor
250GB Hard drive
2GB memory
Gigabyte G31M-ES2L motherboard
BIOS: 14/8/2008
DVD-RW Optiarc drive
Intel G333/G331 Express Chipset Family (Display)
RealTek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC

(the date is wrong on the filename on the dump of the 17th)


+-------------------------------------------------------------------+
|Filename: BSOD analysis -200109.TXT |
|Download: http://www.vistax64.com/attachment.p...achmentid=9668 |
+-------------------------------------------------------------------+

--
tommy2k8

This is almost always a driver:
IRQL_NOT_LESS_OR_EQUAL
This bug check is issued if paged memory (or invalid memory) is accessed
when the IRQL is too high. The error that generates this bug check usually
occurs after the installation of a faulty device driver, system service, or
BIOS. If you encounter bug check 0xA while upgrading to a later version of
Windows, this error might be caused by a device driver, a system service, a
virus scanner, or a backup tool that is incompatible with the new version.

DRIVER_IRQL_NOT_LESS_OR_EQUAL
A driver tried to access an address that is pageable (or that is completely
invalid) while the IRQL was too high.
This bug check is usually caused by drivers that have used improper
addresses.
If the first parameter has the same value as the fourth parameter, and the
third parameter indicates an execute operation, this bug check was likely
caused by a driver that was trying to execute code when the code itself was
paged out. Possible causes for the page fault include the following:
The function was marked as pageable and was running at an elevated IRQL
(which includes obtaining a lock).
The function call was made to a function in another driver, and that
driver was unloaded.
The function was called by using a function pointer that was an invalid
pointer.





But here are a couple of items noticed in your write-up:
Current BIOS is revision F5, 11/6/2008 (You are two behind. Not recommended
unless you're having hardware problems which you are.)

http://www.gigabyte.com.tw/Support/M...ProductID=2889
This motherboard has dualBIOS. Not sure how that works, but if it means
there are actually two BIOS chips, are they setup the same?
Is Easy Energy Saver enabled? It needs to be the latest revision: ET6

http://www.gigabyte.com.tw/Support/M...ProductID=2889
In the BIOS, set Init Display to Onboard VGA instead of PCI (Default.)
Is the keyboard or mouse a USB device?
Is the BIOS set to enabled for the keyboard or mouse if a USB device?
Is the onboard LAN disabled in BIOS?
Is HPET Mode set correctly for the OS installed?
Disable any overclocking features.
Disable onboard audio to verify audio driver is not conflicting.
Make sure you have the motherboard drivers loaded for the OS installed:

http://www.gigabyte.com.tw/Support/M...ProductID=2889
I will assume you mean the Celeron D 3.06GHz with 533 FSB support.
Is the memory rated for 533, 667 or 800? Multiple sticks? All the same?

http://www.gigabyte.com.tw/FileList/...-g31m-es2l.pdf





"tommy2k8" wrote in message
...

As I have posted before, since last summer, my client has been getting
random BSOD's, mostly pointing to memory corruption.

After eliminating everything else (memory, power supply, disk, swapping
memory between slots), a new motherboard (the oher was a ASRock ConRoe
1333-D667).

The morning after the new motherboard was fitted I got a BSOD
IRQL_NOT_LESS_OR_EQUAL, and yesterday DRIVER_IRQL_NOT_LESS_OR_EQUAL.

System specs

Intel 3.00GHz Celeron D Processor
250GB Hard drive
2GB memory
Gigabyte G31M-ES2L motherboard
BIOS: 14/8/2008
DVD-RW Optiarc drive
Intel G333/G331 Express Chipset Family (Display)
RealTek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC

(the date is wrong on the filename on the dump of the 17th)


+-------------------------------------------------------------------+
|Filename: BSOD analysis -200109.TXT |
|Download: http://www.vistax64.com/attachment.p...achmentid=9668 |
+-------------------------------------------------------------------+

--
tommy2k8