BSODing

Herox · 09 Oct 2009

Ok first time i bsod'd it was page fault in a non paged area. I havnt had this since and i did a ram test and nothing came up. Then i got BAD_POOL_HEADER. That could mean anything. Just 10 minutes ago I got IRQL_NOT_LESS_OR_EQUAL. Its getting to the point i wanna go back to XP. I love windows 7 and I love how well it works but i hate getting these random BSODs. It always seems to happen in relation to firefox, i swear. The IRQL happend when a youtube video finished. I really need help or ill have to go back to xp.

edit: in looking, it seems pidgin is known to cause IRQL and bad pool header in windows 7 professional and it could also in ultimate which is what I have. Im not sure if thats the problem but it was running every time i bsod

H2SO4 · 09 Oct 2009

If you upload minidumps, someone may be able to help.

Copy the contents of \Windows\Minidump to another location on your machine, zip them up, upload here (paperclip icon above to attach a file).

Herox · 09 Oct 2009

The site wouldnt give me the option. I can now though. I think the problem does relate to this messenger though. Ive got it running as winxp sp3 see if it helps anything.

Herox · 10 Oct 2009

well i guess no one could help me. I used ccleaner on my pc and surprise, it screwed up my pc. Time to lose my everything YAY.

H2SO4 · 10 Oct 2009

Herox said:

well i guess no one could help me. I used ccleaner on my pc and surprise, it screwed up my pc. Time to lose my everything YAY.

Patience is a virtue. Everyone here volunteers their time.

Surprisingly, only one of your minidumps shows evidence that the "registry cleaner" may have been involved, much as I harbour a strong background disdain for that type of "utility". Literally every one of these crashes is different, and only a few of them seem to directly point at an obvious course of action:

1) Update or remove this firewall. At least a couple of the crashes are attributable to it:

Image path: \??\C:\Windows\system32\drivers\EagleNT.sys
Timestamp: Fri Jun 05 17:49:25 2009 (4A28CE05)

2) Update the video driver - the video appears to be motherboard embedded, though I could be wrong:

Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
Timestamp: Wed Jun 17 04:28:17 2009 (4A37E441)

3) Perform a full CHKDSK /R on at least the system and boot partitions. One of the crashes was in the file system.

After that, monitor the situation. If crashes persist, upload more minidumps. Right now, there's no reason to think this is all a single issue. You've got to whittle them down one-at-a-time.