Question Constant BSODs on laptop ?

[sebsnbach]

Hi,

Laptop model: Acer Nitro AN517-42

ive been struggling with a LOT of bluescreen errors on my laptop. Its mostly during the use of browsers or even on the login-page.
Most common error is irql not less or equal, but also Kernel Mode Trap, Kernel Mode Error, Data Store Corruption.
At this point it is hardly useable anymore.

Ive tried some stuff:
DISM commands, SFC, and checking the RAM.

Here are some dump files from today

https://www.mediafire.com/file/m1dkfuq79t0ujq3/032024-11890-01.dmp/file

032024-12031-01

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

Im not super knowledgeable about Computers at all, so im hoping someone can point me in the right direction to fix this.


EDIT:

More Dumpfiles from today:
https://www.mediafire.com/file/c9swkopeiu2z6sl/032024-11937-01.dmp/file

032024-12031-02

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.

www.mediafire.com

https://www.mediafire.com/file/edt19c4q3eex2pf/032024-12140-01.dmp/file

 

[ubuysa]

This looks very much like a possible RAM problem from these dumps. I'd first suggest a proper RAM test...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

 

[sebsnbach]

Hey, thanks for your reply. Got back a bit later.
I did the memtest today, but it came back with 0 errors.

Is there any other thing that can be checked?

At this point i think i have to send it in for warranty.

 

[ubuysa]

Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file.

The SysnativeBSODCollectionApp does not collect any personally identifying information, it's perfectly safe, and it#s used by several respected Windows help forums. You can look at the files in the zip file, mostly they are txt files, but please don't change or delete anything. If you want to know what data these files contain there are full details here.

 

[sebsnbach]

Hi, here is the ZIP File:

https://www.mediafire.com/file/vzi6q5a5luthpbj/SysnativeFileCollectionApp.zip/file

 

[sebsnbach]

Some other things i noticed:

I do not get BSOD while running a game (i only play one though, so i dont know if that is generally true). I also have Browser Tabs frequently crashing, especially while watching youtube videos.

Also I have had way less bluescreens since i ran the memtest, but might also be a coincidence.
I havent been using my laptop too much.

Thank you for the help, i do very much appreciate it.

 

[Satan-IR]

Do you have Avira antivirus installed on the laptop by any chance?

 

[sebsnbach]

Hi,

yes I had Avira installed.

I was looking at the reports done through cmd
perfmon /rel

I had noticed a while ago that Killer utility services was listed there often so I uninstalled that.
A week ago I saw Avira making issues (did not happen in the past). So I uninstalled it as well. During Uninstalling it needed to repair. No it is not installed anymore but the issues still persist.

 

[ubuysa]

There are still strong indications in those dumps that this is most likely a hardware problem. However, further hardware tests will prevent you from using your PC for some time whilst the tests run, so I think it's probably better to check for rogue third-party drivers first.

To do that you're going to enable Driver Verifier. Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

To enable Driver Verifier do the following:

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

These are high-level Microsoft drivers that manage lower-level third-party drivers that we otherwise wouldn't be able to trap. That's why they're included.

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running for 48 hours, use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past. If Windows doesn't automatically reboot after each BSOD then just reboot as normal and continue testing. The Driver Verifier generated BSOD stop codes are these...

• 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
• 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
• 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
• 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
• 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
• 0xE6: DRIVER_VERIFIER_DMA_VIOLATION

If you see any of these BSOD types then you can disable Driver Verifier early because you'll have caught a misbehaving driver.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query. If drivers are listed then it's enabled, if no drivers are listed then it's not.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up if you like, or not as you choose. Upload the file(s) to the cloud with a link to it/them here (be sure to make it public).

Let's see what that tells us...

 

[Satan-IR]

Well when I checked the one dump you uploaded in post #1 before the edit NETTIO and the netprotection_network_ filter driver come up.

If that dump was created before you uninstalled the Avira and Killer utility network thing I agree with ubuysa that the BOSDs might indicate a hardware issue like RAM too. I would first try to rule out a driver issue.

Therefore, follow the instructions and see if DV shows a driver not playing nice. To emphasize, don't skip the step where you make a restore point or image as you might end up in a BSOD loop.

 

[sebsnbach]

Hello guys, the dumps should all be created from after uninstalling Avira and the Killer utility thing.

I've had a busy week and I'm on vacation now in between switching jobs.

So I can only look into the issue further towards the end of april.

I appreciate the help and will get back, but it will take a while!

Thank you.

 

[ubuysa]

No problem, we'll still be here...