Creator Update Paging in Non-Paged Area

I did the Creator update for Windows 10 today, and since then I've been getting consistent BSOD crashes due to page fault in non-paged area, where I was getting no BSODs before. I'd like to fix the situation and not just do a rollback, but if that's the best step I'll go ahead and do that.

Attachment 134004

Hello Flelm :)

This could be due to a new driver being installed by the Creator update process. The problem is finding which one it is. All the crash reports say that the faulting driver cannot be identified.

I did notice a problem with one of your drives:

Code:

Event[695]:
  Log Name: System
  Source: Disk
  Date: 2017-05-07T15:13:48.661
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-F90QV42
  Description: 
The device, \Device\Harddisk3\DR3, has a bad block.

Event[696]:
  Log Name: System
  Source: NTFS
  Date: 2017-05-07T15:13:48.661
  Event ID: 137
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-F90QV42
  Description: 
The default transaction resource manager on volume F: encountered a non-retryable error and could not start.  The data contains the error code.

It would be worth testing the drive further. E.g. CHKDSK and attempt a repair.

I did run CHKDSK yesterday/overnight on my 3 internal drives. F: is an external drive, I'll try disconnecting that and seeing what happens rather than a full CHKDSK.

The BSOD has started happening quicker and quicker. I cannot even log into Windows now to troubleshoot. Everything has to be done in safe mode.

I ended up doing a chkdsk on that last (external) drive, and still did not fix my issues. I rolled back and my problem was immediately solved.

Did you originally receive the creators update as part of the normal windows update process?

Yes, it was part of the normal process.

Flelm said:

Yes, it was part of the normal process.

So my worry is that it may come back again unless you defer the upgrade.

Yup, I already did that. Thanks. :)