(edited by TylerWolff.7186)
Game crashing and BSOD's make me sad.
Please post the .dmp file from the BSOD’s.
Please post the .dmp file from the BSOD’s.
How would I do that exactly?
The log will be in
%systemroot%\Minidump
which should be C:\windows\Minidump, you should be able to put %systemroot%\Minidump
into the windows search bar in the start menu and hit enter and it should open the folder, then upload the newest dmp file.
The log will be in
which should be C:\windows\Minidump, you should be able to put%systemroot%\Minidump
into the windows search bar in the start menu and hit enter and it should open the folder, then upload the newest dmp file.%systemroot%\Minidump
It shows up when I search it from the start menu, but not when I search it from the “browse” button when I try to upload it.
That is because you need to go to C:\windows\Minidump, the other path is not so much a path as a environment variable, which value is the location of the system directory, I list this one also because sometimes the system directory might be on another named drive, default is C, but that is not always used, so giving the variable it will always point to the system directory no matter its install location.
In either case, use the variable to get to the folder and copy the dmp file to the desktop to make it easier to find, or when in the upload window follow the path to C:\windows\Minidump
That is because you need to go to C:\windows\Minidump, the other path is not so much a path as a environment variable, which value is the location of the system directory, I list this one also because sometimes the system directory might be on another named drive, default is C, but that is not always used, so giving the variable it will always point to the system directory no matter its install location.
In either case, use the variable to get to the folder and copy the dmp file to the desktop to make it easier to find, or when in the upload window follow the path to C:\windows\Minidump
Says I can’t upload dmp files
But if it helps you at all I looked at blue screen report and it said the crash was caused by “driver: ntoskrnl.exe”