[SOLVED] BSOD while playing Fallout shelter quite daily.

PC Tailor

Dignified
Herald
I have run both reports and came up with some new exceptions, the KMODE can be hardware or software but is usually down to driver or firmware incompatibility.

Dump 1: https://pste.eu/p/zM5C.html KMODE_EXCEPTION_NOT_HANDLED
Dump 2: https://pste.eu/p/JDKm.html DRIVER_IRQL_NOT_LESS_OR_EQUAL

View the reports for full Bugcheck information.
Before I cover these steps, it's worth noting I may be going over previous ground or there may be reasons for the "out of date" items - just going off what I see:

  • The NVIDIA drivers are out of date
  • Audio driver is pointed as cause. You may want to disable this.
  • I would remove Avira and just run on Windows Defender for the time being.
  • I'd also check if your HWInfo has any updates, whilst this isn't a usual BSOD cause, you never know being as it is accessing HW info.
  • I'd be tempted to disable ALCOR SD Card Driver using |Autoruns (link in report)
  • The ASACPI.sys is also a previous BSOD causer.
Also @gardenman, liking the new look, I think the Blue/White is much nicer! And easier on the eyes.
 
Last edited:

PC Tailor

Dignified
Herald
I have ran the dump file and you can see the full report here:https://pste.eu/p/YXsX.html

Summary of findings:
BugCheck D1, {0, ff, 0, fffff80e36f857f0}
*** WARNING: Unable to verify timestamp for aswVmm.sys
Probably caused by : hardware ( aswVmm+157f0 )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.

Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80e36f857f0, address which referenced memory

PROCESS_NAME: dwm.exe
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_aswVmm.sys
After looking at the BUCKET ID and your stack, you can see that ASWVMM.SYS was present in the stack leading to the crash, and also the DMP file has indicated this is what caused an IP MISALIGNMENT.

ASSWVMM is a driver in your AVAST AntiVirus toolbox. So first port of call I would temporarily uninstall your AV to see if the issue persists.
 
Reactions: ProzacR

gardenman

Admirable
Herald
It looks like both crashes were caused by Panda. Have you tried temporarily removing it yet? If not, I would consider doing so. This may or may not help.
File information:081719-10906-01.dmp (Aug 17 2019 - 13:07:26)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for NNSPIHSW.sys
Probably caused by:hardware (Process: System)
Uptime:2 Day(s), 2 Hour(s), 48 Min(s), and 21 Sec(s)

File information:081519-10656-01.dmp (Aug 15 2019 - 09:10:49)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Driver warnings:*** WARNING: Unable to verify timestamp for NNSNAHSL.sys
Probably caused by:NNSNAHSL.sys (Process: GameCenter.exe)
Uptime:0 Day(s), 1 Hour(s), 58 Min(s), and 18 Sec(s)
Edit: Results: https://pste.eu/p/xpvh.html
 
Last edited:
Reactions: ProzacR

gardenman

Admirable
Herald
The following crashed:

May 10 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/

Full results: https://pste.eu/p/B7PT.html

Look for an update or slightly older version (try a different version from what you are currently using).

Sometimes the dump files are not 100% accurate. The may say things like Firefox or Chrome crashed, when in fact it was the LAN driver that caused the crash.

And then sometimes there's multiple reasons for crashes. Fix one and you get less crashes. Fix another and get less crashes. Fix a another and no more crashes.

Hopefully we are narrowing it down.
 
Reactions: ProzacR

Colif

Win 10 Master
Moderator
another pc with no lan drivers. magic... or, given its from 2009, its likely using microsoft default drivers.

since 90% of loaded drivers are Avast, its a easy guess.

Avast could be cause, I often blame lan drivers if AV crashes but if you can run with just defender for a while, it will tell you if it was avast or not.
 
Reactions: PC Tailor

PC Tailor

Dignified
Herald
another pc with no lan drivers. magic... or, given its from 2009, its likely using microsoft default drivers.

since 90% of loaded drivers are Avast, its a easy guess.

Avast could be cause, I often blame lan drivers if AV crashes but if you can run with just defender for a while, it will tell you if it was avast or not.
Completely agreed - LAN was my other thought, just thought it'd be best to remove AV first and see.
No where near the first time I've (probably we've) seen Avast specifically cause these issues, as with many other AV except a small few.
 

ProzacR

Honorable
Jan 28, 2014
30
4
10,535
0
I changed my anti-virus to Panda and after seeing following posts also I used Driver Booster to install some fresh drivers it installed sound mainly and no BSOD so far. Thanks for help again.
 
Reactions: PC Tailor

Colif

Win 10 Master
Moderator
I used Driver Booster to install...
If you had a newer PC I would tell you that using 3rd party driver updaters can (and will) install the wrong drivers. I have used it myself in past and 2 times it forced me to use system restore to roll back the installs as it had broken other things.

