Daily BSODs, System not creating MEMORY.dmp

[gwin003]

I have been having problems with my desktop recently. I am crashing a few times a day and have been trying to write down some of the stop messages or .sys files that are causing the BS's.

Some of the .sys files causing the crash are 'win32k.sys' and 'usbstor.sys'. I can get more info later when I get home from work.

I would post the system dump file, but my computer is not creating one. I checked the options in Startup and Recovery, and the option to 'Write an event to the system log' is checked, and 'Write debugging information' is set to 'Kernel memory dump'. I read somewhere that I should try changing that to 'Complete memory dump', but the option is not available. Also the dump file location is set to '%SystemRoot%\MEMORY.DMP'.

Any thought on how to get the memory dump file? Thank!

EDIT: Just read the BSOD Posting Instructions. I will follow them tonight or tomorrow and update. This can be deleted if necessary.

 

[Maguscreed]

we are more interested in minidumps here as they are easier to attach to a post.
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.

Making those changes will hopefully ensure a minidump is created.
It will be in c:\windows\minidump

 

[gwin003]

Thanks for the quick reply. I will try to get to this today or tomorrow. It seems there are different causes for the crashing. Is it appropriate to post several minidump files if they appear to be different?

 

[Maguscreed]

I can't say anything on that until I see the first one.
Sometimes the driver dump alone is enough to pick apart a seemingly random problem.
Other times it involves working your way through several fixes before it's actually resolved.
There is just really no way to know without seeing the dump.
Especially when win32k.sys is involved.