BSoD doesn't create a crash dump?

[CapinWinky]

For the past month, my computer has been experiencing frequent BSoD crashes, something it has not done with any frequency since it's assembly 5 years ago. Naturally, I want to fix the issue, so I got bluescreenview and promptly discovered that no crash dumps were being saved.

I have 2GB RAM and my virtual memory has my page file on my C: with a custom size of 3069 to 6138 (changed from all automatically managed in an effort to fix my missing crash dumps). It is presently at the minimum size of 3069. I also have an auto-managed page file on my H:. I have alternately disabled and enable both of these page files with no luck.

C:\ is a three disk RAID5 on SATA with 400GB+ free space. H:\ is a single SATA disk with 250GB+ free space.

The system failure settings are set to small memory dump to the directory %SystemRoot%\Minidump. I changed the setting from a kernel memory dump since those don't work with bluescreenview and did find that my system had saved a kernel crash dump from a few years ago, so at some point I didn't have this missing crash dump issue.

The BSoD itself displays:
Collecting data for crash dump...
Initializing disk for crash dump...

And nothing else, no failure/success message, no progress indicator, nothing.
I attached a picture of it, I unfortunately cut off a comma and the 0x that appear to the right of the digit '8' in that long string of numbers.

EDIT:
Crash Dump is one of the listings for C:\ in disk management, in case that is a clue as to where the problem is.

 

[zigzag3143]

For the past month, my computer has been experiencing frequent BSoD crashes, something it has not done with any frequency since it's assembly 5 years ago. Naturally, I want to fix the issue, so I got bluescreenview and promptly discovered that no crash dumps were being saved.

I have 2GB RAM and my virtual memory has my page file on my C: with a custom size of 3069 to 6138 (changed from all automatically managed in an effort to fix my missing crash dumps). It is presently at the minimum size of 3069. I also have an auto-managed page file on my H:. I have alternately disabled and enable both of these page files with no luck.

C:\ is a three disk RAID5 on SATA with 400GB+ free space. H:\ is a single SATA disk with 250GB+ free space.

The system failure settings are set to small memory dump to the directory %SystemRoot%\Minidump. I changed the setting from a kernel memory dump since those don't work with bluescreenview and did find that my system had saved a kernel crash dump from a few years ago, so at some point I didn't have this missing crash dump issue.

The BSoD itself displays:
Collecting data for crash dump...
Initializing disk for crash dump...

And nothing else, no failure/success message, no progress indicator, nothing.
I attached a picture of it, I unfortunately cut off a comma and the 0x that appear to the right of the digit '8' in that long string of numbers.

EDIT:
Crash Dump is one of the listings for C:\ in disk management, in case that is a clue as to where the problem is.

Please ensure logging is enabled.




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[CapinWinky]

I don't need a minidump analyzed, I need to fix the problem of not generating minidumps.

To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

I've done all of this.

The only thing left is to assume the BSoD is caused by my raid control driver and thus blocks the creation of a dump file. Unfortunately, installing a newer driver for my SATA and RAID did not fix the BSoD's nor the missing minidump problem.

 

[Maguscreed]

You could upload the perfmon report and do all the other bsod steps in the meantime.
Probably won't tell us enough to diagnose but it's something.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[CapinWinky]

I removed the proprietary sataraid and sataide drivers, used driver sweeper and let windows install some generic drivers automatically. From this, I regained the ability to write mini-dumps. I have an nVidia motherboard (680i SLI from evga) and never had issues until SP1 came out. The new nForce drivers just made things worse. I'm going to try a repair install of windows and see what I can salvage.