0

I was getting a bootloop with "automatic repair" I finally managed to fix it by leaving only my OS ssd plugged in and booting to windows, then it showed a "something went wrong rolling back" or something similar blue screen and I managed to boot to windows, then updated and everything went good so I plugged all the disks back.

My disks are:

  • 1TB SSD with OS
  • 1TB HDD 7200 Seagate
  • 4TB HDD 5600 WD Blue

I can plug the WD and still make it to Windows, if I plug the Seagate through USB I get a BSOD with the code PAGE_FAULT_IN_NONPAGED_AREA AND EUBKMON.SYS

If I leave it plugged in from the start I get a bootloop.

How can I fix this? I can probably plug the Seagate to a linux laptop I have.

I'm pretty sure the seagate is MBR while the other 2 are GPT, not sure if it has anything to do with the crash as it was working fine a few days ago.

Edit:

Files found on the seagate:

  • bootmgr
  • BOOTNXT
  • BOOTSECT.BAK
  • EUMONBMP.SYS
  • RTCNS
  • SYSTEM VOLUME INFORMATION (DIR)
  • Boot (DIR)
Daviid
  • 118
  • 12

2 Answers2

1

That specific BSOD error code is almost certainly due to a bad driver; it does not indicate anything wrong with your drive.

PAGE_FAULT_IN_NONPAGED_AREA basically means that the driver tried to access invalid memory. That usually means there's a bug in the driver.

A quick internet search will tell you that EUBKMON.SYS is part of something called "EaseUS Todo Backup Monitor". It is quite possible that you're encountering a bug present only in the code that processes MBR drives. Either way, it would probably be a good idea to remove the faulty software.

user1655754
  • 308
0

Files found on the seagate:

  • bootmgr
  • BOOTNXT
  • BOOTSECT.BAK
  • EUMONBMP.SYS
  • RTCNS
  • SYSTEM VOLUME INFORMATION (DIR)
  • Boot (DIR)

I deleted these and then used the gdisk command on linux to convert the HDD from MBR to GPT.

After that I was able to connect the HDD to my windows computer without problem and without data loss.

Daviid
  • 118
  • 12