No dump file after BSoD. Dump files ARE enabled

Bronm · 09 Feb 2015

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 Resplendence Software - Advanced System Tools and Developer Components 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

Bronm · 09 Feb 2015

Wrote stuff that was wrong. Ignore this reply

Golden · 10 Feb 2015

Run this anyway - it may help to determine why you aren't getting .dmp files.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

Bronm · 10 Feb 2015

Appreciate the help! This is driving me crazy

Golden · 10 Feb 2015

Code:

Drive	C:
Description	Local Fixed Disk
Compressed	No
File System	NTFS
Size	238.38 GB (255,953,555,456 bytes)
Free Space	94.75 GB (101,739,704,320 bytes)
Volume Name	
Volume Serial Number	C622FD32
	
Drive	D:
Description	Local Fixed Disk
Compressed	No
File System	NTFS
Size	100.00 MB (104,853,504 bytes)
Free Space	70.36 MB (73,781,248 bytes)
Volume Name	System Reserved
Volume Serial Number	20211C74
	
Drive	E:
Description	Local Fixed Disk
Compressed	No
File System	NTFS
Size	100.00 MB (104,853,504 bytes)
Free Space	70.34 MB (73,760,768 bytes)
Volume Name	System Reserved
Volume Serial Number	20211C74
	
Drive	F:
Description	Local Fixed Disk
Compressed	No
File System	NTFS
Size	931.41 GB (1,000,097,181,696 bytes)
Free Space	86.01 GB (92,350,939,136 bytes)
Volume Name	
Volume Serial Number	C622FD32

How many operating systems are installed to this system? Do you recall the bugcheck code that flashes up when the system BSOD's?

Bronm · 10 Feb 2015

I only have windows installed. However when i got my SSD i didnt remove windows from the old drive. At one point i tried using a program(Cant remember the name) that was suppose to "transfer" windows from the old drive to new without re-installing. It never worked but it may have screwed something up.

I dont have the bugcheck code on me, but im sure another BSoD will happen again at some point today. Ill make a point of writing it down

Golden · 10 Feb 2015

OK. I think in installing the way you did causes Windows to get confused about where to write the .dmp files.

However, I think I can take an educated guess at what is causing the BSOD's based on experience here.

Code:

Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public
Start Menu\Programs\DriverMax	Public:Start Menu\Programs\DriverMax	Public

Both of the above are well-known causes of BSOD's - I recommend uninstalling them.

If you still get BSOD's afterwards, please physically disconnect the "old Windows 7 disk", and reboot. Then do this, and it should create .dmp files in C:\Windows\Minidump:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

Bronm · 10 Feb 2015

Wow, thanks so much. Ill try this as soon as i get home. I know drivermax is a recently installed thing but daemons ive had for a long time.

Golden · 10 Feb 2015

Of all the 3rd party software, Daemon Tools causes the most BSOD's -- often with a 0xD1 bugcheck, which is why I asked if you recall what it was.

Remove them, then lets see what we get. In fact, uninstall them then run Driver Verifier straightaway if you like -- lets see if we can force a BSOD.

Bronm · 11 Feb 2015

Well i uninstalled drivermax and daemons, still got a BSoD. Will be removing old hard drive and running driver verifier shortly