BSOD Multiple Errors on Windows 10 and now 8

[bigphatpanda]

Hello guys. I'm fairly new when it comes to computer stuff so I need some help. About two months back my laptop started crashing due to memory management so I had a family friend look at it and they determined my hard drive was starting to go downhill so I replaced it with a new SSD. This was on Windows 10.

At first it was running fine and then after a few days it continued crashing with new BSOD error codes. I once again had it looked at and it was found that my laptop has 2 video drivers installed and they weren't cooperating properly, so we decided it was best to downgrade back to Windows 8 which my laptop was originally built to run on.
Now it still continues to crash with a variety of BSOD codes and I have no idea what the problem is.

Here's the Minidump files for the last 19 crashes (all of which happened after downgrading):
https://docs.google.com/document/d/1QWgyp7C8CXvaR78qQDHENTfikzwdBouF-n2d8hipkdg/edit?usp=sharing

I would really appreciate it if someone could help me out. Or at least point me in the right direction. Thanks a bunch!

 

[Colif]

I can't read dump files but I knw a program that will, can you download and run who crashed: http://www.resplendence.com/whocrashed
it will look at the dump files and give us a summary and may tell you/us what drivers caused the error

copy/paste results in here, and I see what I can do

 

[bigphatpanda]

I can't read dump files but I knw a program that will, can you download and run who crashed: http://www.resplendence.com/whocrashed
it will look at the dump files and give us a summary and may tell you/us what drivers caused the error

copy/paste results in here, and I see what I can do

So here's the results from the WhoCrashed scan:

Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Aspire V3-771, Acer, VA70_HC
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 16989196288 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 11/8/2016 2:16:00 PM your computer crashed
crash dump file: C:\Windows\Minidump\110816-47000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x1A (0x403, 0xFFFFF680000907C0, 0xBA70000304DE5867, 0xFFFFF680000907C4)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 11/8/2016 2:16:00 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x403, 0xFFFFF680000907C0, 0xBA70000304DE5867, 0xFFFFF680000907C4)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 11/8/2016 2:05:07 PM your computer crashed
crash dump file: C:\Windows\Minidump\110816-5640-01.dmp
This was probably caused by the following module: hal.dll (hal+0x54900)
Bugcheck code: 0xA (0xFFFFFB8B630AFF00, 0x2, 0x1, 0xFFFFF802C267D191)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 11/8/2016 1:51:15 PM your computer crashed
crash dump file: C:\Windows\Minidump\110816-5484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x1A (0x403, 0xFFFFF680001D7168, 0xC790000304DE5867, 0xFFFFF680001D716C)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 11/8/2016 1:09:13 PM your computer crashed
crash dump file: C:\Windows\Minidump\110816-5437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x4E (0x99, 0x3017F9, 0x2, 0x600030000300D7A)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

34 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Colif]

Error: MEMORY_MANAGEMENT - 0x403: The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.

Error: PFN_LIST_CORRUPT - 0x99 : A page table entry (PTE) or PFN is corrupted.

now while the IRQ error could to be a driver, these other two look like hardware. I would suggest running http://www.memtest86.com/ on your ram, any errors are too many. If you get any, replace the stick. test each stick by itself and if one does report errors, check it in another slot just to make sure its the stick and not the slot.

its possible the irq error caused by a driver corrupted in the ram, we shall see I guess.