Question BSODs but no dump files ?

Status
Not open for further replies.

supremekaiqc

Honorable
Feb 11, 2018
102
1
10,585
Hello

I have an Acer Predator Helios 300 PH317-54 Laptop.

My last BSOD that whocrashed/bluescreenview is able to catch is from may 2023 and since 2024 I've had 3 BSOD but I cannot troubleshoot them!

I haven't had a dump file to work with :/

any tricks?
 
Update your post to include full system hardware specs and OS information.

On the laptop look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or informational events just before or at the time of the three recent BSODs.
 
Event Viewer and Reliability history monitor has many many errors with
p9HGoFR.png

So I google it and I found that AcerRegistrationBackGroundTask.exe is part of (Acer Product Registration) this software so I uninstalled it.
eSOOxYv.png

Update your post to include full system hardware specs and OS information.

On the laptop look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or informational events just before or at the time of the three recent BSODs.

if you can help further it would be appreciated. If I don't get anymore BSOD then that was the problem and I can thank you in advance.
 
Last edited:
My thought is that the "Registration Task" was likely buggy or corrupt.

However, I am somewhat skeptical about the purpose(s) of that task.....

Just work as normal and if the BSODs return then look for additional error codes etc..

Post accordingly.
 
  • Like
Reactions: supremekaiqc
My thought is that the "Registration Task" was likely buggy or corrupt.

However, I am somewhat skeptical about the purpose(s) of that task.....

Just work as normal and if the BSODs return then look for additional error codes etc..

Post accordingly.
Hello I got a new BSOD now it was UNEXPECTED STORE EXCEPTION
but it's always this one I think.
Still no dump files. Got the bluescreen then PC blackscreened I had to force shutdown.

Event Viewer caught these errors at the same minute of the PC restarted.
NsjYSKl.png

Ok I caught another error but I can't take a picture cause it's in french so im gonna use google translate

Event 161, Source: volmgr
Failed to create the dump file due to an error creating the dump file.

Event 1012, Source: DNS Client Events
An error occurred while reading the local hosts file.

Event 7023, Source: Service Control Manager
The GameInput Service stopped with the error:
The GameInput Service compound file was produced with a newer version of memory.

Event 7031, Source: Service Control Manager
The GameInput Service terminated unexpectedly. This happened 1 time. The following corrective action will be performed in 1000 milliseconds: Restart the service.
 
Last edited:
Before going any further try "dism" and "sfc /scannow" to find and fix any corrupted files.

FYI:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Objective being to stop the errors or at least reduce the number and type of errors.
Ok Sadly, I got another BSOD with no DUMP FILES again.

Before the Bluescreen I could tell that I would get it.
First my videogame froze my mouse froze and then after like 10 sec my discord voice chat stopping working and then after 30-45 seconds I finally got the bluescreen

UNEXPECTED STORE EXCEPTION.
 
Last edited:
That error can result from quite a number of things.

Uninstall Discord for a few days to determine if the BSODs end.

If not, then disable any other apps or utilities that do not need to be running.

Objective being to hopefully end the BSODs.

The next steps being to enable those disabled apps and utilities one at a time. If the BSOD returns the last re-enabled app or utility is a likely culprit.

The troubleshooting process must be slow and methodical. Keep notes. Watch for other errors or system changes.

= = = =

FIY - Reference purposes:

https://www.softwaretestinghelp.com/unexpected-store-exception-fixed/

And here is a Microsoft link regarding the error:

https://answers.microsoft.com/en-us...ndows-11/25c375c0-cbd5-49e5-94d6-dc910161e939

Read both links carefully and any other things that may have happened with respect to the laptop's performance and behavior.

Then try Methods 1 and 2 in the Microsoft Link.

As always, be sure that all important data is backed up at least 2 x to locations away/off of the laptop. Verify that the backups are recoverable and readable.
 
That error can result from quite a number of things.

Uninstall Discord for a few days to determine if the BSODs end.

If not, then disable any other apps or utilities that do not need to be running.

Objective being to hopefully end the BSODs.

The next steps being to enable those disabled apps and utilities one at a time. If the BSOD returns the last re-enabled app or utility is a likely culprit.

