Frequent BSOD memory_management

Thanks for your replies ztrucker and zbook,

Updates:

• Updated display drivers
• Removed Wacom drivers (no longer used anyway)
• Win version 15063.413
• SFC & DISM:

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

• I have already run HDTUNE on all the drives and they all passed (posted 27th May).

• Still to do chkdsk all drives

In the mean time please find my latest BSODs attached in case they offer any other insights.

Attachment 143013

Thanks
George

Updating with the CHKDSK results



Checking file system on C:
The type of the file system is NTFS.
Volume label is WINDOWS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
664320 file records processed. File verification completed.
5198 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
821864 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 697 unused index entries from index $SII of file 0x9.
Cleaning up 697 unused index entries from index $SDH of file 0x9.
Cleaning up 697 unused security descriptors.
Security descriptor verification completed.
78773 data files processed. CHKDSK is verifying Usn Journal...
37603576 USN bytes processed. Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
664304 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
19386140 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

249478143 KB total disk space.
170913504 KB in 409206 files.
241544 KB in 78774 indexes.
0 KB in bad sectors.
778535 KB in use by the system.
65536 KB occupied by the log file.
77544560 KB available on disk.

4096 bytes in each allocation unit.
62369535 total allocation units on disk.
19386140 allocation units available on disk.

Internal Info:
00 23 0a 00 82 71 07 00 cf 2d 0d 00 00 00 00 00 .#...q...-......
1b 04 00 00 21 00 00 00 00 00 00 00 00 00 00 00 ....!...........

Windows has finished checking your disk.
Please wait while your computer restarts.



Checking file system on D:
The type of the file system is NTFS.
Volume label is WD.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
94720 file records processed. File verification completed.
1 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
107662 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.
Security descriptor verification completed.
6471 data files processed.
Stage 4: Looking for bad clusters in user file data ...
94704 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...
82726221 free clusters processed. Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

511999999 KB total disk space.
180900332 KB in 63561 files.
18392 KB in 6473 indexes.
0 KB in bad sectors.
176391 KB in use by the system.
65536 KB occupied by the log file.
330904884 KB available on disk.

4096 bytes in each allocation unit.
127999999 total allocation units on disk.
82726221 allocation units available on disk.

Internal Info:
00 72 01 00 8b 11 01 00 87 11 01 00 00 00 00 00 .r..............
89 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................



E:\>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is WD.

Stage 1: Examining basic file system structure ...
5120 file records processed.
File verification completed.
0 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
6046 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
463 data files processed.

Stage 4: Looking for bad clusters in user file data ...
5104 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
28546316 free clusters processed.
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

255999999 KB total disk space.
141734584 KB in 4166 files.
1256 KB in 465 indexes.
0 KB in bad sectors.
78895 KB in use by the system.
65536 KB occupied by the log file.
114185264 KB available on disk.

4096 bytes in each allocation unit.
63999999 total allocation units on disk.
28546316 allocation units available on disk.

E:\>

Code:

fffff801`cd654638  fffff80b`8eaf1beeUnable to load image nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x111bee

Code:

6 Jul 07:15    Application Error    Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x59079e96
Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.8205, time stamp: 0x59079dd9
Exception code: 0xc0000005
Fault offset: 0x00000000000c1951
Faulting process ID: 0x728
Faulting application start time: 0x01d2f627902f3172
Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe
Faulting module path: NvXDCore.dll
Report ID: 5f7bff7c-3cf6-4d53-aa87-1e1917cef640
Faulting package full name: 
Faulting package-relative application ID:

Code:

nvlddmkm     nvlddmkm               nvlddmkm               Kernel        Manual     Running    OK         TRUE        FALSE        5,832,704         6,443,008   0          8 Jun 00:03:57         C:\WINDOWS\system32\DriverStore\FileRepository\n 36,864

nvlddmkm.sys

nVidia Video drivers

http://www.nvidia.com/Download/index.aspx Get from OEM for laptops

The misbehaving driver is nvlddmkm.sys
This is the Nvidia driver.
Earlier in the thread this driver was replaced.
The driver can be replaced using the Asus web site as a source of computer manufacture approved drivers or can be directly from the Nvidia web site.
Please review the steps that you had made to replace this driver.
If there are several options with revisions on the Asus web site please post all of the options that you see for your computer's serial or product number and the operating system.

Hi zbook, thanks very much for your reply.

I'm only getting one blue screen type at the moment which is an IRQ one that happens sometime around Windows shutdown. Fast startup is still disabled though.

I did another full uninstall of all NVidia drivers on the system and then reinstalled the latest one direct from Nvidia. It seems like the general consensus online is to use Nvidias latest however as the card is made by Zotac perhaps I should try the latest from them (despite being slightly older than Nvidias)?

All I could find on Asus website with regards to compatibility for my motherboard was a hardware compatability list that dates back to 2015 - my NVidia chipset is not listed.

Thanks

Code:

BugCheck A, {8, 2, 1, fffff801cb298b2c}Probably caused by : raspptp.sys ( raspptp!CtlDisconnectCallback+a7 )

Code:

fffff801`cd654638  fffff80b`8eaf1beeUnable to load image nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x111bee

Code:

6 Jul 07:15    Application Error    Faulting application name: NVDisplay.Container.exe, version: 1.2.0.0, time stamp: 0x59079e96
Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.8205, time stamp: 0x59079dd9
Exception code: 0xc0000005
Fault offset: 0x00000000000c1951
Faulting process ID: 0x728
Faulting application start time: 0x01d2f627902f3172
Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe
Faulting module path: NvXDCore.dll
Report ID: 5f7bff7c-3cf6-4d53-aa87-1e1917cef640
Faulting package full name: 
Faulting package-relative application ID:

