hello everyone, i have multiple BSOD and crashes in my laptop i hope you can help me guys, and thank you for your time

[jossef2k]

hello everyone, i have multiple BSOD and crashes in my laptop i hope you can help me guys, and thank you for your time
my laptop specs:
lenovo legion 5
Processor AMD Ryzen 7 4800H with Radeon Graphics 2.90 GHz
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor
gpy nvidia 2060

 

[ubuysa]

Hello, and welcome to the forum!

I've had a look through your dumps and all the indications are that your problem is most likely flaky RAM. The first thing I'd suggest you do is to pop each of the RAM cards out and then reseat them firmly. It's not uncommon to find that this solves the problem.

If you still get BSODs after reseating the RAM then you'll need to run a thorough 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.

This will find most RAM issues, even a single bit error is a failure.

Let us know how that goes.

 

[jossef2k]

hi thank you for answering me, and yes i did all what you said no problem found in the memory
i uploaded another dump file you can look at, and thank you again for your time

 

[ubuysa]

Bear in mind that Memntest86 cannot prove that you RAM is good, but for mow we'll assume that it is.

Three of the latest four dumps (all dated 20th Jan) fail for the same reason - an invalid memory reference...

nt!PoIdle+0x3ba:
fffff806`050541da 00740938        add     byte ptr [rcx+rcx+38h],dh ds:00000000`0000003c=??

Netwtw10+0xa57ee:
fffff802`432057ee aa              stos    byte ptr [rdi] ds:00000000`00000000=??

nt!PoIdle+0x3ba:
fffff806`4e6541da 00740938        add     byte ptr [rcx+rcx+38h],dh ds:00000000`0000003c=??

Note also that two of them are identical and fail in exactly the same place and whilst the processor is running the idle loop (nt!PoIdle). This very strongly points at a hardware cause.

The third fails in a third-party driver (Netwtw10.sys) which is an Intel driver for your AX200 wireless card. The version of this driver you have loaded in old, dating from 2021, so it's worth looking for any update. I don't think this is the root cause however, because it doesn't account for the two failures in the idle loop.

The fourth dump is interesting. It fails during the execution of a processor timer query instruction, so doesn't reference anything external to the CPU...