But since you have an older PC, its likely a better choice than looking blindly.

Most newer PC motherboards have updaters now, MSI has Live Update 6, Gigabyte has their APp Centre, Asrock has the App store... even AI Suite on Asus might have a similar feature now. So if you ever get a newer PC, check motherboard website as they might have a tool you can use instead of Driver Booster.

Hope it fixes it for you :)
 
Reactions: ProzacR

gardenman

Admirable
Herald
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/KMps.html

File information:073119-14765-01.dmp (Jul 31 2019 - 14:37:29)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 23 Hour(s), 41 Min(s), and 30 Sec(s)

Possible Motherboard page: https://www.asus.com/Motherboards/P5QLEPU/
It appears you have the latest BIOS already installed. Version: 0408.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
so many panda drivers :)

I can't say I have seen
Nov 01 2012 ASACPI.sys Asus Advanced Configuration and Power Interface http://www.asus.com/
before, but most boards I look at from Asus are a little newer.
What Asus programs are you running? it might have been loaded by windows

Which GPU do you have?
its not a typical error for a gpu, I would expect it to eventually blame dxgkrnl which is Direct X if it were a GPU driver error.

at least your LAN drivers are up to date now.
 

ProzacR

Honorable
Jan 28, 2014
30
4
10,535
0
Try downloading and running Autoruns as if you have removed the asus programs in the past, they left the part behind.
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

ASACPI.sys is driver you want to stop.

it doesn't stop other programs from running it if its needed, it just stops it at startup. See if it helps.
Thanks, I did that right now. I will say how it goes. Also I checked my motherboard page (https://www.asus.com/lt/Motherboards/P5QLEPU/HelpDesk_Download/) there is nothing to install on windows suggested so I have no idea where that ASACPI.sys came from maybe from 'driver booster'.
 
Reactions: PC Tailor

Colif

Win 10 Master
Moderator
Thanks, I did that right now. I will say how it goes. Also I checked my motherboard page (https://www.asus.com/lt/Motherboards/P5QLEPU/HelpDesk_Download/) there is nothing to install on windows suggested so I have no idea where that ASACPI.sys came from maybe from 'driver booster'.
It only came from Driver Booster if you had run it before you did the last time, as it was on the PC when PC Tailor scanned it the first time

it is strange there are no files at all on motherboard website dated after 2009 and yet file is from 2012. Its likely a win 8 driver but for what motherboard? Sure looks like it is likely from Driver Booster, if you had used it in the past.
 
Reactions: ProzacR

gardenman

Admirable
Herald
No problem at all! I ran the dump files through the debugger and got the following information: https://pste.eu/p/CKK3.html

File information:081019-10109-01.dmp (Aug 10 2019 - 08:02:25)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: audiodg.exe)
Uptime:0 Day(s), 0 Hour(s), 38 Min(s), and 23 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
audiodg.exe - audio device graph isolation (part of windows)
I don't see any sound drivers on PC. likely using default ones that come with windows.
motherboard uses VIA audio, newest on site almost having its 10th birthday

hard to tell what to blame on a 10 year old PC.
 

Colif

Win 10 Master
Moderator
Only 2 ways to get driver to show its face: driver verifer or just wait.

But I don't want to suggest Driver verifer because it can leave you in a boot loop where the only good answer is a clean install... and on a 10 year old PC which doesn't even have win 8 drivers, and uses the LGA 775 chipset, that can mean having to reinstall win 7 1st and then update it to 10... so I hesitate

I mean, I guess you could use reset to get out of boot loop but its still a maybe.

tbh, its time for a new PC. Old PC are fine but expecting it to keep working on newer operating systems when the hardware makers themselves don't support them, is only going to end in tears. My last PC had a Dual Core E6600 and there was no way I even looked at WIn 8 yet alone Win 10, And that was in the past when I didn't know what drivers did.
 
Reactions: PC Tailor

ProzacR

Honorable
Jan 28, 2014
30
4
10,535
0
Only 2 ways to get driver to show its face: driver verifer or just wait.

But I don't want to suggest Driver verifer because it can leave you in a boot loop where the only good answer is a clean install... and on a 10 year old PC which doesn't even have win 8 drivers, and uses the LGA 775 chipset, that can mean having to reinstall win 7 1st and then update it to 10... so I hesitate

I mean, I guess you could use reset to get out of boot loop but its still a maybe.

tbh, its time for a new PC. Old PC are fine but expecting it to keep working on newer operating systems when the hardware makers themselves don't support them, is only going to end in tears. My last PC had a Dual Core E6600 and there was no way I even looked at WIn 8 yet alone Win 10, And that was in the past when I didn't know what drivers did.
Well, it is quite obvious that a new PC will not suffer this kind of problem.
What you think about inserting another sound card into an empty PCI slot? Worth a try?
 

ASK THE COMMUNITY

TRENDING THREADS