[Alan1998]

I do not believe this to be malware related, as I had my system checked about 10 days ago about Essexboy (Martin) on the Avast! Webforums.

 

You can find the Thread Here.

 

I am still running an M$ only Services (Load-up) only. No secondary services except Communications (Atheros), which is apart of my Bluetooth drivers. So I can't just end it.

 

Now, for a while, that solved things, everything returned to normal. Threw the system under the bus by loading BF4 Ultra Setting @ 1080p using a 760. No issues there except some dips to low 40's, but averaging 55+. Now, it has returned.

 

</p>
<p><b>On Thu 2015-04-23 8:08:02 PM GMT your computer crashed</b>
crash dump file: C:\WINDOWS\Minidump\042315-72171-01.dmp
This was probably caused by the following module: <a data-ipb='nomediaparse' href='http://www.google.com/search?q=ntoskrnl.exe'>ntoskrnl.exe</a> (nt+0x150CA0)
Bugcheck code: 0x1A (0x61940, 0xD8E31A3000, 0x63FF000020E01B4, 0x0)
Error: <a data-ipb='nomediaparse' href='http://www.google.com/search?q=MSDN+bugcheck+MEMORY_MANAGEMENT'>MEMORY_MANAGEMENT</a>
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: <a data-ipb='nomediaparse' href='http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System'>Microsoft® Windows® Operating System</a>
company: <a data-ipb='nomediaparse' href='http://www.google.com/search?q=Microsoft%20Corporation'>Microsoft Corporation</a>
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. <b>On Thu 2015-04-23 8:08:02 PM GMT your computer crashed</b>
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: <a data-ipb='nomediaparse' href='http://www.google.com/search?q=ntkrnlmp.exe'>ntkrnlmp.exe</a> (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61940, 0xD8E31A3000, 0x63FF000020E01B4, 0x0)
Error: <a data-ipb='nomediaparse' href='http://www.google.com/search?q=MSDN+bugcheck+MEMORY_MANAGEMENT'>MEMORY_MANAGEMENT</a>
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.</p>
<p>

 

This is from WhoCrashed. I'm at a loss now, and I can only think of Hardware issues now :-(.

 

As for Speccy, well, it's conveniently stopped functioning.

Any ideas?

 

[Advertisements]

Boot to normal mode with "I am still running an M$ only Services (Load-up) only." and try verifying the drivers described in this link. I have not done the steps in the link before or had to perform them. This should help you pinpoint the driver issue you are having.

 

 

http://answers.micro...b3-c48669e4c983

[GooSeSmith]

Boot to normal mode with "I am still running an M$ only Services (Load-up) only." and try verifying the drivers described in this link. I have not done the steps in the link before or had to perform them. This should help you pinpoint the driver issue you are having.

 

 

http://answers.micro...b3-c48669e4c983

[Alan1998]

I will give this a shot when I get home and have time. Thank you :-)