New computer build multiple BSOD (MEMORY_MANAGEMENT, and others)

eforen · 09 Apr 2017

I have been having lots of seemingly random BSOD with this new computer build and can't nail it down.

I have had it BSOD on my while playing games, Adjusting Sound Settings in VoiceMeter Banana, Working in Logisim as well as several other situations I do not remember them all its been a while.

Equipment:

Oculus VR with Touch Controllers
3 Oculus VR Sensors
XBox One Controller Wireless adapter
Audio-Technica AT2020 Running via a Focusrite Solo 2nd Gen
Standard Dell Keyboard (USB)
Some Kinda G10 Mechanical Gaming mouse from china
Dymo LabelWriter 4XL
Wacom Bamboo

What I have tried:

Ran Check Disk and found errors so Replaced Primary Drive (SSD) with New HDD
Reinstalling multiple times
Memory Check but I could not find the log about it in event log and have not had time to run it again as i have 64GB of RAM it takes a bit...
I have unplugged my Focusrite Solo because that seemed to be aggravating the problems. The mic output would start to have a lot of static and it would get fixed for a bit if I unplugged it and plugged it back in but when I turned on driver verifyer it would BSOD immediately if I unplugged it in that state. This has helped but I still get the BSODs I just don't get them as often.
Turned on driver Verification

BSOD messages:

MEMORY_MANAGEMENT
CRITICAL_STRUCTURE_CORRUPTION What Failed: cng.sys
PFN_LIST_CORRUPT
KERNEL_SECURITY_CHECK_FAILURE
CRITICAL_PROCESS_DIED
BAD_SYSTEM_CONFIG_INFO
Recently I had another when using Logisim but I cant remember what it was... And didn't get a photo of it.

I have added a folder LastInstall that has the mini dumps from the last install. Attachment 129107
Thank you in advanced for any help you can give.
P.S. Just tried to run some VR last night and it was crazy laggy in the headset total eye desync jitter which is new but I suspect that is due to the Driver Verification slowing things down that run the Oculus Headset... I almost through up in the bathroom from this... not fun when you desync I felt for that dude in Assassins Creed after this...

Xilnik · 10 Apr 2017

Code:

Start Menu\Programs\Driver Easy	Public:Start Menu\Programs\Driver Easy

Driver update tools do not always install stable drivers and often install drivers meant for other systems. You are much better off getting your drivers from your device manufacturers or from your motherboard manufacturer.

Code:

*** WARNING: Unable to verify timestamp for MBAMChameleon.sys 
*** ERROR: Module load completed but symbols could not be loaded for MBAMChameleon.sys 
0xffff9a01`f6dc92d8  0xfffff805`21a1a67e MBAMChameleon!+0xa67e

What version of Malwarebytes are you using? I am seeing it in your crash stack quite a bit, which is unusual since it is not known to cause crashes like these. I would suspect bad memory being accessed by Malwarebytes over Malwarebytes itself unless you are running a very old version of the software on Windows 10.

Code:

Debug session time: Mon Apr  3 21:05:38.906 2017 (UTC - 6:00)
Loading Dump File [F:\SysnativeBSODApps\Troubleshooting\TenForums\eforen\040317-36625-01.dmp]
Built by: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
System Uptime: 0 days 18:12:19.681
*** WARNING: Unable to verify timestamp for e1d65x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1d65x64.sys
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+f4 )
BugCheck C1, {ffff818414c04c40, ffff818414c0485a, eb43b8, 32}
BugCheck Info: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Bugcheck code 000000c1
Arguments: 
Arg1: ffff818414c04c40, address trying to free
Arg2: ffff818414c0485a, address where one bit is corrupted
Arg3: 0000000000eb43b8, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
BUGCHECK_STR:  0xC1_32
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xC1_32_NETIO!NetioDereferenceNetBufferListChain
MaxSpeed:     3500
CurrentSpeed: 3504
BiosVersion = 1.04
BiosReleaseDate = 08/02/2016
SystemManufacturer = EVGA INTERNATIONAL CO.,LTD
SystemProductName = Default string
BaseBoardProduct = 142-SS-E178

