The game crashed with a fatal error during a BSOD while playing.
The game crashed with a fatal error during a BSOD while playing.
You encountered a reboot from a bugcheck error. Here are the details:
The error code was 0x00000113 with associated parameters saved in the file. The dump is available at the provided link. This isn’t the first issue you’ve faced, and it followed a BSOD. Additional information includes the event ID, execution thread, and system time.
Welcome to the forums, newcomer!
Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time. You've posted this thread in the Windows 10 section. If that wasn't in err, what version(not edition) of the OS are you on?
This is not the first error I've gotten and then proceeded to BSOD.
but you have one .dmp file?
nvlddmkm.sys
Is what I'm seeing with WinDBG. Use DDU to remove all GPU drivers(intel, AMD and Nvidia) in Safe Mode, then manually install the latest GPU driver sourced from Nvidia's support site in an elevated command, i.e, Right click installer>Run as Administrator.
CPU: Intel Core i5 6300HQ
CPU Cooler: It is a laptop so I have no idea how to find this info.
Motherboard:
Model: Lenovo ideapad 700-15ISK SDK0J40709 WIN
Bus Specs. PCI-Express 3.0 (8.0 GT/s) (please do tell me if this is the correct information I've provided)
RAM: DDR4 16GB
PSU: It is a laptop so I have no idea how to find this info.
Chassis: Same as above
OS: Windows 10
Monitor: Same as above
Motherboard Version: E5CN2WW Date: 03/08/2016
I'll be adding the other dumps shortly in the same drive.
Manufacturer: Lenovo
Model: 80RU
SKU: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
I attempted to restart the game, but it shut down within 2 to 3 minutes after launching. The most common issues I encountered were:
Intel® Dual Band Wireless-AC 3165 – network adapter returned an invalid value to the driver.
TabletService service failed to start because the system couldn't locate the specified file.
You haven't provided an answer to the OS version question.
Model: Lenovo ideapad 700-15ISK
Support link: https://pcsupport.lenovo.com/ee/en/...bo...s/pd104075
Specs show no discrete GPU listed, which makes the driver conflict with an Nvidia GPU seem inconsistent. Could you clarify which games you're using and where you obtained the installers?
Regarding the laptop:
Motherboard Version: E5CN2WW
Date: 03/08/2016
Check Lenovo's support page for BIOS updates from 28 Aug 2018. If updated, try reinstalling the chipset drivers.
Did you manually reinstall the chipset drivers?
OS Version:
Microsoft Windows Version 22H2 (OS Build 19045.6216)
Regarding the discrete GPU issue, I accessed the BIOS settings and confirmed the GPU was listed as discrete. The game uses an official launcher and can be downloaded from the following link:
genshin.hoyoverse.com
I want to let you know that I have been playing several titles for more than a year without any problems.
Additionally, the laptop has been serviced twice:
1. I received this laptop from my brother who had a broken hinge last year. I took it to a repair shop to fix the hinge. But soon after, I noticed heating problems. Assuming it was a thermal paste issue, I went to another repair service who told me the motherboard would need replacement (perhaps that explains why this laptop doesn’t show a discrete GPU online).
2. The laptop was opened for fan cleaning and servicing about six months ago.
I will update the BIOS.
And yes, I entered safe mode, ran DDU, then installed the drivers using administrator protocols.
From the dump this is clearly a problem with either the graphics card or the graphics driver. The call stack, which shows all the function calls made in the lead-up to the bugcheck, and which you read from the bottom up, we see the graphics driver nvlddmkm.sys called early on (in frame 5 below)...
Code:
1: kd> k
# Child-SP RetAddr Call Site
00 fffff107`bba17738 fffff801`62e73ad0 nt!KeBugCheckEx
01 fffff107`bba17740 fffff801`62cbc252 watchdog!WdLogEvent5_WdCriticalError+0xe0
02 fffff107`bba17780 fffff801`62c34e51 dxgkrnl!DpiFdoHandleDevicePower+0x86b62
03 fffff107`bba17820 fffff801`62c36381 dxgkrnl!DpiFdoDispatchPower+0x21
04 fffff107`bba17850 fffff801`7e40ea13 dxgkrnl!DpiDispatchPower+0xe1
05 fffff107`bba17970 00000000`00000001 nvlddmkm+0xe3ea13
06 fffff107`bba17978 00000000`00000000 0x1
If we display the details of frame 5 we can see the problem...
Code:
1: kd> .frame /r 5
05 fffff107`bba17970 00000000`00000001 nvlddmkm+0xe3ea13
rax=000000000000139a rbx=0000000000000000 rcx=0000000000000113
rdx=0000000000000019 rsi=ffffc20740d24000 rdi=0000000000000001
rip=fffff8017e40ea13 rsp=fffff107bba17970 rbp=fffff107bba17a09
r8=0000000000000002 r9=00000000000010de r10=fffff801599fd510
r11=000000000000000f r12=ffffc2073b7ebe00 r13=ffffc2073be06010
r14=ffffc2073bf58000 r15=ffffc2073bf58000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040286
nvlddmkm+0xe3ea13:
fffff801`7e40ea13 ?? ???
At the bottom of the above you can see the call to nvlddmkm+0xe3ea13 - this is to the offset 0xe3ea13 into the nvlddmkm.sys graphics driver - the fffff801`7e40ea13 is the resulting virtual address, but the ??? indicates that this address is invalid. We can confirm that this was the instruction that failed by looking at the instruction pointer, this is the RIP register and it contains fffff801`7e40ea13.
What this all means is that a call was made to an address within the nvlddmkm.sys driver that doesn't exist. That could be a problem with the driver, or it could be a problem with the graphics card.
Then I noticed this...
Are you 100% certain that the motherboard they fitted was an EXACT replacement - with the same part number? I don't believe in coincidences and there are three factors here that are almost certainly related...
The motherboard was replaced recently
You don't see a dGPU displayed (have you looked with msinfo32?)
You've had a BSOD that is graphics related
Those three taken together cannot be a coincidence. I would go back to the shop and confirm that the motherboard they installed had exactly the same part number as the old one.
I've updated the BIOS and that should have resolved the BSOD issue, but I encountered another one:
EVENT ID 41: "The system restarted without a clean shutdown. This error might occur if the system stopped responding, crashed, or lost power suddenly."
Also, Furmark is running well with the stress tests. After installing the new BIOS, my in-game performance feels better. Temperatures are much more stable and everything works smoothly now. I suspect the problem could be with the VRM or power rails, though I'm not sure. Also, I’m not sure if anyone would remember this since it’s been a year and I don’t recall placing the receipt.