Windows 10: Several Random BSODs over Last 2 Days - Unexpected Store Exception

Hi all,

My ~5 year old laptop has started to play up with 4-5 BSODs over the last couple of days. These seem to happen at random, once even when the laptop was completely unattended. Dump files are never generated and the system always reboots to a black screen with no mouse pointer (I once left this for ~15 minutes without response). After hard powering off (i.e. holding down the power button), the laptop becomes usable again. The bugcheck is Unexpected Store Exception, but I cannot get muh else out because the dumps always fail. The system generally becomes unresponsive for several seconds before the BSOD appears.

I have run a hard disk check and a system file check, both of which gave no errors. I have had previous problems with BSODs (~6 months ago, even one orange screen of death?) which seemed to resolve when I uninstalled Avast Free Antivirus. If it is caused by a program, my primary suspect is GoG galaxy which I believe finished installing an update the day before the blue screens started occurring, which I am going to uninstall now. I have also changed a setting to try and get it to write small memory dumps, rather than the full ones.

:)

 

Several BSOD's over the last days. Help?

Update the Nvidia graphics driver to version 376.33:

Download NVIDIA, GeForce, Quadro, and Tesla Drivers



Please restart your computer and allow 20 minutes for the system to run before uploading information required to help me investigate your problem. When examining Event Viewer log files many, not all, problems show in the period immediately after
the computer has been booted.



Please upload to your OneDrive and share with everyone a copy of your
System log file from your Event Viewer and post a link here. Please remove any earlier copies of the logs from your OneDrive.



To access the System log select the keyboard shortcut Win+R, type
eventvwr.msc and press the ENTER key. From the list in the left side of the window select Windows Logs and System. Place the cursor on System, select Action from the Menu and
Save All Events as (the default evtx file type) and give the file a name. Do not provide filtered files.
Do not place the cursor in the list of reports before selecting Action from the menu. Do
not clear logs whilst you have a continuing problem.



For help with OneDrive see paragraph 9.3:

gerrys template

 

Several BSOD's over the last days. Help?

What is your computer make and model? If not a branded computer what is your motherboard make and model?



Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please, HTML files are less easy
to work with.

DriverView: Loaded Windows Drivers List

 

Hi BinaryPill,

Welcome to Ten Forums BSOD forum.

There were no BSOD mini dump files collected in the log files.
The files reported the following bugchecks: WHEA 0x124, 7E, 9F.

For all tests /steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.
Share OneDrive files and folders - Office Support
Upload photos and files to OneDrive - OneDrive
Share OneDrive files and folders - Office Support
Upload photos and files to OneDrive - OneDrive


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) Sometimes there are problems in the bios that produce bsod.
The BIOS: BIOS Version/Date Insyde F.11, 23/07/2015
7) Please check to see if this is the most up to date version.

8) Open the website for the computer manufacturer > enter the product or serial number > select the operating system > view the drivers and post a URL or hyperlink into the thread.

9) Create a brand new restore point.

10) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

11) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

12) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 8 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials

13) Download and install HD Tune:
HD Tune website
14) Post images into the thread for the test results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

15) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

16) Open device manager > click view > show hidden devices > expand all rows > look for any row that displays a an icon that is a yellow triangle with a black exclamation mark or an unknown device > post an image into the thread