Your Intel network drivers are showing up in the stack and are even blamed in a few crashes. Make sure you either update/rollback the driver from Intel or from EVGA (preferably your motherboard manufacturer - EVGA - to test stability, but check if stability is better with the Intel version, too).

As for testing your RAM, you should test it with more of a brute force method at 64 GB. After disabling Verifier in a day or two (avoid using your VR headset if it makes you sick with Verifier enabled), remove half your RAM, test for a few days by doing your normal routine in Windows with that half, and then swap that half with the other half to test again with your normal Windows routine with only 32 GB. See if you can narrow down which module(s) is (are) bad by running with only one module at a time while doing your normal Windows routine.

eforen · 10 Apr 2017

Xilnik said:

Code:

Start Menu\Programs\Driver Easy    Public:Start Menu\Programs\Driver Easy

Driver update tools do not always install stable drivers and often install drivers meant for other systems. You are much better off getting your drivers from your device manufacturers or from your motherboard manufacturer.

I do not allow Driver Easy to actually touch my drivers I just use it as a driver scan to let me know what drivers I need to look into and then I go and find the correct driver my self but it lets me know if a driver is out of day or whatever.

Xilnik said:

Code:

*** WARNING: Unable to verify timestamp for MBAMChameleon.sys 
*** ERROR: Module load completed but symbols could not be loaded for MBAMChameleon.sys 
0xffff9a01`f6dc92d8  0xfffff805`21a1a67e MBAMChameleon!+0xa67e

What version of Malwarebytes are you using? I am seeing it in your crash stack quite a bit, which is unusual since it is not known to cause crashes like these. I would suspect bad memory being accessed by Malwarebytes over Malwarebytes itself unless you are running a very old version of the software on Windows 10.

I am using Malwarebytes Premium 3.0.6 last updated 15 hours ago

Xilnik said:

Code:

Debug session time: Mon Apr  3 21:05:38.906 2017 (UTC - 6:00)
Loading Dump File [F:\SysnativeBSODApps\Troubleshooting\TenForums\eforen\040317-36625-01.dmp]
Built by: 14393.953.amd64fre.rs1_release_inmarket.170303-1614
System Uptime: 0 days 18:12:19.681
*** WARNING: Unable to verify timestamp for e1d65x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1d65x64.sys
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+f4 )
BugCheck C1, {ffff818414c04c40, ffff818414c0485a, eb43b8, 32}
BugCheck Info: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Bugcheck code 000000c1
Arguments: 
Arg1: ffff818414c04c40, address trying to free
Arg2: ffff818414c0485a, address where one bit is corrupted
Arg3: 0000000000eb43b8, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
BUGCHECK_STR:  0xC1_32
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xC1_32_NETIO!NetioDereferenceNetBufferListChain
MaxSpeed:     3500
CurrentSpeed: 3504
BiosVersion = 1.04
BiosReleaseDate = 08/02/2016
SystemManufacturer = EVGA INTERNATIONAL CO.,LTD
SystemProductName = Default string
BaseBoardProduct = 142-SS-E178

Your Intel network drivers are showing up in the stack and are even blamed in a few crashes. Make sure you either update/rollback the driver from Intel or from EVGA (preferably your motherboard manufacturer - EVGA - to test stability, but check if stability is better with the Intel version, too).

I have tried to install the drivers from EVGA I will look at them again and see where that goes...

Xilnik said:

As for testing your RAM, you should test it with more of a brute force method at 64 GB. After disabling Verifier in a day or two (avoid using your VR headset if it makes you sick with Verifier enabled), remove half your RAM, test for a few days by doing your normal routine in Windows with that half, and then swap that half with the other half to test again with your normal Windows routine with only 32 GB. See if you can narrow down which module(s) is (are) bad by running with only one module at a time while doing your normal Windows routine.

I was thinking of trying that I may even be able to run it on a single chip I will check my board to see if it supports that and if I can run that low of ram. Point is I will try it out.

Xilnik said:

(avoid using your VR headset if it makes you sick with Verifier enabled)

Oh trust me I am not putting that thing back on until I get this resolved! I like my dinner staying in my belly!