Win 11 BSODs since last month on Ace Magician AM06PRO Mini PC

foxhoundrzl

foxhoundrzl

Active member
Joined
Aug 4, 2017
Posts
26
  • A brief description of your problem (but you can also include the steps you tried) I've been experiencing BSODs since last month. Errors are not always the same, details provided later in this thread. Any assistance would be greatly appreciated!
  • System Manufacturer? Ace Magician
  • Laptop or Desktop? Mini PC Desktop
  • Exact model number (if laptop, check label on bottom) AM06PRO
  • OS ? Windows 11
  • x64 (64bit)
  • What was original installed OS on system? Windows 11
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
  • Age of system? (hardware) 1 year
  • Age of OS installation? 1 year
  • Have you re-installed the OS? No
  • CPU AMD Ryzen 7 4800U
  • RAM (brand, EXACT model, what slots are you using?) 16GB DDR4
  • Video Card Integrated AMD Radeon
  • MotherBoard - (if NOT a laptop) Unsure
  • Power Supply - brand & wattage (if laptop, skip this one) Unsure
  • Is driver verifier enabled or disabled? No
  • What security software are you using? Windows Defender
  • Are you using proxy, vpn, ipfilters or similar software? No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
  • Are you currently under/overclocking? Are there overclocking software installed on your system? No


Speccy Published Results
https://speccy.piriform.com/results/82coMUW0suupoU2lGzBsTjp


BlueScreenView details provided below
==================================================
Dump File : 101524-9125-01.dmp
Crash Time : 10/15/2024 9:26:10 PM
Bug Check String : ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug Check Code : 0x000000fc
Parameter 1 : fffff805`2ad37000
Parameter 2 : 89000004`02a1a963
Parameter 3 : ffff808d`3a3ccfd0
Parameter 4 : 00000000`00000002
Caused By Driver : Wof.sys
Caused By Address : Wof.sys+17000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+414df0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\101524-9125-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 22621
Dump File Size : 952,951
Dump File Time : 10/15/2024 9:26:28 PM
==================================================

==================================================
Dump File : 101024-11343-01.dmp
Crash Time : 10/10/2024 10:43:55 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff807`1b819bcd
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+414df0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+414df0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\101024-11343-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 22621
Dump File Size : 760,940
Dump File Time : 10/10/2024 10:44:16 AM
==================================================

==================================================
Dump File : 100324-8437-01.dmp
Crash Time : 10/3/2024 11:22:15 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff806`63f8ba34
Parameter 3 : ffffb787`f7d329f0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+414fd0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+414fd0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100324-8437-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 22621
Dump File Size : 2,510,899
Dump File Time : 10/3/2024 11:22:32 AM
==================================================

==================================================
Dump File : 092724-12437-01.dmp
Crash Time : 9/27/2024 12:16:48 PM
Bug Check String :
Bug Check Code : 0x00000133
Parameter 1 : 00000000`00000001
Parameter 2 : 00000000`00001e00
Parameter 3 : fffff803`2e11d340
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+416000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+416000
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\092724-12437-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 22621
Dump File Size : 545,394
Dump File Time : 9/27/2024 12:17:11 PM
==================================================

==================================================
Dump File : 092524-10218-01.dmp
Crash Time : 9/25/2024 7:28:25 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`000000ff
Parameter 3 : 00000000`000000c2
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+416000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+416000
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\092524-10218-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 22621
Dump File Size : 2,309,388
Dump File Time : 9/25/2024 7:28:45 PM
==================================================
 

Attachments

Follow-up information:
  • sfc /scannow tool returned no errors
  • Windows memory diagnostics returned no errors
 
TBH BlueScreenView isn't worth having installed, it really doesn't tell you anything terribly useful.

Looking at all the dumps these BSODs seem to happen during different operations and have different bugcheck codes. Reading between the lines in these dumps it's possible that bad RAM could be a factor and whenever bad RAM is suspected it's important to test the RAM before doing anything else. Please test your RAM using Memtest86 as follows...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

In addition, in many of the dumps I can possibly see third-party drivers being called. What we see are the Windows drivers Wdf01000.sys and fltmgr.sys being called in different dumps. These high-level drivers manage drivers that use the Windows Driver Foundation (typically third-party drivers) and filter drivers (often third-party filter drivers). If Memtest86 runs with no errors then the next most sensible step will be to enable Driver Verifier. Full details on how to do that, and what specific options to select, can be found at Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista. Please read through that sticky before doing anything and make sure you understand what you're going to be doing before you do enable Driver Verifier.

If you get BSODs with Driver Verifier enabled please run the Sysnative data collection app again and upload the new output.
 
ubuysa said:
TBH BlueScreenView isn't worth having installed, it really doesn't tell you anything terribly useful.

Looking at all the dumps these BSODs seem to happen during different operations and have different bugcheck codes. Reading between the lines in these dumps it's possible that bad RAM could be a factor and whenever bad RAM is suspected it's important to test the RAM before doing anything else. Please test your RAM using Memtest86 as follows...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

In addition, in many of the dumps I can possibly see third-party drivers being called. What we see are the Windows drivers Wdf01000.sys and fltmgr.sys being called in different dumps. These high-level drivers manage drivers that use the Windows Driver Foundation (typically third-party drivers) and filter drivers (often third-party filter drivers). If Memtest86 runs with no errors then the next most sensible step will be to enable Driver Verifier. Full details on how to do that, and what specific options to select, can be found at Driver Verifier Instructions - BSOD - Windows 11, 10, 8(.1), 7 and Vista. Please read through that sticky before doing anything and make sure you understand what you're going to be doing before you do enable Driver Verifier.

If you get BSODs with Driver Verifier enabled please run the Sysnative data collection app again and upload the new output.
Click to expand...

Thanks! I will create a bootable Memtest86 USB on a difference PC and run it against the AM06PRO machine.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top