nvlddmkm.sys

nVidia Video drivers

http://www.nvidia.com/Download/index.aspx Get from OEM for laptops

Code:

BugCheck 1A, {41793, ffff8700d7000e88, f, e}Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+11b98e )

1) Make sure that there is no over clocking while troubleshooting.


Sometimes there are problems in the bios that produce bsod.

The bios in your computer: BIOS Version/Date American Megatrends Inc. 3701, 31 Mar


Please check to see if this is the most up to date version.


To ensure that there are no improper bios settings please reset the bios.


Sometimes there can be failure to boot after resetting the bios.

So please make sure your files are backed up.

Please make a backup image with Macrium:


Macrium Software | Macrium Reflect Free: Macrium Software | Macrium Reflect Free


And please create a restore point.




How to Clear Your Computers CMOS to Reset BIOS Settings:


How to Clear Your Computers CMOS to Reset BIOS Settings


3 Ways to Reset Your BIOS - wikiHow:


3 Ways to Reset Your BIOS - wikiHow




2) Uninstall all Nvidia drivers/software

The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Asus.

If there are no suitable Asus approved drivers then download from the Nvidia web site.

When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

Hi zbook,

I have performed your suggestions 1) & 2).

However, I get the same old memory management BSOD and an occasional IRQ one at shutdown.

This is all despite doing a clean install of latest NVIDIA (using DDU) and several weeks ago installing a different Wireless Network Card.

Yesterday, to take the Nvidia card out of the equation, I installed an ATI Firepro (workstation) Graphics card (doing a full video driver uninstall before doing so). This has been in for 24 hours and no memory management errors but today I did have the IRQ one.

I've attached my latest reports.
Attachment 148413

Kind regards
George

There was 1 bsod today and yesterday and there were no definitive misbehaving drivers.

Are you still using Fengato software (dvdfab.sys) or was this software uninstalled?

Windows driver verifier is a tool that is used to find misbehaving drivers.
It will repetitively produce bsod until the misbehaving drivers are fixed or until the tool is turned off.

Before using this tool make sure startup and recovery settings have automatic restart unchecked so that you have time to view the bsod window. When windows driver verifier is used there is often a stop code displayed: driver verifier detected violation. Sometimes the misbehaving driver is posted in the form *.sys. If you see it on the bsod window please record the misbehaving driver and post it into the thread.

Microsoft Community

After each bsod you will need to turn off windows driver verifier and return to the desktop. It is important to get comfortable with these methods before using the tool.

Open administrative command prompt and type: shutdown /r /o /f /t 00
The computer should reboot to the windows advanced troubleshooting menu.
Navigate to each of these:
1) startup options (not startup repair) > select #6 safe mode with command prompt > type: verifier /reset
2) command prompt > opens Administrator X: \Windows\system32\cmd.exe > type: verifier /bootmode resetonbootfail
3) restore
The above commands should always be used in the order above to turn off windows driver verifier. If restore is used the bsod mini dump file will likely disappear and little progress will be made in the troubleshooting.

To turn on windows driver verifier and to customize the testing use the information in this link:
Microsoft Community

For information on turning off windows driver verifier see this link:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

Before using windows driver verifier perform the following steps:
1) create a brand new restore point
2) backup files to another drive or to the cloud
3) make an image of the drive using Macrium: Macrium Software | Your Image is Everything
4) save the Macrium image on a drive other than the drive that is being tested with windows driver verifier.

Download and install these two software applications so that you can run them each time you return to the desktop:
Blue screen of death (STOP error) information in dump files.
http://www.resplendence.com/whocrashed

As the bsod occur please post a new zip: BSOD - Posting Instructions - Windows 10 Forums

Code:

BugCheck A, {8, 2, 1, fffff802feeabb2c}Probably caused by : raspptp.sys ( raspptp!CtlDisconnectCallback+a7 )

Code:

BugCheck 1A, {41793, ffff84009cb54ec8, 13, 12}Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+11b980 )

Code:

Event[13728]:  Log Name: System  Source: Microsoft-Windows-Kernel-PnP  Date: 2017-08-10T18:45:18.839  Event ID: 219  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-L224S2J  Description: The driver \Driver\dvdfab failed to load for the device USBSTOR\CdRom&Ven_PLEXTOR&Prod_BD-ROM_PX-B120U&Rev_1.11\6666666666666669FD6&0.

dvdfab.sys

DVDFab Passkey x86 Driver by Fengtao Software Inc

Support: http://www.dvdfab.com/support.htm Downloads: http://www.dvdfab.com/download.htm

Hi zbook,

Regarding dvdfab.sys I reinstalled this as it's absence didn't make any difference. Would you like me to uninstall again?

Today I got a memory management bsod so to me that suggests that the issue wasn't NVidia specific (as I'm now running an ATI workstation card).

I ran driver verifier with the suggested settings (thank you for the link) however when I rebooted all I got was the Windows splash logo (nothing else) and it just hung there. I have now reverted to a restore point. What's going on here?

Many thanks (as always)
George

When you were in the windows advanced troubleshooting menu to choose restore were you not able to choose either 1) startup options then safe mode with command prompt? or 2) command prompt opening Administrator X:\windows\system32\cmd.exe?
The restore option unfortunately leads to a loss of the mini dump and little progress is made in the troubleshooting.
Whenever you have a bsod please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

Safe mode with command prompt had the same problem - hanging windows logo.

If I can get option 2) to work what should I be doing if I get it open? I don't see a BSOD so I'm guessing there's nothing in the mini dump folder?