Troubleshoot A couple bluescreens

[Overkill]

Briefly explain your current issue(s)

Running ok currently

Steps taken to resolve, but have been unsuccessful

ran memtest 9 passes and no errors

Can someone help find the culprit?
dump files
Download dumpfiles.zip



system info

OS Version: Microsoft Windows 7 Home Premium, Service Pack 1, 32 bit
Processor: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz, x64 Family 6 Model 15 Stepping 6
Processor Count: 2
RAM: 3062 Mb
Graphics Card: Intel(R) 82945G Express Chipset Family, 256 Mb
Hard Drives: C: Total - 61443 MB, Free - 40949 MB; D: Total - 243696 MB, Free - 45260 MB;
Motherboard: ASUSTek Computer INC., LEONITE
Antivirus: None

 

[Overkill]

Were you using Chrome while experiencing? Maybe DEV version?

No. I only run stable versions of chrome

 

[vivid]

It was probably caused by : FSPFltd2.sys

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82b6d985, The address that the exception occurred at
Arg3: b14ad6c0, Trap Frame
Arg4: 00000000

Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M - Windows 10 hardware dev

 

[DracusNarcrym]

It was probably caused by : FSPFltd2.sys

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82b6d985, The address that the exception occurred at
Arg3: b14ad6c0, Trap Frame
Arg4: 00000000

Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M - Windows 10 hardware dev

According to @Overkill, it's been solved now, but I believe the dumpfiles pointed to ntoskrnl.exe and hal.dll.

 

[Overkill]

So far so good. Thanks to all who replied