nt!HalpTscQueryCounterOrdered:
fffff801`2b365520 0f01f9          rdtscp

The rdtscp instruction is the Read Time Stamp of the Current Processor instruction, and a failure here might suggest a CPU issue - which would of course account for all other issues. In addition, the logical processor in these four dumps was either 0 or 1, so I checked all your other dumps and the logical processor in every one is either 0 or 1.

Laptops are prone to overheating, so before we get into testing your CPU please download HWMonitor (free) and post a screenshot of the CPU temperatures (all cores) both at idle (with nothing running) and at the maximum load you can throw at it.

If those temperatures are acceptable then we'll look at running a CPU stress test.

 

[jossef2k]

hello ubuysa, i can guarantee that my CPU is cool and not overheating, i clean the laptop and fans, so no dust build up, i did remove one ram stick to test but i still got the BSOD but maybe less frequently, i really don't know what information i can provide so you can help me, im gonna use the laptop for 24 hours then upload another ZIP file because i don't have another one i did reset the machine but no luck so far to solve the problem, thank you again for your help and time i really appreciate it

 

[ET_Explorer]

BSOD(s) and Crashings happens for a reason; What were you doing on your computer/laptop when these problems started?

 

[ubuysa]

hello ubuysa, i can guarantee that my CPU is cool and not overheating, i clean the laptop and fans, so no dust build up, i did remove one ram stick to test but i still got the BSOD but maybe less frequently, i really don't know what information i can provide so you can help me, im gonna use the laptop for 24 hours then upload another ZIP file because i don't have another one i did reset the machine but no luck so far to solve the problem, thank you again for your help and time i really appreciate it

We need hard data before we can eliminate anything. I don't doubt that you keep it clean but the CPU paste could have failed for example. I really would like to see HWMonitor temps for all CPU cores both at idle and at max load. It's always important to start with the simple things and work inwards, and it's never wise to assume anything.

 

[jossef2k]

hello Ubuysa i have some good news ! for 48 hours my laptop did not crash or have a BSOD from a long time, thanks for you instructions.

I'm gonna walk you through what i did that may solved the problem :

-first of all i removed a 8 GB ram stick (i have 16 GB ram, two sticks, the machine now running by just 8 GB ram) first time i used the stick in spot 1 and i did have BSOD next time i did it in the spot 2 and that where the ram is now

-next i did a driver stress using a windows build in tool, i got 2 BSOD one with Nvidia error the other one without any error message

-next i removed some Microsoft/windows updates and i did a 30 days pause for the next updates.

and surprise the machine was stable i did upload another zip file, I'm afraid to install again the other stick , but i think i have to do that anyway to see if it the spot or the stick problem right?

-the other thing is i have some weird warnings and errors in the event viewer, i don't know why.

and again i can't thank you enough, you are a life saver, i was stressed so much about this issue.

i'm gonna let you know about the ram situation

 

[ubuysa]

Thank you for uploading the data. I don't see anything terribly worrying in either you System or Application logs. The dumps could all be explained by bad RAM, so if it's stable with one RAM stick removed it would be wise to swap sticks. Run it on just the other stick, if it fails then you can be pretty certain that that's the faulty RAM and the cause of your problems.

I would still strongly recommend that you download HWMonitor as suggested earlier and post a screenshot of all CPU core temperatures both at idle and at full load. Laptops are notorious for overheating and CPU paste doesn't last forever. I appreciate that you don't think that overheating is the problem but it is essential that we confirm that with real data. I do urge you to provide this information.

 

[jossef2k]

hello again ! the machine has not crashed yet

i did what you said using Heaven Benchmark 4.0

i uploaded the images before and in the time of benchmarking

btw i did reinstall the other ram stick, no problem no BSOD

i dont know what was the problem at the first time

 

[ubuysa]

Unfortunately those HWMonitor uploads don't show the individual CPU core temps - which is what I really wanted to see. Be sure to expand the CPU temp section so that all cores are shown separately .

Also, please post a screenshot of CPU temps whilst at idle (label it idle please) and post another screenshot whilst you have the maximum load you can throw at it running (label that full_load please).

 

[jossef2k]

sorry here is another screenshots, i got the most heat when playing a game even if the utilization of the CPU is 50 %(before and when playing a game)

i did a benchmark using cinebench 100 % CPU utilization

(i did rename the screenshots so you can know when it was toking )

 

[ubuysa]

Thanks for doing that. We now have hard data that confirms you don't have an overheating problem.

 

[jossef2k]

no crashing yet, i think problem solved

ubuysa Thank you ! i wish you the best in your life​

 

[jossef2k]

the BSOD are back
i replaced the ram sticks with a new 16 gb ram but no luck

 

[ubuysa]

Please run the SysnativeBSODCollectionApp again and upload the output.

Was the new 16GB RAM on the QVL for the motherboard?

 

[jossef2k]

i used the tool WhoCrashed but i couldn't understand what the problem, i even got a new ssd and new ram sticks, but no luck, the machine does not overheat, im so frustrated i cant use the pc it keep crashing on me, please help and thank you in advance ! i uploaded the C:\Windows\Minidump in this link : Download Data package from March 12th.



Crash Dump Analysis

---

Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Tue 12-Mar-24 6:43:20 AM your computer crashed or a problem was reported

Crash dump file:	C:\Windows\Minidump\031224-9531-02.dmp (Minidump)
Bugcheck code:	0xA(0x2E, 0xFF, 0x0, 0xFFFFF80784A03EB7)
Bugcheck name:	IRQL_NOT_LESS_OR_EQUAL
Bug check description:	This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

On Tue 12-Mar-24 6:43:20 AM your computer crashed or a problem was reported

Crash dump file:	C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0xA(0x2E, 0xFF, 0x0, 0xFFFFF80784A03EB7)
Bugcheck name:	IRQL_NOT_LESS_OR_EQUAL
Bug check description:	This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

 

[ubuysa]

It's always best to run the SysnativeBSODCollectionApp whenever you get new BSODs, that way we always get all the troubleshooting data we need. Looking at that recent dump however, and also considering your earlier dumps, the common thread here is the graphics card or driver. All of the dumps show that there was a graphics operation in progress at the time of the bugcheck. The version of the graphics driver that you have installed appears current...

0: kd> lmvmnvlddmkm
Browse full module list
start             end                 module name
fffff807`9d520000 fffff807`a0f74000   nvlddmkm T (no symbols)          
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvltsig.inf_amd64_e48e750a86adc1a0\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Feb 15 13:38:19 2024 (65CDF7AB)
    CheckSum:         0393875D
    ImageSize:        03A54000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

That suggests that it might be the card itself that's at fault. The first thing I'd suggest you try is to remove and re-seat the graphics card and any additional power cable to it.

Then, if it still BSODs, you'll need to check to see whether it's the card or the driver that's at fault. The best way to do that is to do the following...

1. Download the Display Driver Uninstaller (DDU).
2. Download the most recent three driver versions for your card from the Nvidia website.
3. Run DDU to uninstall the current driver (the system will reboot).
4. Install the most recent graphics driver.
5. If it BSODs then use DDU to uninstall the driver.
6. Install the immediately prior driver version.
7. If it BSODs then use DDU to uninstall the driver.
8. Install the two versions prior driver version.

If it BSODs on all three of the most recent driver versions, using DDU in between them, then it's most likely the graphics card. In that case, remove the RTX2060 and plug into the motherboard to use the Radeon iGPU. Graphics performance will be poor of course, but if you can't make it BSOD then it the RTX2060 is the problem.

 

[jossef2k]

i have a laptop Lenovo Legion 5 how can i remove the GPU ?

 

[ubuysa]

My mistake. The best you can do then is to disable it in device manager and reboot (to unload the driver for it).