Question Crash issue / BSOD - recently reinstalled Windows 10 ?

[Pepsomo]

Hi I need advice on how to stop my PC from crashing.

I have done memory tests to make sure my ram is okay. I used memtest86 and the windows memory test.
This is a fresh install of Windows 10 64 bit.

My pc has a 1070Ti (latest Geforce drivers), AMD 3700x, 16gb 3200Mhz (running at 2133Mhz stock standard atm), 850 Watt Corsair power supply. Recently replaced the CMOS battery as well (I was experiencing crashed before the battery replacement too).


The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffb8835b6fc2e8, 0x0000000000000000, 0xfffff8041183cb18, 0x0000000000000002). A dump was
Report Id: 8d85c946-a42b-4e5f-9696-8623a0af335c.

I had been experiencing the bug beforehand. I also installed OCCT to test my CPU and powersupply and am unfortunately getting errors on both.

https://imgur.com/a/obW2xM7

View: https://imgur.com/a/obW2xM7


Any advice will be greatly appreciated. I have also tried to use a different plug to power my PC but that has not helped.

 

[SkyNetRising]

Any advice will be greatly appreciated.

Check cpu temperatures.
Reduce cpu overclock.
Increase dram voltage to 1.35V.

BTW - what motherboard are you using?
What cpu cooler?

 

[Pepsomo]

Check cpu temperatures.
Reduce cpu overclock.
Increase dram voltage to 1.35V.

BTW - what motherboard are you using?
What cpu cooler?

CPU idle temps running at 53 degrees C.

CPU cooler is water based - corsair I believe.

Not currently overclocking CPU, just running stock standard.

But will keep the RAM voltage in mind.

 

[SkyNetRising]

CPU idle temps running at 53 degrees C.
CPU cooler is water based - corsair I believe.

That's actually quite high for idle.
What are temperatures at full cpu load?

Your cpu cooler may have failed and need replacing.

 

[ubuysa]

It would be nice to see the dump. Can you upload to a cloud service all dumps in C:\Windows\Minidump with a date in this year please.

The 0x00000050 (0xffffb8835b6fc2e8, 0x0000000000000000, 0xfffff8041183cb18, 0x0000000000000002) is a page fault in a non-pageable pool. The 0x2 in argument 4 indicates that a reference to a non-existing page was made (no PTE present). This is commonly a driver error and the dump may well help locate which driver...

 

[Pepsomo]

It would be nice to see the dump. Can you upload to a cloud service all dumps in C:\Windows\Minidump with a date in this year please.

The 0x00000050 (0xffffb8835b6fc2e8, 0x0000000000000000, 0xfffff8041183cb18, 0x0000000000000002) is a page fault in a non-pageable pool. The 0x2 in argument 4 indicates that a reference to a non-existing page was made (no PTE present). This is commonly a driver error and the dump may well help locate which driver...

Here is a link to two recent minidump files. These are the only minidump files in my C: directory.

https://drive.google.com/file/d/1rVPxNHSfuxUYq7AyKVdkQdwjjtw3BCg-/view?usp=drive_link

 

[ubuysa]

Although the two dumps fail with different bugchecks (0x50 and 0xA) both are commonly caused by bad third party drivers. Typically what happens is that the bad driver fouls up a shared data structure and ends, and it's not until another driver or function tries to access that data structure that we get the BSOD. That's what seems to have happened here because both BSODs actually occur in two different Windows functions. You do have a driver that's a well-known caused of BSODs installed, we see it in these dumps as recently unloaded. The driver is BEDaisy.sys the BattleEye anti-cheat driver.

Because BEDaisy.sys has already been unloaded in these dumps I'm not able to tell you the date of the driver. A good test would be to reboot (to unload BEDaisy.sys) and then see whether you get these BSODs without running the BattleEye anti-cheat tool. That may mean there are certain games you cannot play at the moment. What we want to see is whether it BSODs when BEDaisy.sys is not loaded.

Once you've confirmed that it's BEDaisy.sys causing these BSODs (and it probably is) you should contact BattleEye Support, either for an updated driver version or for further assistance from them. All these anti-cheat tools cause BSODs on many systems, and very often.

 

[Pepsomo]

Although the two dumps fail with different bugchecks (0x50 and 0xA) both are commonly caused by bad third party drivers. Typically what happens is that the bad driver fouls up a shared data structure and ends, and it's not until another driver or function tries to access that data structure that we get the BSOD. That's what seems to have happened here because both BSODs actually occur in two different Windows functions. You do have a driver that's a well-known caused of BSODs installed, we see it in these dumps as recently unloaded. The driver is BEDaisy.sys the BattleEye anti-cheat driver.

Because BEDaisy.sys has already been unloaded in these dumps I'm not able to tell you the date of the driver. A good test would be to reboot (to unload BEDaisy.sys) and then see whether you get these BSODs without running the BattleEye anti-cheat tool. That may mean there are certain games you cannot play at the moment. What we want to see is whether it BSODs when BEDaisy.sys is not loaded.

Once you've confirmed that it's BEDaisy.sys causing these BSODs (and it probably is) you should contact BattleEye Support, either for an updated driver version or for further assistance from them. All these anti-cheat tools cause BSODs on many systems, and very often.

Thanks for looking into this, yes I do actually play a game that uses battle-eye anti-cheat quite regularly.

How can I got about unloading the BEDaisy.sys anti-cheat? Just by rebooting?

The strange thing is, I just got done playing about a 1hr session of a game that uses the anti-cheat and have not had a crash as of yet...

For e.g., my PC experienced a BSOD whilst I was not active at the PC and without running BattleEye. However I can try uninstall the driver completely to test for a few days.

Any suggestions on how I can go out completely disabling / unloading / uninstalling the driver?

Cheers.s

 

[Pepsomo]

Although the two dumps fail with different bugchecks (0x50 and 0xA) both are commonly caused by bad third party drivers. Typically what happens is that the bad driver fouls up a shared data structure and ends, and it's not until another driver or function tries to access that data structure that we get the BSOD. That's what seems to have happened here because both BSODs actually occur in two different Windows functions. You do have a driver that's a well-known caused of BSODs installed, we see it in these dumps as recently unloaded. The driver is BEDaisy.sys the BattleEye anti-cheat driver.

Because BEDaisy.sys has already been unloaded in these dumps I'm not able to tell you the date of the driver. A good test would be to reboot (to unload BEDaisy.sys) and then see whether you get these BSODs without running the BattleEye anti-cheat tool. That may mean there are certain games you cannot play at the moment. What we want to see is whether it BSODs when BEDaisy.sys is not loaded.

Once you've confirmed that it's BEDaisy.sys causing these BSODs (and it probably is) you should contact BattleEye Support, either for an updated driver version or for further assistance from them. All these anti-cheat tools cause BSODs on many systems, and very often.

https://imgur.com/a/0fm2E0q

View: https://imgur.com/a/0fm2E0q


This is a list of the drivers I currently have installed that start with b. I cant see BEDaaisy.sys in there. Unless I am looking in the wrong place.

 

[ubuysa]

If the driver is currently unloaded it won't show.

To unload BEDaisy.sys just reboot and then be sure to not start any game that requires it. AFAIK if you remove it then games that require it will not start. It's a bit of a Catch22.

BTW. I'm not claiming that your problem IS caused by BEDaisy.sys but it's such a well-known cause of BSODs that we need to eliminate it first. If it BSODs after a reboot and before you load any game that requires or uses BEDaisy then please upload the resulting dump.