Windows 11 Persistent Crash/Reboots on Brand new ASUS ROG Intel 9 & nVidia 5090 Laptop

Steve Gillis 0 Reputation points
2026-11-20T23:37:20.7366667+00:00

Hello, looking for support to figure out why my brand new (Less than a week) old ASUS Rog, Model #: G835LXG-DB96 laptop continues to randomly reboot, seeming for different reasons. Bios is patched to latest version and all Windows 11 patches as of 11/20/2026 have been applied as well. Here is the Bug Code from the latest crash:

The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8026dc441a0, 0xffffa40218aed1e0, 0x0000000000000000)

I have the 5 DMP files available to upload since this started happening yesterday.

The .dmp file type isn't allowed to be uploaded here by the policy set for file attachments, so if someone can direct me where to upload those, I can do so immediately.

Thank you in advance for any assistance that can be provided!

Windows for home | Windows 11 | Performance and system failures

8 answers

Sort by: Oldest
  1. AI answer

    2026-11-20T23:38:29.4533333+00:00

    Upload the five minidumps as one ZIP file to OneDrive, create a view-only share link, and add that link to your Q&A post; the 0x3B parameters alone cannot identify the failing driver.

    Prepare and share the dumps safely

    1. Open File Explorer and go to:
         C:\Windows\Minidump
      
    2. Copy the five .dmp files to a new folder on the Desktop. Administrator approval might be required.
    3. Right-click the folder and select Compress to ZIP file.
    4. Upload the ZIP to OneDrive.
    5. Select the uploaded file → Share → configure Anyone with the link can view if available → Copy link.
    6. Post that link in the Q&A thread. This is the established workaround when Q&A blocks .dmp attachments.^1^

    Share only the minidumps, not a large C:\Windows\MEMORY.DMP. Before sharing, avoid putting personal information in the ZIP filename and review the OneDrive permission and account name exposed by the link.

    What this bug check establishes

    0x0000003B is SYSTEM_SERVICE_EXCEPTION. Your first parameter, 0xC0000005, is an access violation. Parameter 2 is the faulting instruction address, and Parameter 3 points to the saved exception context.^2^

    That does not establish whether the cause is NVIDIA, another driver, memory corruption, or hardware. Similar 0x3B cases have implicated entirely different modules, so fixes such as removing the NVIDIA driver or disabling Intel power management should not be applied until these particular dumps identify that component.

    Optional local analysis with WinDbg

    If you want immediate preliminary results, open each dump in WinDbg:

    1. Start WinDbg.
    2. Select File → Open Crash Dump or press Ctrl+D.
    3. Open one file from C:\Windows\Minidump.
    4. Run:
    !analyze -v
    !error 0xc0000005
    .cxr 0xffffa40218aed1e0
    kb
    dx KiBugCheckDriver
    lm t n
    
    1. Save the output, then repeat for all five dumps.

    Microsoft recommends beginning with !analyze; for 0x3B, the saved context from Parameter 3 and the stack backtrace are particularly relevant.^3^ Compare these fields across all five:

    • MODULE_NAME
    • IMAGE_NAME
    • FAILURE_BUCKET_ID
    • STACK_TEXT
    • KiBugCheckDriver
    • Repeated third-party modules in the stack

    A module merely appearing in the stack is not automatically the culprit. A consistent result across several dumps is more useful than a single Probably caused by line.^4^

    Next action based on the dump results

    • If several dumps identify nvlddmkm.sys: treat the NVIDIA graphics driver as the targeted lead. Use the ASUS-supported graphics package first, or perform a clean driver replacement if advised by ASUS. A closely matching Windows 11 0x3B case was resolved by removing and reinstalling the NVIDIA driver, but that action depended on its dumps specifically identifying nvlddmkm.sys.^5^
    • If different dumps identify unrelated modules or memory corruption: stop software experimentation and ask ASUS to run hardware diagnostics.
    • If the dumps remain inconclusive: correlate each crash time with Event Viewer → Windows Logs → System, looking immediately before the BugCheck/unexpected restart for device or driver events. Microsoft also recommends checking Device Manager for fault indicators and matching System-log errors.^2^

    Do not enable Driver Verifier yet. It deliberately stresses drivers and can trigger additional crashes; Microsoft recommends selecting as few drivers as possible when it is necessary.^4^

    Because this laptop is less than a week old and has already received the current BIOS and Windows updates, preserve the dumps and open an ASUS warranty/return case now if crashes continue. Recurrent failures on a new, unmodified system should be investigated within the return period rather than masked through registry changes or a clean Windows installation. ASUS provides a manufacturer-specific automatic shutdown/restart troubleshooting and support path.^6^


    References

    1. (Error)The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8026be7b9dc, 0xffffd58252fc2600, 0x0000000000000000) - Microsoft Q&A
    2. Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
    3. Analyze a kernel-mode dump file by using WinDbg
    4. Analyze bug check (stop code error) data
    5. How to fix 0x0000003b (0x00000000c0000005, 0xfffff804c448b929, 0xffffce025a436150, 0x0000000000000000). - Microsoft Q&A
    6. [Windows 11/10] Troubleshooting - Automatic Shutdown/Restart Issues | Official Support | ROG Global
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Ivan B 127.6K Reputation points Independent Advisor
    2026-11-21T00:09:38.2933333+00:00

    Hi ,

    Search for msinfo32.exe in the search bar, take a screenshot, and post it here so we can see the correct laptop model or desktop configuration.

    Access the c:\windows\minidump folder, copy the files to your desktop, then upload them to OneDrive and post the link here for analysis.

    Thanks

    Was this answer helpful?

    0 comments No comments

  3. Steve Gillis 0 Reputation points
    2026-11-21T00:17:20.4+00:00

    Was this answer helpful?

    0 comments No comments

  4. Ivan B 127.6K Reputation points Independent Advisor
    2026-11-21T00:21:15.7666667+00:00

    Hi,

    In this case, there were 2 failures involving the Intel iGPU driver and 2 failures related to Intel PPM. When errors like these occur, it often points to a hardware issue—typically with the processor or the memory.

    By the way, did you change any BIOS settings?

    Thanks

    Was this answer helpful?


  5. Steve Gillis 0 Reputation points
    2026-11-21T00:32:01.3233333+00:00

    Here is the System Info screenshot: User's image

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.