Blue screen on my computer multiple times a day

[OlsonPolson]

I have no idea where to start with this problem. This is my only computer and I have no money to go out to get it fixed. What can I do to pin point the problem and solve it?

 

[Colif]

Download and run who crashed: http://www.resplendence.com/whocrashed
it will look at errors and give us a summary

Copy/paste results in here

Can you also follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[OlsonPolson]

Download and run who crashed: http://www.resplendence.com/whocrashed
it will look at errors and give us a summary

Copy/paste results in here

Can you also follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

On Sat 9/17/2016 3:29:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFC0000005)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80920FD2890, 0xFFFFAB00FAD7B368, 0xFFFFAB00FAD7AB90)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: KMODE_EXCEPTION_NOT_HANDLED



On Mon 9/12/2016 9:53:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091216-28046-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12890)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802D5342890, 0xFFFF95004E08C368, 0xFFFF95004E08BB90)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 9/11/2016 11:34:22 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091116-26484-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12890)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801E7BF2890, 0xFFFFB10185BB4368, 0xFFFFB10185BB3B90)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Wed 9/7/2016 5:01:23 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090716-29984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0D0)
Bugcheck code: 0xA0 (0xC, 0xFFFFFFFFC0000001, 0xFFFFC68AD4DDB3E0, 0x0)
Error: INTERNAL_POWER_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
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 9/6/2016 7:36:50 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090616-31265-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12890)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80C064B2890, 0xFFFF800149D1E368, 0xFFFF800149D1DB90)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Mon 8/29/2016 12:46:22 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082816-68546-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12890)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8067FD82890, 0xFFFF91013609A368, 0xFFFF910136099B90)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 8/21/2016 1:35:59 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082016-25359-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x12890)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80A24B62890, 0xFFFFDD80E59B2368, 0xFFFFDD80E59B1B90)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.





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

7 crash dumps have been found and analyzed.
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.