Irql bsod

Hi everyone,

I've been browsing around on the forum lately to see if anyone has been having similar issues to the one on my computer, but what I found more or less amounted to "there are many many reasons that this BSOD could occur."

I'm not having too much luck tracking down the ones posted in the forums so far, so I'm uploading the last three minidumps my system has made in hopes someone more experienced than I am will be able to find the error.

This computer's basic specs are as follows:

Gateway 817GM Media Center
OEM OS: Windows XP SP2 Media Center
Current OS: Windows 7 Professional 32-bit
Processor: Intel Pentium 4 530 @ 3.00GHz w/Hyper-Threading
RAM: 1.50GB DDR1 - 4 Banks (Paired White-Black-White-Black) : 1024 0 0 512

I'm aware that DDR1 wants to be either in a matched pair or by itself-- my original configuration was 1024-256-256-512. Thinking this might be the cause of the frequent IRQL issues, I removed both 256MB chips.

For reference, I have tested each of these chips individually using the built-in Windows 7 memory diagnostic with a standard two-pass test.

Please do not link me to memtest86+. Linux variants are my favorite operating systems, but currently I am unable to boot into a LiveUSB or LiveCD type environment due to problems with my monitor resolution.

There is very little installed on this computer at present-- I have made a clean install in hopes that initial instabilities might be responsible for my current problems. This does not seem to be the case, however.

Thanks in advance for any help!

EDIT:

I remembered one item -- this may be responsible, but I have not been able to test to my satisfaction whether or not this is a source of problems. There is one driver enabled on this system originally designed for Windows XP, that being the Realtek HD audio driver that I have yet to find a Windows 7 replacement for. Drivers seem to be a common problem for BSODs, so can someone look into this?

GunboatDebater said:

Hi everyone,

I've been browsing around on the forum lately to see if anyone has been having similar issues to the one on my computer, but what I found more or less amounted to "there are many many reasons that this BSOD could occur."

I'm not having too much luck tracking down the ones posted in the forums so far, so I'm uploading the last three minidumps my system has made in hopes someone more experienced than I am will be able to find the error.

This computer's basic specs are as follows:

Gateway 817GM Media Center
OEM OS: Windows XP SP2 Media Center
Current OS: Windows 7 Professional 32-bit
Processor: Intel Pentium 4 530 @ 3.00GHz w/Hyper-Threading
RAM: 1.50GB DDR1 - 4 Banks (Paired White-Black-White-Black) : 1024 0 0 512

I'm aware that DDR1 wants to be either in a matched pair or by itself-- my original configuration was 1024-256-256-512. Thinking this might be the cause of the frequent IRQL issues, I removed both 256MB chips.

For reference, I have tested each of these chips individually using the built-in Windows 7 memory diagnostic with a standard two-pass test.

Please do not link me to memtest86+. Linux variants are my favorite operating systems, but currently I am unable to boot into a LiveUSB or LiveCD type environment due to problems with my monitor resolution.

There is very little installed on this computer at present-- I have made a clean install in hopes that initial instabilities might be responsible for my current problems. This does not seem to be the case, however.

Thanks in advance for any help!

EDIT:

I remembered one item -- this may be responsible, but I have not been able to test to my satisfaction whether or not this is a source of problems. There is one driver enabled on this system originally designed for Windows XP, that being the Realtek HD audio driver that I have yet to find a Windows 7 replacement for. Drivers seem to be a common problem for BSODs, so can someone look into this?

Memory corruption (probably caused by a driver)

You cant use windows diagnostics because it doesnt stress the memory enough and it is within the windows environment.

If you dont/cant run memtest I would at least run driver verifier to try and determine the driver.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

First off, thanks for the fast response!

Memory corruption (probably caused by a driver)

You cant use windows diagnostics because it doesnt stress the memory enough and it is within the windows environment.

If you dont/cant run memtest I would at least run driver verifier to try and determine the driver.

Really? I wasn't using the memory tester within the Windows environment, but rather using the pre-boot utility accessible by the F8 hotkey opening the bootloader menu and choosing memory diagnostics. Given the lengths of the one thorough test I buckled down to wait out, it does seem like it's doing a fair amount of work.

I'll certainly try the verifier though. Most of the drivers running are generic with the exception of audio. Many thanks.

Hm. I tried simply disabling the audio driver, and everything went pretty well for awhile. Uninstalling and searching for another one at present, but IRLQ is turning again, along with some Special Pool problems. More minidumps attached, help appreciated!

GunboatDebater said:

Hm. I tried simply disabling the audio driver, and everything went pretty well for awhile. Uninstalling and searching for another one at present, but IRLQ is turning again, along with some Special Pool problems. More minidumps attached, help appreciated!

Again memory corruption. Memtest and verifier needed.