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
- Open File Explorer and go to:
C:\Windows\Minidump - Copy the five
.dmpfiles to a new folder on the Desktop. Administrator approval might be required. - Right-click the folder and select Compress to ZIP file.
- Upload the ZIP to OneDrive.
- Select the uploaded file → Share → configure Anyone with the link can view if available → Copy link.
- Post that link in the Q&A thread. This is the established workaround when Q&A blocks
.dmpattachments.^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:
- Start WinDbg.
- Select File → Open Crash Dump or press Ctrl+D.
- Open one file from
C:\Windows\Minidump. - Run:
!analyze -v
!error 0xc0000005
.cxr 0xffffa40218aed1e0
kb
dx KiBugCheckDriver
lm t n
- 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 110x3Bcase was resolved by removing and reinstalling the NVIDIA driver, but that action depended on its dumps specifically identifyingnvlddmkm.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
- (Error)The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8026be7b9dc, 0xffffd58252fc2600, 0x0000000000000000) - Microsoft Q&A
- Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
- Analyze a kernel-mode dump file by using WinDbg
- Analyze bug check (stop code error) data
- How to fix 0x0000003b (0x00000000c0000005, 0xfffff804c448b929, 0xffffce025a436150, 0x0000000000000000). - Microsoft Q&A
- [Windows 11/10] Troubleshooting - Automatic Shutdown/Restart Issues | Official Support | ROG Global