Predator G3-710 freezing and IRQL Not Less or Equal BSOD

WLIM
WLIM Member Posts: 9 New User
edited February 2024 in 2020 Archives
I bought a second hand G3-710 and it was running fine. Recently though, it's been freezing or crashing with the IRQL Not Less than Equal error code.
I checked the specs and found that the BIOS is R01-A1.
Would downloading and installing the R01-A4 update help?

Answers

  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    The only substantial changes I see in those version is the microcode update, but that just fixes the security vulnerabilities in the CPUs. Can you take pictures of the BSODs? They often have fine print that helps see the specific faulting module.
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • WLIM
    WLIM Member Posts: 9 New User
    I contacted Microsoft, and they provided me with some help, e.g. sfc /scannow & DISM.exe /Online /Cleanup-image /Restorehealth using the command prompt. I also installed the R01-A4 update. After doing the above, my computer was fine for the rest of the day and the first half of the next day. Later though, it hung again.
    So far, the BSODs I've gotten are: IRQL_NOT_LESS_OR_EQUAL, System Service Exception & KMODE Exception Not Handled.
  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    Try to take pictures of those screens...
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • WLIM
    WLIM Member Posts: 9 New User
    Got a new BSOD earlier today.
  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    edited September 2020
    OK, that dump was caused by win32kfull.sys, so likely really caused by a corrupted device driver since win32kfull.sys pretty much is involved with the interface between the OS and the hardware. I see you've gone through the SFC and DISM procedures to make sure there isn't corrupting in the OS itself. You might also give CHKDSK on your C: partition a shot, since corrupted sectors could also cause it. I'd start with those, and try to keep in mind what changed just before this started and come back with your results.
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • WLIM
    WLIM Member Posts: 9 New User
    I've run CHKDSK on both my C: and D: drives, but no errors were detected in either. However, when I opened event viewer to try and identify what was causing the problems, I noticed that there were always critical errors with DriverFrameworks-UserMode.

    Event 10111: "The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash."
    Event 10110: "A problem has occurred with one or more user-mode drivers and the hosting process has been terminated."

    I've tried disabling and re-enabling the offending driver, but that's not working either. Currently using a Cloud II HyperX headset.

  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    Try running with the headset disconnected for a while to see if that is the culprit. If it is then we'll look into which drivers it's using, and if you keep getting crashes with it not connected then we'll know it's likely something else.
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • WLIM
    WLIM Member Posts: 9 New User
    So I've tried that, but it's incredibly inconsistent. I ran World of Warcraft with the headset unplugged, and it was fine. I tried plugging the headset back in, and it's stable so far. What's weird is that yesterday, it was running fine with the headset plugged in from around 2pm-6pm, but started randomly hanging when I powered it back on again from 7.30pm onwards.
  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    Yeah, diagnosing intermittent problems can be the least rewarding task to do with a computer. :( Until you actually find out what the problem was. :)
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • WLIM
    WLIM Member Posts: 9 New User
    Hmm, the random freezing seems to have started again, and this time there's no DriverFrameworks-UserMode critical error.
    It just froze while I was using Google Chrome with no associated critical error in the Event Viewer.
  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    Keep watching the BSODs and capture pictures when they have that tiny text like the win32kfull.sys you showed above. Eventually there'll be enough evidence to say what's causing it, or that it's random enough it's got to be the PSU or memory...
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • WLIM
    WLIM Member Posts: 9 New User
    Unfortunately, it's not really giving me BSODs, just the random freezing.
  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    Does it ever recover from a freeze after a few minutes? There are a couple of different types of freezes. It can freeze by locking things up when a task takes over but doesn't release. In that case you can still move the mouse around but clicking it doesn't do anything. Those are usually software based. It can lock things up by locking the PCI bus and in that case the mouse doesn't even move. Those are usually hardware or driver. Try disconnecting all your peripherals except keyboard, mouse and monitor. Then do your normal use as much as possible to see if the issue persists.
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • WLIM
    WLIM Member Posts: 9 New User
    Nope, it's never recovered after freezing. In my case, it's the latter. Nothing works when it freezes. 
    I've already tried disconnecting my peripherals as it was one of the suggestions from the Microsoft advisor, but to no avail. I've also connected them all to my laptop, and everything runs smoothly then. 
  • WLIM
    WLIM Member Posts: 9 New User
    Right, so I got this earlier
    https://imgur.com/a/kDNXNAZ
  • billsey
    billsey ACE Posts: 35,102 Trailblazer
    Dang, that's one of the BSODs that doesn't point at a specific driver. I note that it's not the IRQ NOT LESS THAN OR EQUAL TO type. Let's try and capture a few of them to see if they are pretty much random or not. Random crashes will tend to point at a faulty power supply or faulty memory...
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.