How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
I don't know why it crashes, but every time I start up metal gear solid 5 or state of decay it crashes 5 to 10 minutes in, just started doing this 3 days ago.
Windows 10 BSoD random crashes, critical process died, unknown store exception
- Thread starter How Not To Game
- Start date
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {3f, 155d, 14657fbc, ace9ee36}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
*** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.sorry it's taken me a while to answer.
A number of the dump files point to memory management just like the one posted above. This can mean that either the RAM is failing The dump file finally goes on to say that at least one page of the pagefile is corrupted.
First try rebuilding your Pagefile. This is a simple process
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for a button under virtual memory called 'change'. This will lead you to the dialogue box where you can change the size of the pagefile or even turn it off.
You need to uncheck everything and then make sure 'no paging file' is checked and then reboot.
To start the pagefile up again use the recommended amount and pop the same figure in each of the boxes . Click apply and hopefully you will have a nice clean Pagefile.
Please run these scans:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
If the bsod continues then you'll need to test your RAM. Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool
Post any new dump files.
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
i got new RAM 16 GB and still crashes
Hi,
sorry to hear your issue's were not resolved.
Unfortunately I have recently been having my own issues and am currently running on a machine i cobbled together out of old parts.
This has meant i don't have full access to my debugging data although it appears that even if I did it still wouldn't help the following issue.
Each dump file is coming back with incorrect symbols ( these are used to denote drivers and apps ). Here's one of yours:
As you can see it looks a bit of a mess and I know from various messages from other debuggers that they are seeing the same thing.
The last time something like this occurred it was down to Microsoft needing to update their servers. I'm going to contact a few colleagues and see if they know any more about this latest issue.
The above Bugcheck EF has a few tips on it's developer page:
So does the crash only happen when you been gaming 5-10 minutes?
Did you change the pagefile as suggested?
sorry to hear your issue's were not resolved.
Unfortunately I have recently been having my own issues and am currently running on a machine i cobbled together out of old parts.
This has meant i don't have full access to my debugging data although it appears that even if I did it still wouldn't help the following issue.
Each dump file is coming back with incorrect symbols ( these are used to denote drivers and apps ). Here's one of yours:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffff9501eb36b080, 0, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
ETW minidump data unavailable
"><Unable to get nt!KiCurrentEtwBufferOffset><Unable to get nt!KiCurrentEtwBufferBase>*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KTHREAD ***
*** ***
*************************************************************************
Unable to open image file: C:\Windows\symbol_cache\win32kbase.sys\5932781C180000\win32kbase.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\win32kbase.sys\5932781C180000\win32kbase.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\win32kbase.sys\5932781C180000\win32kbase.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\win32kbase.sys\5932781C180000\win32kbase.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\crashdmp.sys\5801A69319000\crashdmp.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\crashdmp.sys\5801A69319000\crashdmp.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\crashdmp.sys\5801A69319000\crashdmp.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\crashdmp.sys\5801A69319000\crashdmp.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\ks.sys\58BA5E8E68000\ks.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\ks.sys\58BA5E8E68000\ks.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\ks.sys\58BA5E8E68000\ks.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\ks.sys\58BA5E8E68000\ks.sys
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\hal.dll\57DAC91A75000\hal.dll
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\hal.dll\57DAC91A75000\hal.dll
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\hal.dll\57DAC91A75000\hal.dll
The system cannot find the path specified.
Unable to open image file: C:\Windows\symbol_cache\hal.dll\57DAC91A75000\hal.dll
The system cannot find the path specified.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!593278B1818000 )
Followup: MachineOwnerAs you can see it looks a bit of a mess and I know from various messages from other debuggers that they are seeing the same thing.
The last time something like this occurred it was down to Microsoft needing to update their servers. I'm going to contact a few colleagues and see if they know any more about this latest issue.
The above Bugcheck EF has a few tips on it's developer page:
So does the crash only happen when you been gaming 5-10 minutes?
Did you change the pagefile as suggested?
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
Yes it only happens 5 to 10 minutes into a game and yes i did my pagegile twice, i also dis the scan sfc /scannow but is said nothing was wrong.
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
will do
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
sorry I haven't replied in a while I have been on vacation I now have a new processor (FX-8350) and it still crashes. I have no idea what to do at this point it doesn't even blue screen it just freezes and restarts my pc.
Last edited:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffff9708351e8800, 0, 0, 0}
ETW minidump data unavailable
Probably caused by : memory_corruption
Followup: memory_corruption
---------Hmm.. Well I was kinda thinking it was probably your gpu at fault but we'll see.
What i was going to go on to suggest is that you try down clocking your graphics card by a few megahertz.
MSI overclocking app will help you in this process and do remember to down clock not over clock..
Personally I'd try dropping the core by 1000MHz at first and try that for a while.
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
I didnt know if you ment 100Mhz or 1000 so i put it down 100Mhz and it crashed right as i started a game
Last edited:
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
Also if i took it into a local pc shop eould ot be useful or would i waste my time?
Well they would have more resources to test so it might be worth your while.
They will be able to test your gpu in a different machine ect .
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
Alright i will take it in tomorrow
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
I do aswell
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
I found out i needed a new powersupply because i only had a stock 500W so i bought a Corsair 80+ Platinum 750W
Well that's great news, thank you for updating.
So the 500W psu you had was just a generic brand then? It does pay to go that little bit extra when buying the PSU. Many users will try and save money on cheaper models which is the worst thing one can do. One should always buy from a well known brand as well reading up on reviews first and taking into account the needed 'ampage'
Graphic cards need a certain amount of amps to run despite what the wattage may be and one should always make sure this criteria is either matched or surpassed before buying.
So the 500W psu you had was just a generic brand then? It does pay to go that little bit extra when buying the PSU. Many users will try and save money on cheaper models which is the worst thing one can do. One should always buy from a well known brand as well reading up on reviews first and taking into account the needed 'ampage'
Graphic cards need a certain amount of amps to run despite what the wattage may be and one should always make sure this criteria is either matched or surpassed before buying.
How Not To Game
Honorable Member
- Joined
- Jun 21, 2017
Well idk what brand it was all i know is it was my stock psu necause befpr a added all of my new stuff the pc was a prebuilt
Sometimes there isn't even a brand name printed on but whatever at least you got it sorted out which is great.
Similar threads