The troubleshooting process must be slow and methodical. Keep notes. Watch for other errors or system changes.

= = = =

FIY - Reference purposes:

https://www.softwaretestinghelp.com/unexpected-store-exception-fixed/

And here is a Microsoft link regarding the error:

https://answers.microsoft.com/en-us...ndows-11/25c375c0-cbd5-49e5-94d6-dc910161e939

Read both links carefully and any other things that may have happened with respect to the laptop's performance and behavior.

Then try Methods 1 and 2 in the Microsoft Link.

As always, be sure that all important data is backed up at least 2 x to locations away/off of the laptop. Verify that the backups are recoverable and readable.
I did most of what they said already the only thing I didn't do was Driver Verifier. I am scared of that thing.
 
I am not familar with Driver Verifier per se - generally do not use such utilities/tools.

Many of those tools just use some built in Windows/Microsoft code and present a different graphical picture.

You can learn about the installed drivers in other ways.

Here is a link that uses Device Manager and Powershell.

https://www.technorms.com/87172/how-to-check-driver-version

You do not need to download anything.

If you are only concerned about a few specific drivers then use Device Manager per Method 1.

For a much longer list with details then use Method 2. Powershell (which is what I do) to obtain the driver information.

What makes it easy is that you do not need to retype the Get-WinObject ...... cmdlet. You can copy and paste the text in the grey box into Powershell. Shown in red color below.

Here is what doing so looks like (shown in bold) on my computer. Note that I did not copy and paste all of the results.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\WINDOWS\system32> Get-WmiObject Win32_PnPSignedDriver| select DeviceName, Manufacturer, DriverVersion

DeviceName Manufacturer DriverVersion
---------- ------------ -------------
Local Print Queue HP 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
WAN Miniport (Network Monitor) Microsoft 10.0.22621.1
WAN Miniport (IPv6) Microsoft 10.0.22621.1
WAN Miniport (IP) Microsoft 10.0.22621.1
WAN Miniport (PPPOE) Microsoft 10.0.22621.1
WAN Miniport (PPTP) Microsoft 10.0.22621.1
WAN Miniport (L2TP) Microsoft 10.0.22621.1
WAN Miniport (IKEv2) Microsoft 10.0.22621.1
WAN Miniport (SSTP) Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Linksys, LLC 10.0.22621.1
Generic software device Linksys, LLC 10.0.22621.1
Microsoft Wireless Router Module Linksys, LLC 1.0.0.2
My Book Live Network Storage Western Digital Corporation 2.2.0.7
Generic software device HP 10.0.22621.1
WSD Scan Device HP 10.0.22621.1
HP OfficeJet Pro 9010 series PCL-3 HP 29.117.2.7675
WSD Print Device HP 10.0.22621.1
Generic software device HP 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Computer Device Microsoft 10.0.22621.1
Audio Endpoint Microsoft 10.0.22621.1
Audio Endpoint Microsoft 10.0.22621.1
Oculus Virtual Audio Device Microsoft 13.3.46.740
Remote Desktop Device Redirector Bus Microsoft 10.0.22621.2506
Oculus Virtual Gamepad Emulation Bus Facebook, Inc. 1.5.8.0
Plug and Play Software Device Enumerator (Standard system devices) 10.0.22621.1
Microsoft System Management BIOS Driver (Standard system devices) 10.0.22621.1
NDIS Virtual Network Adapter Enumerator Microsoft 10.0.22621.1
NVVHCI Enumerator NVIDIA 3.5.3090.2760

.
.
.
.
.

Requires a bit of reading searching to work throught the list and find any specific driver and version information.

If you are comfortable trying something new and a little bit of "coding" then give Powershell (Method 2) A a try.

A "Get-" cmdlet just does that. It gets information and will not try to download, install, etc.. There are other Powershell cmdlets used for such things.
 
Also I just noticed in Event Viewer there is this thing with 2000 errors in the past 7 days 500 in the last 24 hours and 24 in the last hour it is

Event ID: 808
Source: PrintService

Print spooler failed to load a plug-in C:\WINDOWS\system32\spool\DRIVERS\x64\3\FXSUI.DLL, Error Code 0x7F

and also Event ID 131
Source: DeviceSetupManager

