New
#11
Right, I've put in my system specs and configured it to make small dumps, not kernal dumps, I'll upload them as soon as possible
Right, I've put in my system specs and configured it to make small dumps, not kernal dumps, I'll upload them as soon as possible
Good, that will help. Make sure you have a C:/windows/Minidump folder. If there is not one, create a folder called Minidump in C:/windows.
I'm not getting any crash dumps.
I don't know what went wrong. Here's a screenshot of my settings, I don't think I've missed anything. https://i.imgur.com/zyPV0WB.png
Ok, done that. Hopefully it will work next time it crashes.
Also, open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
So it's still not giving me any crash dumps, which is annoying. I've tried the second option fix and that didn't work either.
But on the plus side, after running the command prompt, it said there were no integrity violations on the second time through. Hopefully, that's done it.
Yes, sadly so.
So far, only ones displaying an IRQL_NOT_LESS_OR_EQUAL error.
And the second option didn't work on the crash dumps.