F5F Stay Refreshed Software Operating Systems BSODs on Lenovo Slim 7 ProX

BSODs on Lenovo Slim 7 ProX

BSODs on Lenovo Slim 7 ProX

Pages (2): 1 2 Next
R
RattleWarrior
Member
64
11-16-2016, 08:40 AM
#1
Hi there, I've been using my Slim 7 ProX laptop for about a year and a half now. Recently, I started experiencing these BSODs. The machine freezes for a few minutes before crashing. Unlike typical BSODs, there are many random errors displayed (see attached photo). BugCheck in EventViewer shows the system rebooted after a bugcheck with ID 0x00000133. A dump was saved at C:\Windows\MEMORY.DMP. Report ID: e39818e4-15a0-4783-8016-b4852df59fa0. These occurrences happen roughly twice a month. BlueScreenView pointed to ntoskrnl.exe+41bf10 as the driver/address. I checked with MemTest and it didn’t reveal any problems, but I might run it for extra assurance. Since the laptop has soldered RAM, I can’t replace parts. Any suggestions on how to fix this would be greatly appreciated. Thanks!
R
RattleWarrior
11-16-2016, 08:40 AM #1

Hi there, I've been using my Slim 7 ProX laptop for about a year and a half now. Recently, I started experiencing these BSODs. The machine freezes for a few minutes before crashing. Unlike typical BSODs, there are many random errors displayed (see attached photo). BugCheck in EventViewer shows the system rebooted after a bugcheck with ID 0x00000133. A dump was saved at C:\Windows\MEMORY.DMP. Report ID: e39818e4-15a0-4783-8016-b4852df59fa0. These occurrences happen roughly twice a month. BlueScreenView pointed to ntoskrnl.exe+41bf10 as the driver/address. I checked with MemTest and it didn’t reveal any problems, but I might run it for extra assurance. Since the laptop has soldered RAM, I can’t replace parts. Any suggestions on how to fix this would be greatly appreciated. Thanks!

M
mccoop03
Posting Freak
910
11-16-2016, 10:59 AM
#2
Looks like a GPU related issue. Also someone reported it could be a drivers problem. Have you updated them recently?
M
mccoop03
11-16-2016, 10:59 AM #2

Looks like a GPU related issue. Also someone reported it could be a drivers problem. Have you updated them recently?

E
EdenMarie
Member
190
11-16-2016, 06:59 PM
#3
Hi, thank you for your update. I haven’t performed a full driver replacement yet, but it might be worth trying. Regarding the BugCheck/dump file, it may not display the exact driver responsible for the BSOD if the GPU isn’t clearly identified. Knowing which GPU is causing the problem would make troubleshooting easier.
E
EdenMarie
11-16-2016, 06:59 PM #3

Hi, thank you for your update. I haven’t performed a full driver replacement yet, but it might be worth trying. Regarding the BugCheck/dump file, it may not display the exact driver responsible for the BSOD if the GPU isn’t clearly identified. Knowing which GPU is causing the problem would make troubleshooting easier.

K
KidArmy21
Member
51
11-18-2016, 12:10 AM
#4
It should. Maybe sending it would help.
K
KidArmy21
11-18-2016, 12:10 AM #4

It should. Maybe sending it would help.

I
Its_Mizz
Member
55
11-18-2016, 11:25 PM
#5
I tried to upload them to the forum directly but it wouldn't let me, so here's a Google drive link: https://drive.google.com/drive/folders/1...sp=sharing . I uploaded one from today as well as an older one. Thanks for the help!
I
Its_Mizz
11-18-2016, 11:25 PM #5

I tried to upload them to the forum directly but it wouldn't let me, so here's a Google drive link: https://drive.google.com/drive/folders/1...sp=sharing . I uploaded one from today as well as an older one. Thanks for the help!

K
kate484803
Member
147
11-19-2016, 04:44 AM
#6
I’m considering turning off the NVIDIA GPU to check for any errors. Your Minidump files would be very useful for diagnosing the problem. Regarding the AMD GPU, it seems the crash might be linked to a faulty driver or installation. The Windows update issue you described could also play a role. It’s possible the OS isn’t updating properly, which might affect system stability. Backing up data and attempting a clean install could help resolve these issues.
K
kate484803
11-19-2016, 04:44 AM #6

