I keep getting BSODs

[deadmoo5e]

I can not figure out why I'm getting these crashes. Doesn't seem to be a single thing or program I run that triggers it. Just that it can take between 1-5 hours between bootup until my machine crashes.

 

I'm attaching the latest .dmp file in this dump. I'm not computer savy enough to analyse it myself. I have run memtest86+ for 24 hours with several passes so I'm confident my memory is not at fault here.

 

I'll appreciate any help 

 

My hardware

 

CPU Intel i7 4770k
Motherboard Asus Maximus VI Formula
RAM Corsair Dominator Platinum 16GB 1866MHz
GPU Asus Radeon R9 Fury Strix
Case Fractal Design R5
Storage OCZ Vertex 4 256GB
PSU Corsair AX 750

WLAN Asus PCE-AC68
Display BenQ XL2420Z
Cooling Corsair H100i
Keyboard Logitech G710+
Mouse Logitech G400

Operating System  Windows 10 Home

 

 

100616-5890-01.rar

[deadmoo5e]

Just now, Wedsea040 said:

What blue screen code do you get when it appears?

PAGE_FAULT_IN_NONPAGED_AREA

[TeeTwo]

Do you perhaps have an E: drive?

Just a question to measure the validity of the dump info.

[tikker]

Did you try just one RAM stick as well? I know you said it passed memtest, but it may be worth trying.

[deadmoo5e]

4 minutes ago, TeeTwo said:

Do you perhaps have an E: drive?

Just a question to measure the validity of the dump info.

I do have an WD E drive yes

3 minutes ago, tikker said:

Did you try just one RAM stick as well? I know you said it passed memtest, but it may be worth trying.

 

Yeah all four at once and all four individually

[TeeTwo]

Just now, deadmoo5e said:

I do have an WD E drive yes

 

Yeah all four at once and all four individually

Then my conclusion of the .dmp info is: SOMETHING is corrupting the data on your RAM, and/or failure to access a certain driver or file that is supposed to be on the E: drive called modclass.ini (located in e:\dump_analysis\program\triage\modclass.ini).

Perhaps that file is screwing things up, or your sticks or slots are actually defect and they just dont fuck up during memtest.

Anyway, heres the info i found:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffff8c80006f56d8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80210ae6d02, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffff8c80006f56d8 