Code: 25/01/2018 2:51 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff8016752acac P4: ffffd48e4adb6798 P5: ffffd48e4adb5fe0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\012618-99812-01.dmp \\?\C:\WINDOWS\TEMP\WER-111953-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER900.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA78.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_2c656a802a24cf577d167665486f82a99656cc5_00000000_cab_037d0d75 Analysis symbol: Rechecking for solution: 0 Report Id: 03540798-5dca-4918-9aec-ba2865cd0c97 Report Status: 4 Hashed bucket:8/01/2018 10:34 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 124 P2: 0 P3: ffff8583c9721028 P4: be000000 P5: 100110b P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010818-63562-01.dmp \\?\C:\WINDOWS\TEMP\WER-892203-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER150B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER151C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER153C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_5d13bf1b80fa5eaafded455bf161cea6914873_00000000_cab_03461549 Analysis symbol: Rechecking for solution: 0 Report Id: 3f32c8de-74d1-4acf-84c3-c01145e44d47 Report Status: 4 Hashed bucket: 12/01/2018 11:12 PM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 3 P3: ffffd90dfa88a060 P4: fffffb034a8298f0 P5: ffffd90dfa459c10 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\011318-95078-01.dmp \\?\C:\WINDOWS\TEMP\WER-1841000-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B2C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D3F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D8E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_f9e193157909b14164aad9fc0642126675e6029_00000000_cab_03251e39 Analysis symbol: Rechecking for solution: 0 Report Id: 30005337-d852-4744-895e-28e494d527e9 Report Status: 4 Hashed bucket:[/quote] Code: 8/01/2018 10:35 AM Windows Error Reporting Fault bucket 0x124_GenuineIntel_PROCESSOR_CACHE, type 0 Event Name: BlueScreen Response: Not available Cab Id: 9a2dd2dc-b0bb-4e11-9cc3-b600aab024a9 Problem signature: P1: 124 P2: 0 P3: ffff8583c9721028 P4: be000000 P5: 100110b P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\010818-63562-01.dmp \\?\C:\WINDOWS\TEMP\WER-892203-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER150B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER151C.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER153C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_5d13bf1b80fa5eaafded455bf161cea6914873_00000000_cab_247e7e63 Analysis symbol: Rechecking for solution: 0 Report Id: 3f32c8de-74d1-4acf-84c3-c01145e44d47 Report Status: 268435456 Hashed bucket:12/01/2018 11:13 PM Windows Error Reporting Fault bucket 0x9F_3_SETPOWER_IMAGE_rtwlane.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 7002243e-1339-4ae2-87d5-c83c62a0035a Problem signature: P1: 9f P2: 3 P3: ffffd90dfa88a060 P4: fffffb034a8298f0 P5: ffffd90dfa459c10 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\011318-95078-01.dmp \\?\C:\WINDOWS\TEMP\WER-1841000-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B2C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D3F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D8E.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_f9e193157909b14164aad9fc0642126675e6029_00000000_cab_10a1b51a Analysis symbol: Rechecking for solution: 0 Report Id: 30005337-d852-4744-895e-28e494d527e9 Report Status: 268435456 Hashed bucket:[/quote] Code: 26/01/2018 12:38 AM Windows Error Reporting Fault bucket AV_aswHdsKe!unknown_function, type 0 Event Name: BlueScreen Response: Not available Cab Id: 735c8350-86b9-4f53-ac0c-b2804c3db082 Problem signature: P1: 1000007e P2: ffffffffc0000005 P3: fffff8016752acac P4: ffffd48e4adb6798 P5: ffffd48e4adb5fe0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\012618-99812-01.dmp \\?\C:\WINDOWS\TEMP\WER-111953-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER900.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA78.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_2c656a802a24cf577d167665486f82a99656cc5_00000000_cab_1b0e4a89 Analysis symbol: Rechecking for solution: 0 Report Id: 03540798-5dca-4918-9aec-ba2865cd0c97 Report Status: 268435456 Hashed bucket:8/01/2018 10:35 AM Windows Error Reporting Fault bucket LKD_0x1A1_WIN32K_CALLOUT_WATCHDOG_nt!KiSwapContext, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: d7f77da3-1e96-4ccb-a779-e4389b902627 Problem signature: P1: 1a1 P2: ffffb58d235ec700 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20171214-1909.dmp \\?\C:\WINDOWS\TEMP\WER-892203-0.sysdata.xml \\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20171214-1909.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A6.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER914.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER944.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_33a22df78f31b8e6f689cf32261981d958922e_00000000_cab_247e48bd Analysis symbol: Rechecking for solution: 0 Report Id: ed813288-b367-4dc2-bb22-961acadddd2d Report Status: 268435456 Hashed bucket:[/quote]

 

