This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 67%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECC%3C/text%3E%3C/svg%3E)
While playing on my gaming laptop (a MSI GS66 Stealth), it began to crash while playing games which it used to run with no problem. In the reliability monitor, it gives the following hardware error:
Source
Windows
Summary
Hardware error
Date
4/6/2024 9:03 PM
Status
Report sent
Description
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 124
Parameter 1: 7
Parameter 2: ffffdf0f275be020
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_22631
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.22631.2.0.0.768.101
Locale ID: 1033
Extra information about the problem
Bucket ID: LKD_0x124_7_GenuineIntel_FIRMWARE_{8f87f311-c998-4d9e-a0c4-6065518c4f6d}_IMAGE_GenuineIntel.sys
How do I go about resolving this error or what could be causing it?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Try update Windows and all drivers (including the intel's one).
You may report this issue using the Feedback Hub app.
If problem persists, then check with intel's support.
Thank you, for your prompt reply. I've updated all of my drivers as well as windows but the problem persists. Is it possible I need to update my BIOS?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 14.000000000000002%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECG%3C/text%3E%3C/svg%3E)
Solving your problem through long-distance telepathy is unlikely to work. We can't even see what driver is causing the problem.
My suggestion is to upload the crash dump (MEMORY.DMP) under the windows directory somewhere where others can take a look at it. This can be quite large, easily 700MB to 2 or 3 GB. I might find time for a quick look, at least to identify the driver causing the problem.
The alternative is to identify the driver yourself:
This should identify the driver causing the problem. If it's a peripheral device just chuck it out and get a better equivalent. Consider sending a report to the manufacturer.
Just as info,
I had a similar problem while developing a customer design a while ago. The cause was that the peripheral (a PCIe card) wasn't responding to a read access. So even if the Intel root-complex is reporting the error, the real cause might well be something else.
dmp file.txt Thank you for the suggestion, I have attached what I think is the dmp file here.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
One other thought just crossed my mind, there are a lot of hypervisor messages in your trace. Are you running this on a VM? If so, it could also be an issue with the VM configuration. I don't really use VMs, not very popular in industrial controls, but I have tinkered a bit. Maybe your VM is suggesting that there are more interrupts available than are really supported by the system. Some of the entry level chipsets only support up to eight MSI interrupts per device although PCI Express would allow up to thiry-two, for instance.
If you have updated the driver as suggested, checked the correct driver version aganst your hardware and it still crashes, maybe see what you can configure in the VM.
Thank you once again for your assistance. As for as I know, my computer is not running a virtual machine. I will work through the fix you linked in the comment you posted before this one. I found the original DMP file if you still want it, but I'm not sure how to put it in a file type the attachment tool for the comments will permit.
For some reason, the other comments on this question got deleted, and I'm not sure why.
Yeah, I got a message that a moderator was reviewing the answers. Either the moderator has just run amok or some English word in my comment is an unacceptable curse in another language. I have been given no explanation for "answer has been deleted due to a violation of our Code of Conduct". It makes one wonder ....
Regarding the dump file and your offer to upload, I'm sure that can't be done in the forum, if for no other reason due to the size of the file. Also, it lets people see many details about your machine so it could be a security issue. I don't think you can extract passwords or other sensitive information, though.
You would need to put it on a OneDrive share or something like that. Besides, without the symbols (*.pdb) file I won't really be able to dig into the memory dump. I don't expect either Microsoft or NVidia to publish their *.pdb file.
I was working through the fix you linked, but I got stuck on step 5. When I went to rename the nvlddmkm.sys file, file explorer wouldn't let me, so I've reached a dead end on that front.
Also reinstalling my Nvidia drivers did not fix the problem.
Try performing Clean Boot and see if the problem persists?
Have a look at:
https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
If not, enable services one by one to see which one causing the problem.