It is probably time you updated your CN profile as the system you are having a problem with is clearly not a Pii running win95,98 or ME.

It appears you have a multiboot system with XP, Vista and Win7 installed however this may not be the case. You just might have several harddrives that you swap out to use different op system Since your problem only exhibits in Vista & 7, but not in XP it is unlikely to be a hardware issue. IRQ NOT LESS OR EQUAL stop errors are usually related to incompatible drivers so have you made any hardware or software changes immediately prior to the manifestation of the problem? Please also provide a full description of the system including the multiboot setup.

If you're not having problems with WinXP on the same box, I'd assume it's a driver issue. If you still have it, I could throw your minidump into the ol' debugger and see what driver it says caused the crash.

I don't know if it is the sound card at fault because I believe that the system does this due to motherboard compatibility issues and it used to do the same thing with a different sound card in it as well.

Razor, how do I do that? I did change the crash option to minidump and used the minidump reader to obtain the pictures I linked on here.

My screename used to be superjnf, but eversince I could connect my facebook, I am going to start using this.

Could not find the E:\Mini120412-01.dmp Dump File, Win32 error 0n1392
The file or directory is corrupted and unreadable.

Apparently not with that minidump. Corrupted dumps are rare. Check for updated SATA / RAID / whatever interface your system uses. If you have the most up-to-date drivers, it's time to do some serious hardware diagnostics.

Yep, it's corrupt. I can't imagine that dump reader you used does much validation at all, and it's just silently eating errors. You'll notice most of the fields are left blank, and the information it does grab is at the very beginning of the dump file.

Okay I think I am planning to put Windows XP back on this system, but before I do, I went into BIOS and changed one setting.

I ENABLED the "Limit CPUID MaxVal" feature in the BIOS and then booted into Vista and then the BSOD does not happen anymore like it used to. However, then Windows gave me information about the blue screens:

I am not sure what is going on but when I went back to BIOS and disabled the "Limit CPUID MaxVal", the blue screens are not happening, but I rebooted and enabled it back. What does "Limit CPUID MaxVal" mean?

Intel Virtualization Technology is enabled as well, but I left that alone since I doubt that is the cause.

The Blue Screens are random, they are either PFL, or IRQ, and I remember the next one was win32k.sys, so I don't know what is going on.

My screename used to be superjnf, but eversince I could connect my facebook, I am going to start using this.

I looked at my settings and it is telling me that I have only 1.8 GHz instead of the full 2.4 GHz and I don't see a speed difference either. Is CPUID MaxVal limiting my CPU Speed? I have the feeling that my CPU is overheating since sometimes the computer freezes unexpectedly. This is a very small case since it is a Shuttle Glamour XPC. I am using the ICE Stock Cooling which came with the case.

My screename used to be superjnf, but eversince I could connect my facebook, I am going to start using this.

EDIT: Out of all of your dumps, only Mini120712-02.dmp would load, and its not in a happy state. According to the dump, it was caused by ExQueryPoolUsage. Either you have faulty software in the kernel, or you have faulty hardware. Given what you've told me and what I've seen in the crash dumps, the safe bet is faulty RAM.

riider:I'm not downloading anything.Relax, they're just a collection of minidumps.

The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this
site. Computing.Net and Purch hereby disclaim all responsibility
and liability for the content of Computing.Net and its accuracy.