this one has 250 errors in the last 7 days

can this help a little bit?

I am not familar with Driver Verifier per se - generally do not use such utilities/tools.

Many of those tools just use some built in Windows/Microsoft code and present a different graphical picture.

You can learn about the installed drivers in other ways.

Here is a link that uses Device Manager and Powershell.

https://www.technorms.com/87172/how-to-check-driver-version

You do not need to download anything.

If you are only concerned about a few specific drivers then use Device Manager per Method 1.

For a much longer list with details then use Method 2. Powershell (which is what I do) to obtain the driver information.

What makes it easy is that you do not need to retype the Get-WinObject ...... cmdlet. You can copy and paste the text in the grey box into Powershell. Shown in red color below.

Here is what doing so looks like (shown in bold) on my computer. Note that I did not copy and paste all of the results.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\WINDOWS\system32> Get-WmiObject Win32_PnPSignedDriver| select DeviceName, Manufacturer, DriverVersion

DeviceName Manufacturer DriverVersion
---------- ------------ -------------
Local Print Queue HP 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
Local Print Queue Microsoft 10.0.22621.1
WAN Miniport (Network Monitor) Microsoft 10.0.22621.1
WAN Miniport (IPv6) Microsoft 10.0.22621.1
WAN Miniport (IP) Microsoft 10.0.22621.1
WAN Miniport (PPPOE) Microsoft 10.0.22621.1
WAN Miniport (PPTP) Microsoft 10.0.22621.1
WAN Miniport (L2TP) Microsoft 10.0.22621.1
WAN Miniport (IKEv2) Microsoft 10.0.22621.1
WAN Miniport (SSTP) Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Linksys, LLC 10.0.22621.1
Generic software device Linksys, LLC 10.0.22621.1
Microsoft Wireless Router Module Linksys, LLC 1.0.0.2
My Book Live Network Storage Western Digital Corporation 2.2.0.7
Generic software device HP 10.0.22621.1
WSD Scan Device HP 10.0.22621.1
HP OfficeJet Pro 9010 series PCL-3 HP 29.117.2.7675
WSD Print Device HP 10.0.22621.1
Generic software device HP 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Generic software device Microsoft 10.0.22621.1
Computer Device Microsoft 10.0.22621.1
Audio Endpoint Microsoft 10.0.22621.1
Audio Endpoint Microsoft 10.0.22621.1
Oculus Virtual Audio Device Microsoft 13.3.46.740
Remote Desktop Device Redirector Bus Microsoft 10.0.22621.2506
Oculus Virtual Gamepad Emulation Bus Facebook, Inc. 1.5.8.0
Plug and Play Software Device Enumerator (Standard system devices) 10.0.22621.1
Microsoft System Management BIOS Driver (Standard system devices) 10.0.22621.1
NDIS Virtual Network Adapter Enumerator Microsoft 10.0.22621.1
NVVHCI Enumerator NVIDIA 3.5.3090.2760

.
.
.
.
.

Requires a bit of reading searching to work throught the list and find any specific driver and version information.

If you are comfortable trying something new and a little bit of "coding" then give Powershell (Method 2) A a try.

A "Get-" cmdlet just does that. It gets information and will not try to download, install, etc.. There are other Powershell cmdlets used for such things.
 
Seems to be a moving target here....

If, as it appears "dism" and "sfc /scannow" did not resolve the problem then the next step would be to reinstall the printer drivers.

Check that the print queue is empty and, if not, delete any pending print jobs. The clear the Event Viewer logs and observe to 1) see if the BSOD's continue and/or the Errors continue to occur.

If the errors continue then reinstall the printer drivers.

Make and model printer?

Go to the applicable manufacturer's website to manually download the applicable printer drivers.

Be sure that the website is really the manufacturer's website. Just because the manufacturer's name appears in the pathname/URL does not mean that the link is truly the manufacturer.

Once the printer driver is downloaded manually reinstall and reconfigure.

Hopefully any remaining problems will stand out via the Event Viewer logs.
 
HP OfficeJet 8020 series PCL-3

there's a big queue of stuff idk why so I'm gonna uninstall everything. I don't own this printer anymore anyways.

thank you for that.
 
Status
Not open for further replies.

Latest posts