Hi Ntx, any chance you could post at least 2 of your latest logs? These logs are not always accurate when it comes to certain hardware issues, so it's important to have a few to compare with for accuracy.

Well, the file attached was the only BSOD dump file I got even after so many BSODs. I just can't get any more BSOD dump files. I even tried to enable hidden files but to no avail. My settings are the same as madmonkey's. Attached is the picture of my settings and the minidumps folder.

Ntx710I

Hi NTX, those settings look ok to me.

Since we have nothing really to go on at the point, we could always look around for common causes to these stop errors, but "IRQL_NOT_LESS_OR_EQUAL" is a common stop error because it can cover pretty much an infinate number of possible issues, both hardware and software. For that reason, it may involve a more drastic approach to diagnosing the problem, if common causes are ruled out. If you receive anything other than this message, please be sure to note them down as it may help to narrow the problem down further.

Also, take a look in your Event Viewer for any errors which appear here (Start, Control Panel > Administrative Tools > Event Viewer).

If the settings are correct, but no log files are being produced, then this may suggest that the system was not able to complete the dump and/or the disk itself was not accessible at the time of the crash.

In the meantime, you might want to check for memory problems too, which is the most common cause of this particular error, by running memtest86.

Will do the memtest after I reached home. Anyway, the event viewer is quite complicated. Can you guide me to the appropriate source?

Thanks in advance.

Just click on "Windows Logs" category and under there you'll see "Application" and "System", as well as a few others, but those two were particularly interested in.

When you click on Application for example, scroll down the list. You'll see a lot of "Information" events, but also "Warnings" and "Errors" possibly dotted here and there. When you click on an Error, the information about the error will appear below the list. The Source, Event ID and description are the most important.

In System, there are loads of errors. All, except a select few, are

Source: atapi and the event ID:11
Description:The driver detected a controller error on \Device\Ide\IdePort0.


In Application, there are only a few errors. I caught one of them to be

Source:EventSystem and the event ID:4609
Description:The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043c from line 45 of d:\longhorn\com\complus\src\events\tier1\eventsyst emobj.cpp. Please contact Microsoft Product Support Services to report this error.

Oh dear, that would certainly explain why no log files are being produced.

Can you give me some history regarding this PC. Is it a custom built PC, or do you have a make and model? Has there been any hardware changes since you purchased it, in terms of hard drives and CD-ROM's? Is it still under warranty?