- May 19, 2014
- 2
- 0
- 4,510
Hi everyone, I've recently built myself a new computer. Ever since I've built it I've been having constant blue screens. It mainly happens when I'm on a browser, watching a video on the internet or playing a game through steam. At first I never had any blue screens but my games constantly crashed to the desktop - so I formatted my hard drive and reinstalled windows and all the drivers again but now I get blue screens whenever I play or game or sometimes they just crash to the desktop.
I tested my ram and it's not faulty, however is it safe to run the memtest a few more times just to double check? This problem has been driving me crazy for about a week and I've been trying to figure it out for myself but I'm all out of options - I just cannot figure out what is wrong with my computer. I've read everywhere and it's all people saying "could be the power supply, could be the ram, could be your mouse and keyboard, could be your monitor, could be outdated drivers causing a conflict, could be faulty hardware" so before I go replacing all my parts for my pc I was just wondering if someone could please help me with this! 😀
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer To be filled by O.E.M.
System Model To be filled by O.E.M.
System Type x64-based PC
Processor AMD FX(tm)-8350 Eight-Core Processor, 4000 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 2006, 01/10/2013
SMBIOS Version 2.7
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.90 GB
Available Physical Memory 5.21 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 12.5 GB
Page File Space 7.90 GB
Page File C:\pagefile.sys
My graphics card is GTX760 (factory overclocked) I've used afterburner to "try" and underclock it but I'll be honest I'm not even sure how much I should underclock it by and which things I should be underclocking! I've done a clean install of the newest graphics drivers with some software but I didn't do it in safe mode if that makes a difference.
And here is the crash log I got from WhoCrashed v 5.01
System Information (local)
--------------------------------------------------------------------------------
computer name: SAMUEL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8482394112 total
VM: 2147352576, free: 1933049856
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 20/05/2014 02:46:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-25802-01.dmp
This was probably caused by the following module: clfs.sys (CLFS+0x4B82E)
Bugcheck code: 0xD1 (0xFFFFFA7FF7CA20BD, 0x2, 0x1, 0xFFFFF88000CAE82E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\clfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Common Log File System Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 20/05/2014 02:00:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-21871-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA8060960090, 0x2, 0x1, 0xFFFFF80002C8E5EF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 20/05/2014 01:27:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-21855-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E2F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004987E2F, 0xFFFFF880025D7568, 0xFFFFF880025D6DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread 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 19/05/2014 21:01:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-27393-01.dmp
This was probably caused by the following module: avgtdia.sys (0xFFFFF88004518F20)
Bugcheck code: 0xD1 (0xFFFFFA80C03EFA40, 0x2, 0x0, 0xFFFFF88004518F20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\avgtdia.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Network connection watcher
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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. It is suggested you look for an update for the following driver: avgtdia.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 19/05/2014 05:30:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-26769-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0xFFFFF80006000000, 0x2, 0x0, 0xFFFFF80002E0B6FB)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid memory at a process IRQL that was too high.
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.
On Mon 19/05/2014 04:01:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-27440-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x76378)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000106378, 0xFFFFF88007FA6F60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 19/05/2014 03:00:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-27050-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5705D)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF8800165805D)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 18/05/2014 21:50:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-29546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF880066F0240, 0xFFFFF880096F0240, 0xFFFFF880006F0240)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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.
On Sat 17/05/2014 20:21:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-31527-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x384D8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C9A4D8, 0xFFFFF880025D6988, 0xFFFFF880025D61E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 17/05/2014 03:11:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-28610-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x162A72)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8801124CA72, 0xFFFFF880025D6C68, 0xFFFFF880025D64C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 335.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 335.23
Bug check description: This indicates that a system thread 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. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
if someone or anyone could take the time to suggest different things I should do to narrow down the possible causes for this error I'd be so thankful because it really could be anything!
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation)
avgtdia.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.)
I tested my ram and it's not faulty, however is it safe to run the memtest a few more times just to double check? This problem has been driving me crazy for about a week and I've been trying to figure it out for myself but I'm all out of options - I just cannot figure out what is wrong with my computer. I've read everywhere and it's all people saying "could be the power supply, could be the ram, could be your mouse and keyboard, could be your monitor, could be outdated drivers causing a conflict, could be faulty hardware" so before I go replacing all my parts for my pc I was just wondering if someone could please help me with this! 😀
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer To be filled by O.E.M.
System Model To be filled by O.E.M.
System Type x64-based PC
Processor AMD FX(tm)-8350 Eight-Core Processor, 4000 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 2006, 01/10/2013
SMBIOS Version 2.7
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.90 GB
Available Physical Memory 5.21 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 12.5 GB
Page File Space 7.90 GB
Page File C:\pagefile.sys
My graphics card is GTX760 (factory overclocked) I've used afterburner to "try" and underclock it but I'll be honest I'm not even sure how much I should underclock it by and which things I should be underclocking! I've done a clean install of the newest graphics drivers with some software but I didn't do it in safe mode if that makes a difference.
And here is the crash log I got from WhoCrashed v 5.01
System Information (local)
--------------------------------------------------------------------------------
computer name: SAMUEL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8482394112 total
VM: 2147352576, free: 1933049856
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 20/05/2014 02:46:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-25802-01.dmp
This was probably caused by the following module: clfs.sys (CLFS+0x4B82E)
Bugcheck code: 0xD1 (0xFFFFFA7FF7CA20BD, 0x2, 0x1, 0xFFFFF88000CAE82E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\clfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Common Log File System Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 20/05/2014 02:00:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-21871-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFFA8060960090, 0x2, 0x1, 0xFFFFF80002C8E5EF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 20/05/2014 01:27:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052014-21855-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20E2F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004987E2F, 0xFFFFF880025D7568, 0xFFFFF880025D6DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread 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 19/05/2014 21:01:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-27393-01.dmp
This was probably caused by the following module: avgtdia.sys (0xFFFFF88004518F20)
Bugcheck code: 0xD1 (0xFFFFFA80C03EFA40, 0x2, 0x0, 0xFFFFF88004518F20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\avgtdia.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Network connection watcher
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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. It is suggested you look for an update for the following driver: avgtdia.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 19/05/2014 05:30:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-26769-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0xFFFFF80006000000, 0x2, 0x0, 0xFFFFF80002E0B6FB)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid memory at a process IRQL that was too high.
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.
On Mon 19/05/2014 04:01:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-27440-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x76378)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000106378, 0xFFFFF88007FA6F60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 19/05/2014 03:00:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051914-27050-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5705D)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF8800165805D)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 18/05/2014 21:50:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-29546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF880066F0240, 0xFFFFF880096F0240, 0xFFFFF880006F0240)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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.
On Sat 17/05/2014 20:21:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-31527-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x384D8)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C9A4D8, 0xFFFFF880025D6988, 0xFFFFF880025D61E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 17/05/2014 03:11:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-28610-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x162A72)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8801124CA72, 0xFFFFF880025D6C68, 0xFFFFF880025D64C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 335.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 335.23
Bug check description: This indicates that a system thread 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. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
if someone or anyone could take the time to suggest different things I should do to narrow down the possible causes for this error I'd be so thankful because it really could be anything!
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
10 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation)
avgtdia.sys (AVG Network connection watcher, AVG Technologies CZ, s.r.o.)
Facebook
Twitter
Instagram