BSoD no dump file created. Dump files are enabled

I've been having BSoD's for well over a year now, once or twice almost every day. I've tried multiple times to figure out whats wrong but... I dont have ANY dump files.

I've followed instructions on how to enable them but it still doesn't create a file. Im really hoping you all can help me out here.

The current settings are:
Page files on both hard drives enabled.
Set custom page size to 17000MB-20000MB
System managed size and no paging file boxes are unchecked
Write an event to system log box checked
Automatically restart unchecked
Debug information set to small memory dump/kernal. Both settings dont work
Overwrite existing file box is greyed out when debug is set to small memory. Checked when set to kernal
Small and kernal memory dump location set to C:\Windows\Minidump and C:\Windows\Memory.DMP I created these folders as they were not present

I got a SSD awhile back and use it for my windows. However i didnt reformat my other hard drive and windows is still installed on the old one however i boot from the SSD (maybe this is some how the problem)

Im using WhoCrashed from http://www.resplendence.com/main to force a BSoD when trying to creat a dump file.

There are NO files in either folder. Both on the SSD or old hard drive.

I've searched many forums now and found others with what seems to be the same problem but with no solutions. I would VERY much appreciate the help!
The BSoD's seem to mostly happen when playing games however they have happened when only using chrome
4 answers Last reply
More about bsod dump file created dump files enabled
  1. i would say bad memory stick...
    but 1st tell me what OS are you using
    to test memory open your pc case (when its off ofc) and remove the memory sticks 1 by 1 (ofc make sure to leave 1 each time) and also change their place.
    If you have only 1 memory stick remove it and clean the small part thats being inserted to the motherboard with pencil rubber then put it back in
    If this doesnt work change the primary drive from BIOS and see if the old drive also crashes you
  2. I think whocrashed does not force a bugcheck, it just attempts to read existing memory .dmp files.
    generally, to force a memory dump google: "how to force a memory dump using the keyboard"
    or look here: https://msdn.microsoft.com/en-us/library/ff545499(v=vs.85).aspx
  3. woops sorry, i have windows 7.
    I have cleaned the memory sticks but have not tried only running one.
    Whocrashed does have a force BSoD option.

    Im pretty sure that my no dump files is caused by how i installed windows when i got my SSD. I used a program that was "supposed" to transfer windows from old drive to the SSD without re-installing it. It didnt work... So i ended up just installing it on the SSD however i never removed windows from the old drive. Computer boots from the SSD now. But I've checked both drives minidump and memory.dmp folders and both are empty.

    I was told daemon tools and drivermax cause many BSoD's so i have uninstalled those and hoping that works. But even if it does it still doesnt solve my mystery of no dump files
  4. yep, it does. I guess it has just been a long time since I ran it.

    Bronm said:
    woops sorry, i have windows 7.
    I have cleaned the memory sticks but have not tried only running one.
    Whocrashed does have a force BSoD option.

    Im pretty sure that my no dump files is caused by how i installed windows when i got my SSD. I used a program that was "supposed" to transfer windows from old drive to the SSD without re-installing it. It didnt work... So i ended up just installing it on the SSD however i never removed windows from the old drive. Computer boots from the SSD now. But I've checked both drives minidump and memory.dmp folders and both are empty.

    I was told daemon tools and drivermax cause many BSoD's so i have uninstalled those and hoping that works. But even if it does it still doesnt solve my mystery of no dump files
Ask a new question

Read More

Blue Screen Hard Drives Systems