FAULTING_IP: 
nt!MmBuildMdlForNonPagedPool+312
fffff802`10ae6d02 498b00          mov     rax,qword ptr [r8]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  ffff970181e865d0 -- (.trap 0xffff970181e865d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe48000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=ffff8cc640000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80210ae6d02 rsp=ffff970181e86760 rbp=ffff970181e86780
 r8=ffff8c80006f56d8  r9=ffffe48253400000 r10=00000000deadb000
r11=0000100000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!MmBuildMdlForNonPagedPool+0x312:
fffff802`10ae6d02 498b00          mov     rax,qword ptr [r8] ds:ffff8c80`006f56d8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80210b916ca to fffff80210b5c2b0

STACK_TEXT:  
ffff9701`81e862d8 fffff802`10b916ca : 00000000`00000050 ffff8c80`006f56d8 00000000`00000000 ffff9701`81e865d0 : nt!KeBugCheckEx
ffff9701`81e862e0 fffff802`10a82ffa : 00000000`00000000 00000000`00000000 ffff9701`81e865d0 fffff802`10ad941a : nt! ?? ::FNODOBFM::`string'+0x2623a
ffff9701`81e863d0 fffff802`10b658fc : ffffe482`52480000 ffffe482`50139000 00000000`00000000 ffffe482`53400000 : nt!MmAccessFault+0x9ca
ffff9701`81e865d0 fffff802`10ae6d02 : ffffe482`4d91d010 fffff806`19f167fc 00000000`00000001 ffffe482`4d91d010 : nt!KiPageFault+0x13c
ffff9701`81e86760 fffff806`18b1f891 : ffffe482`4d8c8000 ffffe482`53400000 ffffe482`4d8c8000 00000000`6f3c4891 : nt!MmBuildMdlForNonPagedPool+0x312
ffff9701`81e867f0 fffff806`19ee1d1f : ffffe482`4db385f8 ffffe482`50ddaa70 ffffe482`4deb3000 ffffe482`4d8c8000 : ndis!NdisAllocateMdl+0x31
ffff9701`81e86830 ffffe482`4db385f8 : ffffe482`50ddaa70 ffffe482`4deb3000 ffffe482`4d8c8000 00000000`00000176 : bcmwl63a+0xe1d1f
ffff9701`81e86838 ffffe482`50ddaa70 : ffffe482`4deb3000 ffffe482`4d8c8000 00000000`00000176 fffff806`19ec413c : 0xffffe482`4db385f8
ffff9701`81e86840 ffffe482`4deb3000 : ffffe482`4d8c8000 00000000`00000176 fffff806`19ec413c ffffe482`4d84ba30 : 0xffffe482`50ddaa70
ffff9701`81e86848 ffffe482`4d8c8000 : 00000000`00000176 fffff806`19ec413c ffffe482`4d84ba30 ffffe482`4dea0780 : 0xffffe482`4deb3000
ffff9701`81e86850 00000000`00000176 : fffff806`19ec413c ffffe482`4d84ba30 ffffe482`4dea0780 00000000`000000bb : 0xffffe482`4d8c8000
ffff9701`81e86858 fffff806`19ec413c : ffffe482`4d84ba30 ffffe482`4dea0780 00000000`000000bb ffffe482`4d84ba30 : 0x176
ffff9701`81e86860 ffffe482`4d84ba30 : ffffe482`4dea0780 00000000`000000bb ffffe482`4d84ba30 ffffe482`4f8b5010 : bcmwl63a+0xc413c
ffff9701`81e86868 ffffe482`4dea0780 : 00000000`000000bb ffffe482`4d84ba30 ffffe482`4f8b5010 fffff806`19f4fb3b : 0xffffe482`4d84ba30
ffff9701`81e86870 00000000`000000bb : ffffe482`4d84ba30 ffffe482`4f8b5010 fffff806`19f4fb3b 00000001`1000acf0 : 0xffffe482`4dea0780
ffff9701`81e86878 ffffe482`4d84ba30 : ffffe482`4f8b5010 fffff806`19f4fb3b 00000001`1000acf0 ffffe482`4f8b5000 : 0xbb
ffff9701`81e86880 ffffe482`4f8b5010 : fffff806`19f4fb3b 00000001`1000acf0 ffffe482`4f8b5000 ffff01ea`c56f1421 : 0xffffe482`4d84ba30
ffff9701`81e86888 fffff806`19f4fb3b : 00000001`1000acf0 ffffe482`4f8b5000 ffff01ea`c56f1421 fffff806`19f15e32 : 0xffffe482`4f8b5010
ffff9701`81e86890 00000001`1000acf0 : ffffe482`4f8b5000 ffff01ea`c56f1421 fffff806`19f15e32 00000000`00000000 : bcmwl63a+0x14fb3b
ffff9701`81e86898 ffffe482`4f8b5000 : ffff01ea`c56f1421 fffff806`19f15e32 00000000`00000000 00000000`00000000 : 0x1`1000acf0
ffff9701`81e868a0 ffff01ea`c56f1421 : fffff806`19f15e32 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe482`4f8b5000
ffff9701`81e868a8 fffff806`19f15e32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff01ea`c56f1421
ffff9701`81e868b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : bcmwl63a+0x115e32


STACK_COMMAND:  kb

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

[deadmoo5e]

2 hours ago, TeeTwo said:

Then my conclusion of the .dmp info is: SOMETHING is corrupting the data on your RAM, and/or failure to access a certain driver or file that is supposed to be on the E: drive called modclass.ini (located in e:\dump_analysis\program\triage\modclass.ini).

Perhaps that file is screwing things up, or your sticks or slots are actually defect and they just dont fuck up during memtest.

Anyway, heres the info i found:

That's pretty comprehensive.  I'll see if I can't reformat that E Drive and see if that helps. Maybe disconnect it.

 

I'm still pretty sure it's not the memory given the thorough testing. And I borrowed a stick from a friend of mine and I still got the BSOD.

 

Again thanks a lot for looking at it for me. 

[TeeTwo]

18 minutes ago, deadmoo5e said:

That's pretty comprehensive.  I'll see if I can't reformat that E Drive and see if that helps. Maybe disconnect it.

 

I'm still pretty sure it's not the memory given the thorough testing. And I borrowed a stick from a friend of mine and I still got the BSOD.

 

Again thanks a lot for looking at it for me. 

No problem. Do look into a complete reformat of your system to ensure that the file system end up as pure as possible imo, just remember to save important data. If issues continue, try using a different mobo. Maybe a slots traces going bad. Good luck fixing the issue tho, my signature kinda reminds me of how ridiculous issues can be sometimes.

[deadmoo5e]

Just now, TeeTwo said:

No problem. Do look into a complete reformat of your system to ensure that the file system end up as pure as possible imo, just remember to save important data. If issues continue, try using a different mobo. Maybe a slots traces going bad. Good luck fixing the issue tho, my signature kinda reminds me of how ridiculous issues can be sometimes.

I already tried reverting back to windows 7 and now I'm back again to Windows 10 (clean install). 

 

And I guess good lga 1150 is in short supply these days

[TeeTwo]

1 minute ago, deadmoo5e said:

I already tried reverting back to windows 7 and now I'm back again to Windows 10 (clean install). 

 

And I guess good lga 1150 is in short supply these days

Well, you never know... might work. Give it a try, cant really go any worse now, can it?

And yea, LGA1150 mobos that are usefull barely exist where i am anymore. Theres like 2 mITX mobos available and one is an ASRock workstation/server mobo with ECC support for 300 bucks, the other a really cheap Asus... But to be honest, not alot of fun stuff is available here so your result may vary.

[ObliviationGNx]

are you running torrent...

[deadmoo5e]

On 6.10.2016 at 10:30 PM, TeeTwo said:

Well, you never know... might work. Give it a try, cant really go any worse now, can it?

And yea, LGA1150 mobos that are usefull barely exist where i am anymore. Theres like 2 mITX mobos available and one is an ASRock workstation/server mobo with ECC support for 300 bucks, the other a really cheap Asus... But to be honest, not alot of fun stuff is available here so your result may vary.

Well I went on another forum with the same issue and they said it was some wlan driver causing it as well. So when I disconnected the PCE-AC68 I didn't get the BSOD for 24 hours (with torrents) . Then I plugged it back in got the BSOD. Now I removed the E drive and it worked for hours. Until I tested with a download in qbittorent and it BSOD'ed after two minutes. Tested the PCE-AC68 in different slots and still BSODs.

 

Looks like I either have to live without the PCE or spring for a new motherboard. 

[TeeTwo]

On 2016-10-08 at 2:27 AM, deadmoo5e said:

Well I went on another forum with the same issue and they said it was some wlan driver causing it as well. So when I disconnected the PCE-AC68 I didn't get the BSOD for 24 hours (with torrents) . Then I plugged it back in got the BSOD. Now I removed the E drive and it worked for hours. Until I tested with a download in qbittorent and it BSOD'ed after two minutes. Tested the PCE-AC68 in different slots and still BSODs.

 

Looks like I either have to live without the PCE or spring for a new motherboard. 

id suggest to live without the PCE. You should be able to use a usb wifi stick or the ethernet port on your mobo.  That, or if you truly value your internet speed then you should go for a new mobo.

[deadmoo5e]

On 10.10.2016 at 2:51 PM, TeeTwo said:

id suggest to live without the PCE. You should be able to use a usb wifi stick or the ethernet port on your mobo.  That, or if you truly value your internet speed then you should go for a new mobo.

Looks like I have to RMA this one and spring for a new one. Now I'm starting to get video driver crashes immediately accompanied with BSODs every few hours.