Windows 10: Frequent BSOD on Lenovo Gaming Laptop with HyperThreading and Dump File Creation Issues

My Lenovo gaming laptop is experiencing frequent BSODs. I checked the Event Viewer and found a recurring warning before each BSOD:'The hypervisor did not enable mitigations for side-channel vulnerabilities for virtual machines because HyperThreading is enabled. To enable mitigations for virtual machines, disable HyperThreading.' Additionally, I'm seeing a 'Dump file creation failed due to error during dump creation. BugCheckProgress was: 0x00040049' message in the Event Viewer. This issue occurs daily, and I’m unable to diagnose it. Interestingly, if I manually trigger a BSOD, a dump file is c

:)

 

BSOD / Dump File creation failure 161

Hello Aira,

I am Jaspreet Singh.

Please try these steps listed in the guide here and see if the dumps are created after this : https://appuals.com/how-to-fix-dump-file-creati...

Disclaimer: this is a non Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (potentially unwanted products). Thoroughly research any product advertised on the site before you decide to download and install it

 

Multiple 0x0000009c BSODs on Windows 10 Lenovo Laptop

Symptoms:

• Windows 10 Pro BSODs randomly (after freezing). I have almost 12 identical dumps (attached).
• There seems to be no pattern to it but sometimes it happens when the machine is idle.
• The machine just hangs and then eventually reboots -- most of the time I don't even see a BSOD screen, it just goes from a frozen screen to reboot and the dump is generated.

Steps Taken With No Success:

• Ran full memtest with no issues.
• Clean Windows reinstall.
• Changed from HDD to Crucial SSD.
• Updated BIOS and drivers to what I think are the latest (manufacturer website).

Important System Characteristics:

• Lenovo Z70 laptop with dual Intel 5500 and nVidia GeForce 840M graphics cards
• Virtualization technology is turned on in BIOS in order to run virtual machines
• The BSODs stopped for a good while and then started up again quite frequently lately. I haven't been able to pinpoint any changes in how I use the machine.

Most of the dumps seem to point to intelppm.sys --I'm not sure where to go from here.I have attached the output of the information DM log collector. I have gone through all the files and sanitized them to remove any sensitive personal information (according to me) but that shouldn't affect the integrity of the information.

 

Frequent BSOD, the dump file is never created

Frequent BSODs can be incredibly frustrating, especially when there's no dump file to help diagnose the issue. Here are some steps and considerations to help address the problem and potentially support your warranty claim:

1. Ensuring Dump Files are Created

First, let's make sure your system is set up correctly to create dump files:

System Settings for Dump Files:

Right-click on "This PC" and select "Properties".

Click on "Advanced system settings" on the left.

Under the "Advanced" tab, click on "Settings" in the Startup and Recovery section.

Ensure that "Write an event to the system log" is checked.

Set "Write debugging information" to "Kernel memory dump" or "Complete memory dump".

Choose a location for the dump file (typically %SystemRoot%\MEMORY.DMP).

Check Disk Space:

Ensure you have enough disk space on your system drive for the dump file. A complete memory dump can be very large.

Disable Automatic Restart:

In the same Startup and Recovery settings window, uncheck "Automatically restart". This will allow you to see the BSOD error message, which can provide clues.

2. Investigate Hardware Issues

Even though memTest86+ didn’t find errors, there might still be hardware issues:

Check for Overheating:

Ensure your laptop is not overheating. Clean the fans and vents, and consider using a cooling pad.

Test with One RAM Stick:

If your laptop has multiple RAM sticks, try running with just one at a time to see if one might be faulty.

Check Hard Drive Health:

Run diagnostics on your hard drive using tools like CrystalDiskInfo to check for any issues.

3. Analyze Event Viewer Logs

Although the dump file is not created, Event Viewer logs might provide some insights:

Open Event Viewer:

Press Win + X and select "Event Viewer".

Navigate to Windows Logs > System.

Look for critical errors around the time of the BSOD. Pay particular attention to errors related to drivers or hardware.

4. Update Drivers and BIOS

While you mentioned that drivers and BIOS are up-to-date, ensure that all drivers are from the manufacturer’s website rather than relying solely on Windows Update. Consider rolling back to older versions of drivers if the issue started after a recent update.

5. Use System File Checker and DISM

Corrupted system files can also cause BSODs:

Run System File Checker:

Open Command Prompt as an administrator and run sfc /scannow.

Run DISM Tool:

In the Command Prompt, run:

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

Warranty Claim

If the above steps don't resolve the issue and you still can't get a dump file, here are some tips for claiming the warranty:

Document the Issue:

Keep a detailed log of the BSOD occurrences, including dates, times, and any specific activities you were doing when it happened.

Record Video Evidence:

Use your phone to record video of the BSOD occurrences to show the service center.

Include Error Logs:

Provide screenshots or printouts of Event Viewer logs showing recurring critical errors.

By ensuring your system is correctly configured to create dump files, investigating potential hardware issues, analyzing logs, and considering all driver updates, you can better understand and potentially resolve the BSOD issues. If you still face problems, documenting everything thoroughly will support your warranty claim.

If you need more detailed help or run into issues with any of these steps, feel free to ask!

Best,

Alan