Log Name: Application
Source: Windows Error Reporting
Date: 22/04/2025 13:10:34
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Tedrow
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\042223-42260-01.dmp C:\Users\David\AppData\Local\Temp\WER-335589-0.sysdata.xml C:\Users\David\AppData\Local\Temp\WERE6D5.tmp.WERInternalMetadata.xml

These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue
\Kernel_0_0_cab_0379ea4e

Analysis symbol:
Rechecking for solution: 0
Report Id: 042223-42260-01
Report Status: 2051
Hashed bucket:
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2025-04-22T12:10:34.2472900Z" />
<EventRecordID>89057</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Tedrow</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>BlueScreen</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Windows\Minidump\042223-42260-01.dmp C:\Users\David\AppData\Local\Temp\WER-335589-0.sysdata.xml C:\Users\David\AppData\Local\Temp\WERE6D5.tmp.WERInternalMetadata.xml</
Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue \Kernel_0_0_cab_0379ea4e</Data>
<Data>
</Data>
<Data>0</Data>
<Data>042223-42260-01</Data>
<Data>2051</Data>
<Data>
</Data>
<Data>0</Data>
</EventData>
</Event>

This is a text copy from the function in the event viewer.
I haven't seen much of interest but this seems to be reported just before
the PC powers off.
There is no Blue Screen stop.
Just PSU off.

Anyone have an idea about what is going on?

TIA


Dave R

--
AMD FX-6300 in GA-990X-Gaming SLI-CF running Windows 10 x64

--
This email has been checked for viruses by Avast antivirus software. www.avast.com

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

David wrote:

C:\Windows\Minidump\042223-42260-01.dmp C:\Users\David\AppData\Local\Temp\WER-335589-0.sysdata.xml C:\Users\David\AppData\Local\Temp\WERE6D5.tmp.WERInternalMetadata.xml

You'll need to install the debugger and probably also symbol files corresponding to the version of Windows you're running, it's been a
while since I needed to do that ...

<https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 22 Apr 2025 17:22:56 +0100, Andy Burns wrote:

David wrote:

C:\Windows\Minidump\042223-42260-01.dmp
C:\Users\David\AppData\Local\Temp\WER-335589-0.sysdata.xml
C:\Users\David\AppData\Local\Temp\WERE6D5.tmp.WERInternalMetadata.xml

You'll need to install the debugger and probably also symbol files corresponding to the version of Windows you're running, it's been a
while since I needed to do that ...

<https://learn.microsoft.com/en-us/troubleshoot/windows-client/

performance/read-small-memory-dump-file>

Thanks - will do soon.

My main issue is that all the on line help seems to be aimed at finding
the dump files and error logs after a blue screen has halted the PC.

I am coming from the opposite direction.
I don't get a blue screen, the system just powers off.
However there does seem to be a blue screen event (twice) in the Windows Application Log around the time of the halt.

Cheers



Dave R

--
AMD FX-6300 in GA-990X-Gaming SLI-CF running Windows 10 x64

--
This email has been checked for viruses by Avast antivirus software. www.avast.com

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

David <wibble@btinternet.com> wrote:

On Tue, 22 Apr 2025 17:22:56 +0100, Andy Burns wrote:

David wrote:

C:\Windows\Minidump\042223-42260-01.dmp
C:\Users\David\AppData\Local\Temp\WER-335589-0.sysdata.xml
C:\Users\David\AppData\Local\Temp\WERE6D5.tmp.WERInternalMetadata.xml

You'll need to install the debugger and probably also symbol files corresponding to the version of Windows you're running, it's been a
while since I needed to do that ...

<https://learn.microsoft.com/en-us/troubleshoot/windows-client/

performance/read-small-memory-dump-file>

Thanks - will do soon.

My main issue is that all the on line help seems to be aimed at finding
the dump files and error logs after a blue screen has halted the PC.

I am coming from the opposite direction.
I don't get a blue screen, the system just powers off.
However there does seem to be a blue screen event (twice) in the Windows Application Log around the time of the halt.

I don't think that's much different. A BSOD is called a BugCheck in Windows terminology. When you get a BugCheck the default behaviour is to reboot
(can be controlled in 'Startup and Recovery' settings): https://www.tenforums.com/tutorials/69012-enable-disable-bsod-automatic-restart-windows-10-a.html

I don't think there's an option to power off, but maybe it does that if the reboot fails.

The trail this leaves is shown in the log, and to debug it is the same as
you'd do for a BSOD. You can set it to leave a more verbose memory dump
that can be inspected with a debugger like WinDbg: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/crash-dump-files

However probably all you want is to know what driver or program caused the crash. I hope you shouldn't need to go too deep to find that out.

Theo

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)