Windows 10: BSOD MEMORY_MANAGEMENT started after upgrade to Win 10

I used to have Windows 7 on this system with no issues. After upgrading to Windows 10, several buggy things started occurring:

1. During the upgrade process and afterwards every time I booted the system it would halt on a blue screen and say:
The Digital Signature of a file could not be verified\windows\system 32\drivers\Tpmx64.sys
Error system code Oxc000042B

I would have to hit F8 to change startup options, and then choose option 7 "Disable driver signature enforcement." which would allow it to continue booting up.

2. It began to show a pop-up window every time upon logging into Windows that said, "The SoundMAX audio driver did not load. You may need to re-install SoundMAX."

3. The BSOD events also started happening. There has been no particular program or activity that seemed to cause it. It happens both when I'm at the computer and when it's idle. It seems to happen every 1-2 days on average.

I decided to do a clean re-install of Windows 10, hoping it would clear up the issues. It did eliminate issues 1 and 2, but not the BSODs. It's always been the MEMORY_MANAGEMENT error message both before and after Windows 10 re-installation.

I did Memtest86+ for 18.75 passes and no memory errors occurred. In addition, I never had any BSODs previously with Windows 7, so I'm pretty confident it's not the physical memory.

I am attaching the .zip file as well as the results from running WinDbg on the two most recent MEMORY.DMP files. I used the BlueScreenView program to look at the minidump files and with all of them the driver in the stack at the time of the error is ntoskrnl.exe. In amongst all the WinDbg output it says:

ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation. The data read from storage does not match the original data written. This indicates the data was corrupted by the storage stack, or device hardware.

Hopefully I've collected enough info that someone can help me finally figure this bugger out. *BangheadThanks in advance.

:)

 

Stopping the 1709 update

is there any way to delay in windows 10 Home? It is a nightmare trying to upgrade to 1709 again and again. Can Microsoft solve this upgrade problems? MEMORY_MANAGEMENT is the only sign in BSOD .

 

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

 

Hi Fonebone,

Welcome to the 10forums.

Please update the drivers of your NoMachine Microphone adapter audio device
Driver Reference Table - nxaudio.sys

0x1A is a little wide, because the memory management goes very deep, but as the dumps say the corruption was caused by either drivers or hard drive.

As usual the 0x1A crashes do not reveal any driver possibly causing it, forcing the use of driver verifier to attempt to find any driver.
If driver verifier doesn't crash your system after 48h, stop driver verifier and run hard drive tests.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.





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.

 

OK, thanks, I am starting the driver verifier.

The first thing you said was to update the drivers of NoMachine Microphone adapter audio device. I did a check and it says they are current.

I also ran sfc /scannow and it said there were file errors it could not fix. All the files it found were in the C:\windows\WinSxS\amd64_etc-really-long-name folders. Is that something I need to address and do you think it is relevant to what's causing my BSOD event?

Thanks.

 

If you checked through device manager I would say that you need to check the company that provides the right drivers which is usually the company that makes device (no driver update program or something)


If SFC says in the log that the source is corrupted then try following
Please try following command in admin command prompt
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial.

After restorehealth is successful finished, run sfc twice with a reboot between them, that should completely resolve the corruption.

 

Here's the latest:

The driver verifier caused a BSOD crash. It seems to point to the nxusbs.sys driver, if I am interpreting things correctly. I have attached some info files. The drivers that start with nx... belong to the NoMachine remote desktop service. I used the NoMachine "check for update" function to check if all their drivers are current and it says they are.

What's my next step?

 

Try to reinstall NoMachine with a new download