Enable both Intel and AMD gpu and then run the Hardware & Device troubleshooter again. In fact enable everything that is disabled and then run the Troubleshooter again and see if it can fix the GPUs problem and all the other problems it mentions.
No, don't update the Intel Drivers if it says you shouldn't. Just make sure that there are no yellow exclamation marks or error on the Intel graphics.
Windows has some corruption or missing files that couldn't be fixed by SFC. There is a small free program that will try to download the Windows files that are bad and replace them. It tends to run DISM.exe. But I have found out that sometimes DISM doesn't work if SFC is unable to fix any Windows files. Make sure you can connect to the internet.
The small free program is called SFCFix. Run it and see if it fixes your Windows installation. I have attached the program to this post if you want to download it and use it or you can download from this website: SFCFix 3.0 Free Download for Windows 10, 8 and 7 - FileCroco.com
If the laptop fell 3-4 feet it is a good chance your laptop was damaged or something came loose. Yes, if you can open the rear of the laptop without having to dissemble it and try and see if you see anything abnormal. I know most laptops you can remove the rear cover to install RAM Memory or Hard drive etc. without having to tear it apart.
As for the the two other BSOD Bug codes: 0x03B:
The stop code indicates that executing code had an exception and the thread that was below it, is a system thread.
The exception information returned in paramter one is listed in NTSTATUS Values and is also available in the ntstatus.h file located in the inc directory of the Windows Driver Kit.
One possible exception value is 0xC0000005: STATUS_ACCESS_VIOLATION
This means that a memory access violation occurred.
The !analyze debug extension displays information about the bug check and can be very helpful in determining the root cause.
For more information see the following topics:
Crash dump analysis using the Windows debuggers (WinDbg)
Analyzing a Kernel-Mode Dump File with WinDbg
Using the !analyze Extension and !analyze
In the past, this error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. If you suspect this is the case, use the pool options in driver verifier to gather additional information.
To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace). You can also set a breakpoint in the code leading up to this stop code and attempt to single step forward into the faulting code.
For general troubleshooting of Windows bug check codes, follow these suggestions:
- If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
- If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
- Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.
- Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.
As for BSOD Bug code 0x0D1:
Causehttps://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xd1--driver-irql-not-less-or-equal#cause
A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.
This bug check is usually caused by drivers that have used improper addresses.
If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:
- The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
- The function call was made to a function in another driver, and that driver was unloaded.
- The function was called by using a function pointer that was an invalid pointer.
The !analyze debug extension displays information about the bug check and can be very helpful in determining the root cause.For more information, see Crash dump analysis using the Windows debuggers (WinDbg)To start, examine the stack trace using the k, kb, kc, kd, kp, kP, kv (Display Stack Backtrace)command.If the problem is caused by the driver that you are developing, make sure that the function that was executing at the time of the bug check is not marked as pageable or does not call any other inline functions that could be paged out.If you are not equipped to use the Windows debugger to work on this problem, you can use some basic troubleshooting techniques.
- Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing this bug check.
- If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
- Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications.
Seems like the AMD Driver is causing all the problems. If you can't get the AMD GPU driver to work then I would just disable the AMD Driver in Device Manager and see if you get anymore BSODs. But keep your Intel Integrated Graphics Enabled. If your BSOD stops and you can't install the AMD driver correctly it is possible the AMD GPU card is either loose or got damaged when the laptop fell. Just my personal opinion.
But First try and get your Windows OS repaired.
