Windows 10: Memory_management bsod

First BSOD after a while of running fine. This is a new build PC with a clean install of Windows 10. It crashed a lot after installation, then settled down.

Today, I'm running a download installer for 9.5GBytes of graphics applications and data. At the sime time, I started using Firefox. BSOD!

Attached is the dm_log_collector file.

Attachment 59087

:)

 

MEMORY_MANAGEMENT,PFN_LIST_CORRUPT,BAD_POOL_HEADER BSODs on Windows 10 while gaming or just using my PC.

Any news on this?

I am still getting MEMORY_MANAGEMENT BSODs

 

Lots of BSOD's

PS: after my previous/last replie i had 3 more BSOD's:

seems like there are a lot of random once...

MEMORY_MANAGEMENT win32kbase.sys

MEMORY_MANAGEMENT ntoskrnl.exe

ntoskrnl.exe

 

Warning Programs that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Talent, please remove them as it may cause trouble.

Please uninstall Webroot ScureAnywhere and use Windows Defender as alternative
Unfortunately, I couldn't find any proper instructions or tool to remove it.
Code: ffffd000`22c26628 fffff801`79feb33bUnable to load image \SystemRoot\System32\drivers\WRkrn.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for WRkrn.sys *** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys WRkrn+0xb33b[/quote]

 

Another crash: DRIVER_IRQL_NOT_LESS_OR_EQ in NETIO.SYS

Attachment 59490

Why did you suggest removing Webroot, a virus checker?

Pete

 

The code below means a driver has been flagged, in this case it was a driver from Webroot that caused instability.
It is best to uninstall it and use Windows Defender as alternative to make sure Webroot won't be causing problems while troubleshooting.
Code: *** WARNING: Unable to verify timestamp for WRkrn.sys *** ERROR: Module load completed but symbols could not be loaded for WRkrn.sys[/quote] In this part you can see that the Network Input/Output System driver (netio) was blamed.
Code: Probably caused by : hardware ( NETIO!KfdClassify2+1cc )[/quote] I only see network (related) drivers, with 'hardware' as probable cause it could mean the network card has been damaged.
The only way I know to test if the network card is causing problems is by updating the network drivers and see if that helps.
Driver Reference Table - rt640x64.sys
Code: 2: kd> k Child-SP RetAddr Call Site ffffd000`2318bb78 fffff802`24d4e2e9 nt!KeBugCheckEx ffffd000`2318bb80 fffff802`24d4cac7 nt!KiBugCheckDispatch+0x69 ffffd000`2318bcc0 fffff801`1416269c nt!KiPageFault+0x247 ffffd000`2318be50 fffff801`1360046c NETIO!KfdClassify2+0x1cc ffffd000`2318bf20 fffff801`135d20a2 tcpip!WfpTlShimInspectRecvTcpDatagram+0x1fc ffffd000`2318c140 fffff801`135cf469 tcpip!InetInspectReceiveTcpDatagram+0x262 ffffd000`2318c250 fffff801`135cea2b tcpip!TcpTcbReceive+0x1a9 ffffd000`2318c4a0 fffff801`135ce475 tcpip!TcpMatchReceive+0x1fb ffffd000`2318c750 fffff801`136021fe tcpip!TcpPreValidatedReceive+0x385 ffffd000`2318c840 fffff801`13601f3e tcpip!IppLoopbackIndicatePackets+0x9a ffffd000`2318c8c0 fffff802`24c76b35 tcpip!IppLoopbackTransmitCalloutRoutine+0x10e ffffd000`2318c930 fffff801`135c74ff nt!KeExpandKernelStackAndCalloutInternal+0x85 ffffd000`2318c980 fffff801`135c81e0 tcpip!IpNlpFastContinueSendDatagram+0xa5f ffffd000`2318ca80 fffff801`135c69ab tcpip!IppSendDatagramsCommon+0x790 ffffd000`2318cc80 fffff801`135d986e tcpip!IpNlpFastSendDatagram+0x38b ffffd000`2318cd60 fffff801`135d8ff5 tcpip!TcpTcbSend+0x7ae ffffd000`2318d0a0 fffff801`135d8c8e tcpip!TcpEnqueueTcbSendOlmNotifySendComplete+0xa5 ffffd000`2318d0d0 fffff801`135d87db tcpip!TcpEnqueueTcbSend+0x2fe ffffd000`2318d1d0 fffff802`24c76b35 tcpip!TcpTlConnectionSendCalloutRoutine+0x2b ffffd000`2318d250 fffff801`135fcb16 nt!KeExpandKernelStackAndCalloutInternal+0x85 ffffd000`2318d2a0 fffff801`1470d7d7 tcpip!TcpTlConnectionSend+0x76 ffffd000`2318d310 fffff801`146eeecd afd!AfdFastConnectionSend+0x387 ffffd000`2318d4d0 fffff802`24fe94d0 afd!AfdFastIoDeviceControl+0x89d ffffd000`2318d850 fffff802`24fe8c76 nt!IopXxxControlFile+0x850 ffffd000`2318da20 fffff802`24d4dfa3 nt!NtDeviceIoControlFile+0x56 ffffd000`2318da90 00007ff9`d16d4ec4 nt!KiSystemServiceCopyEnd+0x13 000000d8`9abfecd8 00000000`00000000 0x00007ff9`d16d4ec4[/quote]

 

The 'network card' is the motherboard. I do have a spare DLine network card I could try instead of the onboard one.

 

Try it , ruling out the current NIC immediately *Smile

 

System crashed, then had one of my drives start clicking, like the disk drive click-of-death. Thinking it was the new 3TB drive, I removed it, put it on an external USB adapter and it was working fine. Now I'm not sure which drive was clicking.

Running HDTune and looking at SMART details both the old 750GByte drive and the new 3TB drive were fine. Not tried any stress tests on either yet.

I don't have the crash details to post at the moment.

 

Try running following tests on all your hard drives





Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

• Short Drive Self Test
• Short generic
• Long generic

If the short generic fails, no need for the long generic.


Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk
Disk Check - Windows 7 Help Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

 

More crashes, not had a chance to try another network card.

Attachment 61292

 

I switched to the DLink network card today.

Shortly afterwards, another crash - NTFS.SYS

Attachment 61358

 

Did you already run the hard drive tests?

 

Not yet, will try later today

 

The smaller Samsung drive failed the long generic test; I ran chkdsk and found it detected bad blocks. Would this be the cause of crashing?