Experienced a blue screen followed by a restart, suggesting a potential issue.
Experienced a blue screen followed by a restart, suggesting a potential issue.
This occurred while I was working in Lightroom CC. Assistance is needed!
It appeared...
"For more information on using just-in-time (JIT) debugging instead of this window, see the details below. ************** Exception Text ************** System.ArgumentOutOfRangeException: InvalidArgument=Value of '-1' is not valid for 'index'. Parameter name: index at System.Windows.Forms.ListView.GetItemState(Int32 index, Int32 mask) at System.Windows.Forms.ListViewItem.get_StateImageIndex() at System.Windows.Forms.ListView.ListViewNativeItemCollection.Add(ListViewItem value) at System.Windows.Forms.ListView.ListViewItemCollection.Add(ListViewItem value) at Microsoft.Windows.ManagementUI.CombinedControls.EventHomeControl.UpdateLogSummaryUI() ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.9310.0 built by: NET481REL1LAST_C CodeBase:
file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
---------------------------------------- Microsoft.ManagementConsole Assembly Version: 3.0.0.0 Win32 Version: 10.0.26100.1 CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.ManagementConsole/3.0.0.0__31bf3856ad364e35/Microsoft.ManagementConsole.dll
---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.9310.0 built by: NET481REL1LAST_C CodeBase:
file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
---------------------------------------- MMCFxCommon Assembly Version: 3.0.0.0 Win32 Version: 10.0.26100.1 CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/MMCFxCommon/3.0.0.0__31bf3856ad364e35/MMCFxCommon.dll
---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.9032.0 built by: NET481REL1 CodeBase:
file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C CodeBase:
file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.9032.0 built by: NET481REL1 CodeBase:
file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.9256.0 built by: NET481REL1LAST_B CodeBase:
file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.9032.0 built by: NET481REL1 CodeBase
---------------------------------------- EventViewer Assembly Version: 10.0.0.0 Win32 Version: 10.0.26100.1 CodeBase:
file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/EventViewer/v4.0_10.0.0.0__31bf3856ad364e35/EventViewer.dll
---------------------------------------- MIGUIControls Assembly Version: 1.0.0.0 Win32 Version: 10.0.26100.3912 CodeBase:
file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/MIGUIControls/v4.0_1.0.0.0__31bf3856ad364e35/MIGUIControls.dll
---------------------------------------- System.ServiceProcess Assembly Version: 4.0.0.0 Win32 Version: 4.8.9032.0 built by: NET481REL1 CodeBase:
* Just-in-Time Debugging Reminder
To activate just-in-time (JIT) debugging, the .config file (machine.config) on your system must be configured with the jitDebugging option enabled in the System.windows.forms section. Additionally, the application needs to be built with debugging features turned on. For instance: when JIT debugging is active, unhandled exceptions will be forwarded to the JIT debugger installed on the machine instead of being managed by this interface.
I believe this issue happened after the system was resolved. Is that right?
Have you executed DISM and SFC to verify the Windows installation is stable?
https://support.microsoft.com/en-us...-w...d86e0ef4ca
Have you checked for malware on this machine?
Could you provide the full specifications for this computer (model and make of every installed part)?
Thank you for your reply.
Have you executed DISM and SFC to verify the system's health?
- I'm performing it now.
Device Nitro ANV15-51
Processor 13th Gen Intel® Core™ i5-13420H 2.10 GHz
Installed RAM 8.00 GB (5.71 GB available)
System type 64-bit OS, x64 processor
Pen and touch No input devices connected
Edition Windows 11 Pro
Version 24H2
Installed on 24/04/2025
OS build 26100.3915
Experience Windows Feature Experience Pack 1000.26100.83.0
https://drive.google.com/file/d/1NkOGmwO...drive_link
Here's a screenshot of the result.
Are you sure you want to proceed? It's okay now, but you might want to run additional tests.
Scan using Malwarebytes or Hitman Pro. A free trial version is enough.
Remove any identified threats.
8: kd> !error 0xc000009a
Error code: (NTSTATUS) 0xc000009a (3221225626) – insufficient system resources to finish the API.
It seems there’s a problem with the ACPI interface (bios).
I recommend opening bios, updating or modifying it, reverting the changes, and then restarting.
You should switch the memory dump type to kernel and supply the kernel memory dump file (memory.dmp).
This will display the hardware the plug-and-play device is attempting to add.
BiosVersion = V1.18
BiosReleaseDate = 10/08/2024
SystemManufacturer = Acer
SystemProductName = Nitro ANV15-51
SystemFamily =
ProcessorNameString = REG_SZ 13th Gen Intel® Core™ i5-13420H
I’ll review the drivers shortly.