Input from command prompt (I'll keep these coming):

Code: C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management toolVersion: 10.0.16299.15 Image Version: 10.0.16299.309 [==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully. C:\WINDOWS\system32>chkdsk /scan The type of the file system is NTFS. Volume label is Windows. Stage 1: Examining basic file system structure ... 1918720 file records processed. File verification completed. 23289 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 39346 reparse records processed. 2252544 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 39346 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 166913 data files processed .CHKDSK is verifying Usn Journal... 38615640 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 953599248 KB total disk space. 858425408 KB in 1523098 files. 791864 KB in 166914 indexes. 0 KB in bad sectors. 2064056 KB in use by the system. 65536 KB occupied by the log file. 92317920 KB available on disk. 4096 bytes in each allocation unit. 238399812 total allocation units on disk. 23079480 allocation units available on disk. C:\WINDOWS\system32>[/quote] By the way, though this comment was clearly automatically generated, I'm not sure whether the bugchecks listed will be useful because they're a little older.

 

BSOD dump files are needed for debugging.
Steps 10 and 11 will display information about them.
Then some modifications may be made as the logs displayed problems with the dumps:
Code: Event[18633]: Log Name: System Source: volmgr Date: 2018-03-31T15:20:31.539 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-EEQBT0R Description: Dump file creation failed due to error during dump creation.[/quote]

 

Some other things:

The latest BIOS could not be found on HPs website. Driver list could not be found either. Link: https://support.hp.com/au-en/drivers...58?sku=N8L44PA

CCleaner was not installed when I was doing this. I've installed it now, but I figure you were looking for settings, which don't matter because it hasn't been running.

Virtual Memory and Recovery settings attached. Note that the dump file size was changed recently (from full) because dumps were not saving.

Begining Memtest shortly.

 

1) Under startup and recovery system failure
a) uncheck: Automatically restart
b) change small memory dump to Automatic memory dump
c) make sure the dump directory is now memory dump
d) reboot after the above changes

2) For Ccleaner please post an image so that for now and in the future the settings will allow you to keep the files needed for troubleshooting

3) For the BIOS the upgrade can be downloaded directly from this link or the HP website link for drivers and BIOS:

HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

https://support.hp.com/au-en/drivers...58?sku=N8L44PA

4) If the HP support assistant is not already installed please install it and check to see that the drivers are up to date:
HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

 

Might have got here a bit late. Laptop won't boot at all now, after I left it unattended for some time doing nothing in particular. Can access PC hardware diagnostics UEFI which doesn't even detect the Hard Drive when I try to test it. Can do a memory check. Memtest86+ wouldn't boot even after changing BIOS settings. Might try booting Linux from a USB or something.

 

Just tried to install the 'Ultimate Boot CD' to a USB to see what I could do and then it booted to windows instead. Wtf? Must have mucked up the BIOS settings trying to boot memtest. Will restore to defaults. For now, backing up data for obvious reasons.

 

While I'm at it, these are the CCleaner settings I'm now working with (the latest crash also failed to create a dump file, but I also hadn't changed the settings as suggested. This has now been done). Any advice regarding booting Memtest correctly? I suppose I could try a CD.

 

Ccleaner settings are ok (make sure that memory dumps, windows log files, and windows error reporting, and windows event logs are not cleaned during the troubleshooting.)

Methods used to use Memtest86+ when initial attempts fail:

Boot from USB Drive on Windows 10 PC Windows 10 Installation Upgrade Tutorials:
Boot from USB Drive on Windows 10 PC Windows 10 Tutorials

Note
If you have fast boot or ultra fast boot enabled in your UEFI firmware settings, then you will need to temporarily disable fast boot or ultra fast boot to be able to boot from a USB.
How to Enable Fast Boot or Ultra Fast Boot in UEFI Firmware Settings for Windows:
Enable or Disable Fast Boot in UEFI Firmware Settings for Windows Windows 10 Tutorials

1. Try another USB stick
2. Try all USB ports (2.0 and 3.0)
3. Maybe when using UEFI Bios you have to temporarily switch to Legacy in BIOS settings
4. Turn off temporarily fast boot, secure boot, CSM if enabled

 

Memtest sucessfully passed 8 times. HD Tune tests also seem to indicate no issue. Surprised it ddidn't blue screen halfway through at random.














In the meantime, I got a different BugCheck 'Critical Process Died'. The nature of the blue screen was very similar to previous blue screens, with the system becomming unresponsive for 15-20 seconds before the blue screen appeared, only this time, it seemed to attempt to recover and failed. System dump files are still failing to write, even after setting the computer to not reset upon blue screening (it gets stuck at 0%). I noticed in the Event Viewer, the Kernel-Power messages had "This error is caused because the system stopped responding and the hardware watchdog triggered a system reset." added to it.

There were no devices with a yellow triangle with a black exclamation mark in the device manager. There is a 'pcouffin device for Amd 64 bits systems' driver with a white circle, blue question mark though.

 

1) For memtest86+ version 5.01 please post an image of the test results into the thread.
2) For problems withing device manager > post images into the thread.
3) For any BSOD run the beta log collector and post a new zip into the thread:
log collector v2-beta08.zip

 

The Memtest86+ Pass: