Multiple bugcheck codes in a small time interval. It indicates to a memory malfunction. Not necessarily the physical memory, a misbehaving driver may also do it.
Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If it does not show any error, enable Driver Verifier to monitor the drivers. Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using
CCleaner looking at Tools > System Restore.
If there is no points,
make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.
______________________________________
Code:
BugCheck 18, {0, fffffa8007e9a7b0, 2, fffffa8006b1c780}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 )
Followup: MachineOwner
---------
Code:
BugCheck 50, {ffffd6fb7ea00118, 0, fffff800035c1382, 7}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43781 )
Followup: MachineOwner
---------
Code:
BugCheck A, {20, 2, 1, fffff800034cd77c}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+605 )
Followup: MachineOwner
---------