BSOD on a nearly new computer

That's OK, I just wondered if it was enabled. It obviously isn't if you don't know about it. Carry on as per mate and I'll ask the BSOD Team to drop by and take a look to see if I'm missing anything. I'm 99% certain this is a driver causing the issue but a fresh set of eyes may see something different.

hello, Nick. Boozad has pretty much covered all the bases. What brand SSD do you have. Could you check and make sure your Firmware is up to date and if you have a tool box, see if you can determine it's health. If you have benchmarked it before, try to run the same tests again and see if there is a drastic difference. Ther will be some minor differences, it is drastic ones we are concerned with.

If you would, could you run these online scanners

Scan with Kaspersky TDSSKiller:
Anti-rootkit utility TDSSKiller
Anti-rootkit utility TDSSKiller
ESET online scanner:
Free Virus Scan | Online Virus Scanner from ESET
Free Online Virus Scanner | ESET

If you have any Gigabytes Utilities installed, uninstall every one of them. They are known causes of BSODs.

Thanks for dropping Steve, much appreciated as usual mucca.

I don't know how much help I can be. You covered the bases pretty well.

It's a baffling one Steve, if it wasn't for the MemTest86+ results I'd be calling a RAM problem nailed on. Everything seems to be pointing towards a driver but I'm buggered if it will show its head.

Nick at the moment I'm of the mind that a clean install of Windows would more than likely solve the issue. I'm as sure as I can be that it's definitely not hardware related but finding out the offending software/driver is proving really difficult. If you do decide to go down that route let us know and we'll help you all you need.

I can't check the latest dump just yet as I'm on my phone but I'll take a look later.

Nick, I looked at your dump file and found this

Code:

Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 0, fffff88001a89a0a}
Probably caused by : tcpip.sys ( tcpip!TtFireTimerEx+e3 )
Followup: MachineOwner

In further looking, I also found these errors blamed

Code:

fffff880`035a69b8  fffff880`08236318Unable to load image mbam.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mbam.sys
*** ERROR: Module load completed but symbols could not be loaded for mbam.sys
 mbam+0x5318

That is Malwarebytes

Code:

fffff880`035a6098  fffff880`00de1000*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
 MpFilter+0x27000

That is a Windows Update, but it is also Microsoft Windows AntiMalware protection system.

Code:

fffff880`035a5af0  fffff880`04a52481Unable to load image bflwfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bflwfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for bflwfx64.sys
 bflwfx64+0x2481

That is your Bigfoot Networks Bandwidth Control Wireless NDIS Light Weight Filter driver

I do find it curious that 2 of the 3 mentioned were anti virus/Malware related.

I would suggest you run these online scanners

Scan with Kaspersky TDSSKiller:
Anti-rootkit utility TDSSKiller
Anti-rootkit utility TDSSKiller
ESET online scanner:
Free Virus Scan | Online Virus Scanner from ESET
Free Online Virus Scanner | ESET

Also, please download and run a full scan with Superantispyware SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
It is a free program and does a very good job with adware/tracking/malware programs we all get from cruising the net, as long as you can tolerate their nag popups. I use it often as an on demand scanner.

I would think if you are going to do a clean install, it would be best if you can find any Viruses/rootkits or other such programs first. Some have been known to live through a clean install.

When you get ready do a clean install, let us know and Boozad or I will guide you through it and give you a good tutorial. If you have any questions at all, feel free to ask. We don't mind a bit.