Windows 8.1 bsod problems mainly MEMORY_MANAGEMENT help!

[MasterChief]

It's in the RTWLANU_Driver folder you extracted to. Probably also inside another folder in there like "x64" or similar.

But anyway, nevermind that. Forget it. I got it wrong (or link I researched told me wrong.)

You have 8192CU and already have the latest driver.

Realtek says it is compatible with 8 - but they don't say about 8.1.

Suggest 2 things:

1) Leave wireless adapter out of machine to see how it goes.

2) If good after a day or so - or if you just want to try now instead - take the x64 .sys you downloaded already and put it in C:\Windows\System32\drivers folder.

Rename the original to .bak first.

Reboot after. Test it out to see if it works.

 

[pork]

thanks downloading now

 

[MasterChief]

No, no you already have it on your drive as per the screenshots.

 

[pork]

ok but do i need to uninstall the current drives before i put the new ones in that folder

 

[pork]

i had another memory management bsod ill atach the latest dump

 

[MasterChief]

667 MHz 9-9-9-24 timings. Set RAM like that, as said a while ago. Don't bother asking how because I don't have that motherboard to say about.

Run chkdsk /r command from elevated command prompt.

 

[pork]

hi master chief ive ran chkdsk /r

but confusingly the lowest frequency i can set my ram is 800 take a look

View attachment 37561

 

[MasterChief]

You want 1333 MHz to set there. That = 667 MHz in Windows CPU-Z screen.

 

[pork]

ohhhhhhhhh k thanks

 

[pork]

ok but do i need to uninstall the current drivers before i put the new ones in that folder

 

[pork]

Omg the drivers worked in that folder !! Ill get back to here if i have another bsod

 

[pork]

hi master i am sad to say it but i had another bsod

heres the new grab all

 

[MasterChief]

hi master i am sad to say it but i had another bsod

heres the new grab all

It's NTFS related. That either means your RAM is still acting up (we can't say just by one crash) - OR - from all the crashes you've had, there's some corruption of the hard drive.

So, for every hard drive (partition, really) - run this command from an elevated command prompt. Change the letter C to match for each partition, each time:

chkdsk /r C:

I also suggest to post a new screenshot of the CPU-Z Memory tab so we can see how that is looking. Just to verify etc...

I am leaning towards it being corruption on the hard drive needing to be fixed now, because it crashed during a scan (the NTFS file system, I mean.) And, you had numerous crashes per day before. Now it's not nearly as often.

But yep - CPU-Z and command(s).

STACK_TEXT:  
ffffd000`29d06e38 fffff802`5b3870d8 : 00000000`0000004e 00000000`00000002 00000000`000b089b 00000000`0013efff : nt!KeBugCheckEx
ffffd000`29d06e40 fffff802`5b2888cf : ffffc000`0c925010 ffffc000`0c925011 ffffd000`29d06fd0 ffffc000`0c925010 : nt! ?? ::FNODOBFM::`string'+0x1af38
ffffd000`29d06ed0 fffff802`5b289482 : 00000000`00000000 00000000`00000000 00000000`00000001 ffffd000`29d07328 : nt!MiFlushSectionInternal+0x31b
ffffd000`29d070e0 fffff802`5b28d608 : ffffe000`00b7ccc8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmFlushSection+0x1a2
ffffd000`29d071a0 fffff802`5b310f29 : ffffe000`0613a9d8 00000000`00000000 ffffe000`00000000 00000000`00000000 : nt!CcFlushCachePriv+0x6c0
ffffd000`29d072b0 fffff800`00911c38 : ffffe000`00b7ccc8 ffffd000`29d07730 00000000`00000001 ffffc000`0c493a50 : nt!CcFlushCache+0x11
ffffd000`29d072f0 fffff800`0097678e : ffffe000`00b7ccc8 ffffc000`0c493a50 ffffe000`00b7ccc8 ffffc000`0c38ec12 : Ntfs!NtfsFlushUserStream+0xac
ffffd000`29d07370 fffff800`008922f0 : ffffe000`00b7ccc8 ffffe000`0025b180 ffffe000`05075200 fffff800`008806ff : Ntfs!NtfsFlushVolume+0x3da
ffffd000`29d074c0 fffff800`0088a14b : ffffe000`00b7ccc8 ffffe000`050752d0 ffffe000`01aa52f0 fffff802`5b5b1f01 : Ntfs!NtfsVolumeDasdIo+0x200
ffffd000`29d07560 fffff800`0088babc : ffffe000`00b7ccc8 ffffe000`050752d0 ffffe000`00fe5801 00000000`00000101 : Ntfs!NtfsCommonRead+0x1eab
ffffd000`29d07700 fffff800`00772f3e : ffffe000`047b0d00 ffffe000`050752d0 ffffe000`050752d0 ffffe000`05075670 : Ntfs!NtfsFsdRead+0x1dc
ffffd000`29d077b0 fffff800`00771ae6 : ffffe000`019da180 00000000`00000000 ffffe000`05075201 ffffe000`019da180 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x25e
ffffd000`29d07830 fffff802`5b5b4995 : ffffe000`05075670 ffffd000`29d07b00 00000000`00000000 ffffd000`201e0180 : fltmgr!FltpDispatch+0xb6
ffffd000`29d07890 fffff802`5b3674b3 : ffffe000`058a62c0 000000b9`1c65e5f8 00000000`00000000 ffffc000`00000018 : nt!NtReadFile+0x7d5
ffffd000`29d07a10 00007ffe`b15565da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000b9`1c65e3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`b15565da

 

[MasterChief]

ehhhh /sigh

I just reviewed the original post. I totally forgot that you said you had 32 pieces of malware.

Almost for sure, that (even if removed or still more even present) is probably the most likely cause.

All of your latest crashes are PFN List corrupt:

"Corruption problems can be due to a virus that has worked its way into the vital system files of your computer or it could be due to the fact that your computer’s registry is being affected with corrupt files."

I agree in this case, based on all factors and how you are not getting 0x1A anymore.

Let's see CPU-Z, see how it goes after you run command(s) - but really like I said already - Killdisk then clean install Windows it is going to be.

But anyhow, uninstall: Driver Reference Table - AODDriver2.sys

 

[pork]

ive ran chk dsk for my windows drive and for the partition and heres the memory tab oh and about AODDriver2.sys shall i just delete it ill post its location aswell i dont know what device those drivers are for i dont think i have amd overdrive

View attachment 37751View attachment 37752View attachment 37753

 

[pork]

well thats interesting i just had anothe memorymanagement bsod

see atttachedView attachment 37755

 

[MasterChief]

grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr

I mean that as in lol.

I already told you that 5-5-5 is crazy!!!

9-9-9-24

"To fix your issue, set the RAM in your bios for 9-9-9-24 timings instead of the crazy 5-5-5-15 it is at now. Probably best to set bios to Optimized Defaults then save."

When you do that, make sure MHz does not change from 667 MHz.

 

[pork]

what do these correspond ? i didnt change anything ?


View attachment 37771

 

[pork]

i had another memory management bsod

 

[pork]

updated