I’m considering turning off the NVIDIA GPU to check for any errors. Your Minidump files would be very useful for diagnosing the problem. Regarding the AMD GPU, it seems the crash might be linked to a faulty driver or installation. The Windows update issue you described could also play a role. It’s possible the OS isn’t updating properly, which might affect system stability. Backing up data and attempting a clean install could help resolve these issues.

A
ARMADAE
Member
66
11-19-2016, 08:52 AM
#7
Install the latest Lenovo update and ensure all components refresh. Once complete, run a memory check like MemTest86.
A
ARMADAE
11-19-2016, 08:52 AM #7

Install the latest Lenovo update and ensure all components refresh. Once complete, run a memory check like MemTest86.

M
mineblork
Member
208
11-19-2016, 02:28 PM
#8
Thanks for your update! I downloaded and applied the Lenovo System Update, but only the audio Dolby version was available—no changes were made. I performed two MemTest86 runs and got zero errors. It seems the problem might be connected to thermal management, though my Cinebench test showed no crashes. The CPU reached up to 101°C, which isn’t unusual for these lightweight laptops in performance mode. I’m considering a full Windows reinstall now. It’s odd that Windows hasn’t updated since purchase, but the minidump data hints it could be an AMD-related issue. Noticed today it crashed again, but this was the first time I saw a standard blue screen without the previous artifacts. Any advice or troubleshooting steps would be helpful!
M
mineblork
11-19-2016, 02:28 PM #8

Thanks for your update! I downloaded and applied the Lenovo System Update, but only the audio Dolby version was available—no changes were made. I performed two MemTest86 runs and got zero errors. It seems the problem might be connected to thermal management, though my Cinebench test showed no crashes. The CPU reached up to 101°C, which isn’t unusual for these lightweight laptops in performance mode. I’m considering a full Windows reinstall now. It’s odd that Windows hasn’t updated since purchase, but the minidump data hints it could be an AMD-related issue. Noticed today it crashed again, but this was the first time I saw a standard blue screen without the previous artifacts. Any advice or troubleshooting steps would be helpful!

A
aicontepig
Member
57
11-21-2016, 10:36 AM
#9
101 is quite high, though; I expected thermal throttling to reduce it. For everyday use, it should be fine without problems. I believe a format and reinstall would be best now. Once back in Windows, run the system update again.
A
aicontepig
11-21-2016, 10:36 AM #9

101 is quite high, though; I expected thermal throttling to reduce it. For everyday use, it should be fine without problems. I believe a format and reinstall would be best now. Once back in Windows, run the system update again.

E
Em1_Gamer
Junior Member
2
12-06-2016, 08:40 PM
#10
I'm facing the same problem too—over 30 BSODs since buying the laptop two years ago. I turned off the 3050 discrete GPU in the BIOS; it doesn't seem to be an Nvidia issue. It looks like a driver problem from the AMD iGPU or possibly the Windows HID v2 advanced guestures trackpad driver. I've tried three new motherboards from Lenovo, reimaged the laptop three times, changed the Wi-Fi card, and applied all updates from Microsoft and Lenovo in the last couple of years. I've sent every minidump to AMD using their bug report tool, but nothing has resolved it so far.
E
Em1_Gamer
12-06-2016, 08:40 PM #10

I'm facing the same problem too—over 30 BSODs since buying the laptop two years ago. I turned off the 3050 discrete GPU in the BIOS; it doesn't seem to be an Nvidia issue. It looks like a driver problem from the AMD iGPU or possibly the Windows HID v2 advanced guestures trackpad driver. I've tried three new motherboards from Lenovo, reimaged the laptop three times, changed the Wi-Fi card, and applied all updates from Microsoft and Lenovo in the last couple of years. I've sent every minidump to AMD using their bug report tool, but nothing has resolved it so far.

Pages (2): 1 2 Next