Windows won't make minidumps on BSOD

[ferrari24]

Since December 29th my computer has been getting BSOD's about once every other day, and there aren't any minidumps created.

I've checked my settings and it is set to create minidumps (instead of full kernel dumps).

I'd sure like these to figure out what is causing these random crashes. I'll post the three dumps that I do have (it seems that the new BSOD's have the same problems as these though).

I know this isn't caused by faulty RAM because my other installation of Windows XP has never had a BSOD (hard to believe, but I use it about 1/2 as much as my other XP).

 

[Route44]

First minidump is 0x50 and it points to memory corruption.

Second minidump is 0xC2 BAD_POOL_CALLER
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

Under this one there was a long list of processes that could not load.

Third minidump is 0x3B and I had to search google for this one.

Cause: This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

Here are my suggestions:

1. Run MemTest on your RAM

2. Run chkdsk

3. Uninstall and reinstall your video card and drivers

4. I would also run a harddrive diagnostics

* There is a lot of conflicts with drivers and drivers/processes not loading.

* You may have to do a Windows repair.

 

[ferrari24]

Like I said, this hasn't happened on my x86 version of Windows, just the x64 version. I'm going to do a Windows repair, thanks.