• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: October 30th, 2023

help-circle
  • I read all 4 of the BSODs. The repeated occurrence of PAGE_FAULT_IN_NONPAGED_AREA errors pointing to the nvlddmkm.sys file, which is related to NVIDIA graphics drivers, strongly suggests that the problem is related to the graphics driver or its interaction with the system.

    Here are possible factors contributing to these issues:

    Driver Problems: Outdated, corrupted, or incompatible NVIDIA graphics drivers could be causing conflicts or memory access issues, leading to the PAGE_FAULT_IN_NONPAGED_AREA errors.

    Memory Issues: While the error often relates to the driver, underlying hardware problems, especially with the system’s RAM, could also cause similar symptoms.

    Software Conflicts: Other software interactions or conflicts with the graphics driver might be triggering these errors.

    Given this, the most likely issue appears to be related to the NVIDIA graphics drivers. Here are steps you can take to resolve or further diagnose the problem:

    Update or Reinstall Graphics Drivers: Ensure that you have the latest version of the NVIDIA drivers installed. Consider performing a clean install of the drivers to eliminate any potential corruption.

    Hardware Diagnostics: Run hardware diagnostics, particularly memory tests, to check for any issues with the system’s RAM or other hardware components.






  • As soon as I started reading it the first line I thought “this guy’s using wordpress”. Last time this happened to me I had an outdated plugin that allowed a bad actor to jack with my .htaccess file. I reset my .htaccess file, updated my plugins, started paying for longer backup lengths, and suggested the org hire an MSP of some kind to manage the site, since nobody on staff had any WP expertise.




  • The dumps are kind of all over the place. I opened the 3 most recent:
    UNEXPECTED_STORE_EXCEPTION (154)
    The first minidump points to an “UNEXPECTED_STORE_EXCEPTION” (154). This type of error is related to the Windows Store component.
    The analysis indicates an access violation and suggests a problem with a memory address.
    Possible causes: This error can be caused by various factors, including system file corruption, disk issues, memory problems, or even driver problems.
    BAD_POOL_CALLER (c2)
    The second minidump shows a “BAD_POOL_CALLER” (c2) error, which indicates issues with memory pool allocation.
    The analysis points to problems with freeing memory or double freeing memory allocations.
    Possible causes: This error is often related to hardware or driver issues, including issues with RAM, drivers, or recently installed hardware.
    UNEXPECTED_STORE_EXCEPTION (154)
    The third minidump is another instance of “UNEXPECTED_STORE_EXCEPTION” (154) similar to the first one.
    It again suggests an access violation with memory.
    The root cause could be similar to the first occurrence, possibly involving system file corruption, disk problems, or other system issues.

    I’d start by downloading memtest86, booting to that, and testing your memory. If your RAM passes, download something like SeaTools, boot to that, and test your disk. It’s probably one of those two, based on these dumps.