bsod Constent BSODs on Windows 10

[AMDFerTehWin]

every since getting my new cpu(AMD Pheonom ii x4 945) i have been getting almost constant BSODs my specs are as follows....

 

What WhoCrashed Says : Computer name: DESKTOP-BRGQB20
                                               Windows version: Windows 10 , 10.0, build: 14393
                                               Windows dir: C:\Windows
                                               Hardware: ASUSTeK Computer INC., M3N72-D
                                               CPU: AuthenticAMD AMD Phenom(tm) II X4 945 Processor AMD586, level: 16
                                               4 logical processors, active mask: 15
                                               RAM: 8588279808 bytes total

 

What I Say : AMD Phenom II X4 945

                    ASUS M3N72-D mobo

                    EVGA Geforce GTX770 SC

                    8GB OCZ RAM

                    128 GB Samsung SSD

                    Many Many Storage Drives

 

Here is A Copy/Paste of the Past 5 Crash Dumps

 

 

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 2/11/2017 5:39:23 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-146296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8025FC6BC0C, 0xFFFFDE812A25AF70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2/11/2017 2:51:15 PM your computer crashed
crash dump file: C:\Windows\Minidump\021117-138609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xC1 (0xFFFFBD8819C34FC0, 0xFFFFBD8819C34A88, 0x774040, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 driver wrote to an invalid section of the special pool.
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 2/11/2017 10:27:53 AM your computer crashed
crash dump file: C:\Windows\Minidump\021117-139328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xF7 (0x16002F5694A0, 0xADB1CC7A8DC6, 0xFFFF524E33857239, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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 Fri 2/10/2017 5:47:55 PM your computer crashed
crash dump file: C:\Windows\Minidump\021017-232718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xF7 (0x7B81D06903C0, 0x20A5791F401B, 0xFFFFDF5A86E0BFE4, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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 Thu 2/9/2017 6:46:46 PM your computer crashed
crash dump file: C:\Windows\Minidump\020917-208781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.

 

 

[Master Disaster]

Almost certainly bad ram. Run memtest for at least one full pass

[AMDFerTehWin]

1 minute ago, Master Disaster said:

Almost certainly bad ram. Run memtest for at least one full pass

how does one "memtest"

[Sauron]

Well,

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).

I suggest you monitor your cpu temperature, phenoms don't like anything above 64C. It could also be busted ram, although it's less likely if this started happening only when you changed your cpu.

[Sauron]

1 minute ago, AMDFerTehWin said:

how does one "memtest"

http://www.memtest86.com/

 

boot from the live image and run the fill test 3-4 times

[Master Disaster]

1 minute ago, AMDFerTehWin said:

how does one "memtest"

http://www.memtest86.com

 

Download, use Rufus to make a bootable USB, boot from the drive and run the test.

[AMDFerTehWin]

2 minutes ago, Master Disaster said:

http://www.memtest86.com

 

Download, use Rufus to make a bootable USB, boot from the drive and run the test.

will do

[ElZamo92]

Try reseating you memory. It worked for me when I had the same problem a couple of months ago.

[AMDFerTehWin]

4 minutes ago, Sauron said:

Well,

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).

I suggest you monitor your cpu temperature, phenoms don't like anything above 64C. It could also be busted ram, although it's less likely if this started happening only when you changed your cpu.

my cpu temp is usaly 40c idle and sometimes 50c when gaming 

[AMDFerTehWin]

2 minutes ago, ElZamo92 said:

Try reseating you memory. It worked for me when I had the same problem a couple of months ago.

shout i do it before or after memetest?

[ElZamo92]

1 minute ago, AMDFerTehWin said:

shout i do it before or after memetest?

Try it if the memtest turns out OK

[AMDFerTehWin]

1 minute ago, ElZamo92 said:

Try it if the memtest turns out OK

ok

[AMDFerTehWin]

16 minutes ago, Master Disaster said:

Almost certainly bad ram. Run memtest for at least one full pass

 

[AMDFerTehWin]

1 hour ago, ElZamo92 said:

Try it if the memtest turns out OK

 

[AMDFerTehWin]

2 hours ago, Master Disaster said:

Almost certainly bad ram. Run memtest for at least one full pass

Looks to be your right will mark as answer if no more BSODs

[ElZamo92]

It says your memoty is fine, so try reseating you dims. Also try putting them in different slots. Just be sure that the slots you choose are capable of running your memory on dual channels.