Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blue Screen: DPC_WATCHDOG_VIOLATION #75

Open
4 tasks done
PhilippeDr opened this issue Mar 31, 2024 · 3 comments
Open
4 tasks done

Blue Screen: DPC_WATCHDOG_VIOLATION #75

PhilippeDr opened this issue Mar 31, 2024 · 3 comments

Comments

@PhilippeDr
Copy link

PhilippeDr commented Mar 31, 2024

System

  • Motherboard: MSI X570-A PRO
  • BIOS Version: 7C37vHM
  • GPU: KFA2 RTX 2070
  • CSM is turned off.
  • 4G decoding is enabled.
  • UEFIPatch is applied without DSDT
  • I have read Common issues (and fixes)

Description

My computer occasionally crashes giving me a blue screen saying DPC_WATCHDOG_VIOLATION, this started happening after the patch, I've even applied the patch on another system with almost identical specs and there it doesn't seem to be happening, is there anything I could try to fix this while keeping rebar enabled, lower bar size maybe?

@terminatorul
Copy link
Owner

terminatorul commented Apr 1, 2024

Sorry I don't know about this. @xCuri0 did you hear anything before about this blue screen ?

However you should disable NvStrapsReBar just to make sure NvStrapsReBAR was causing it. Also make sure this is not from memory overclocking or memory errors for example, can you run OCCT Memory Test ?

Also make sure you have the latest video driver and chipset drivers

@xCuri0
Copy link

xCuri0 commented Apr 1, 2024

@terminatorul those that complained about bluescreens from rebaruefi were always running overclocks, resizable bar puts more load on cpu and pcie than usual

@PhilippeDr
Copy link
Author

PhilippeDr commented Apr 3, 2024

I fixed the issue by lowering my rebar from 8GB to 4GB, I also temporarily removed my Bluetooth adapter from my pc to test if it was a faulty driver causing it and since doing both of those I haven't bluescreened

I'm also not running any overclocks, and have the latest video drivers and chipset drivers

Ill be testing it with 8GB again and ill update this with my findings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants