Blasius Pallhuber
Herzlich willkommen
Hallo, ich wäre dankbar für Hilfe bei der Beseitigung eines Startproblems; ich bekomme plötzlich nach dem Windows Symbol eine Blue screen.
Bin unerfahren in der Reparatur von so etwas, habe aber erstmal folgendes probiert:
1.) Einige Hardware entfernt, welche entbehrlich ist.
2. ) Sitz von Karten, Kabeln etc geprüft. Sieht alles normal aus.
3.) safe mode probiert. Im safe mode stürtzt der Computer nicht ab, ich komme rein und nicht sieht ungewöhnlich aus.
4.) Folgendes ausgelesen:
Mir fehlt die Fachkenntnis, um daraus etwas zu schließen. Wenn jemand sich hier auskennt, es wäre toll, wenn sich ein Hinweis zur Behebung des Problems ergeben würde. Danke für jeden Ratschlag!
---------
Bin unerfahren in der Reparatur von so etwas, habe aber erstmal folgendes probiert:
1.) Einige Hardware entfernt, welche entbehrlich ist.
2. ) Sitz von Karten, Kabeln etc geprüft. Sieht alles normal aus.
3.) safe mode probiert. Im safe mode stürtzt der Computer nicht ab, ich komme rein und nicht sieht ungewöhnlich aus.
4.) Folgendes ausgelesen:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.578 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46
Microsoft (R) Windows Debugger Version 10.0.29482.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [J:\Minidump\010826-6224-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 7601.24384.amd64fre.win7sp1_ldr_escrow.190220-1800
Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`03452c90
Debug session time: Thu Jan 8 21:20:56.866 2026 (UTC + 1:00)
System Uptime: 0 days 0:00:06.803
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`032acba0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`035bcbf0=000000000000000a
3: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032b4cc0, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for m4cxwin764.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1562
Key : Analysis.Elapsed.mSec
Value: 8384
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 9
Key : Analysis.Init.CPU.mSec
Value: 1546
Key : Analysis.Init.Elapsed.mSec
Value: 74134
Key : Analysis.Memory.CommitPeak.Mb
Value: 65
Key : Analysis.Version.DbgEng
Value: 10.0.29482.1003
Key : Analysis.Version.Description
Value: 10.2509.29.03 amd64fre
Key : Analysis.Version.Ext
Value: 1.2509.29.3
Key : Bugcheck.Code.LegacyAPI
Value: 0xa
Key : Bugcheck.Code.TargetModel
Value: 0xa
Key : Failure.Bucket
Value: 0xA_m4cxwin764!unknown_function
Key : Failure.Exception.IP.Address
Value: 0xfffff800032b4cc0
Key : Failure.Exception.IP.Module
Value: nt
Key : Failure.Exception.IP.Offset
Value: 0x9bcc0
Key : Failure.Hash
Value: {3e1dd499-0a52-7402-4452-e73bec897b89}
Key : Faulting.IP.Type
Value: Paged
Key : Hypervisor.Flags.Value
Value: 0
Key : Hypervisor.Flags.ValueHex
Value: 0x0
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Version
Value: 7.1.7601.24384
BUGCHECK_CODE: a
BUGCHECK_P1: 0
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff800032b4cc0
FILE_IN_CAB: 010826-6224-01.dmp
FAULTING_THREAD: fffffa8012876040
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800034b6300
GetUlongPtrFromAddress: unable to read from fffff800034b62f0
GetUlongPtrFromAddress: unable to read from fffff800034b64a8
0000000000000000
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
IP_IN_PAGED_CODE:
nt!ExInterlockedRemoveHeadList+30
fffff800`032b4cc0 4c8b00 mov r8,qword ptr [rax]
STACK_TEXT:
fffff880`035bcbe8 fffff800`032baf69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`035bcbf0 fffff800`032b8d88 : 00000000`00000000 00000000`00000000 fffffa80`12877100 fffffa80`14478000 : nt!KiBugCheckDispatch+0x69
fffff880`035bcd30 fffff800`032b4cc0 : 00000000`00000246 fffff880`040a2de7 00000000`00000052 fffff800`0328dc16 : nt!KiPageFault+0x448
fffff880`035bcec0 fffff880`040a2de7 : 00000000`00000052 fffff800`0328dc16 ffff01f3`3706fecb 00000000`e0070066 : nt!ExInterlockedRemoveHeadList+0x30
fffff880`035bced0 00000000`00000052 : fffff800`0328dc16 ffff01f3`3706fecb 00000000`e0070066 fffffa80`14478f48 : m4cxwin764+0x15de7
fffff880`035bced8 fffff800`0328dc16 : ffff01f3`3706fecb 00000000`e0070066 fffffa80`14478f48 fffffa80`14478f58 : 0x52
fffff880`035bcee0 00000000`00000001 : 00000000`00000000 00000000`00000000 fffffa80`14478000 fffff880`040965c4 : nt!IoAllocateErrorLogEntry+0x26
fffff880`035bcf10 00000000`00000000 : 00000000`00000000 fffffa80`14478000 fffff880`040965c4 fffffa80`14478000 : 0x1
SYMBOL_NAME: m4cxwin764+15de7
MODULE_NAME: m4cxwin764
IMAGE_NAME: m4cxwin764.sys
STACK_COMMAND: .process /r /p 0xfffffa8012863b00; .thread 0xfffffa8012876040 ; kb
BUCKET_ID_FUNC_OFFSET: 15de7
FAILURE_BUCKET_ID: 0xA_m4cxwin764!unknown_function
OS_VERSION: 7.1.7601.24384
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {3e1dd499-0a52-7402-4452-e73bec897b89}
Followup: MachineOwner
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.578 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46
Microsoft (R) Windows Debugger Version 10.0.29482.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [J:\Minidump\010826-6224-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 7601.24384.amd64fre.win7sp1_ldr_escrow.190220-1800
Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`03452c90
Debug session time: Thu Jan 8 21:20:56.866 2026 (UTC + 1:00)
System Uptime: 0 days 0:00:06.803
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`032acba0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`035bcbf0=000000000000000a
3: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032b4cc0, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for m4cxwin764.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1562
Key : Analysis.Elapsed.mSec
Value: 8384
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 9
Key : Analysis.Init.CPU.mSec
Value: 1546
Key : Analysis.Init.Elapsed.mSec
Value: 74134
Key : Analysis.Memory.CommitPeak.Mb
Value: 65
Key : Analysis.Version.DbgEng
Value: 10.0.29482.1003
Key : Analysis.Version.Description
Value: 10.2509.29.03 amd64fre
Key : Analysis.Version.Ext
Value: 1.2509.29.3
Key : Bugcheck.Code.LegacyAPI
Value: 0xa
Key : Bugcheck.Code.TargetModel
Value: 0xa
Key : Failure.Bucket
Value: 0xA_m4cxwin764!unknown_function
Key : Failure.Exception.IP.Address
Value: 0xfffff800032b4cc0
Key : Failure.Exception.IP.Module
Value: nt
Key : Failure.Exception.IP.Offset
Value: 0x9bcc0
Key : Failure.Hash
Value: {3e1dd499-0a52-7402-4452-e73bec897b89}
Key : Faulting.IP.Type
Value: Paged
Key : Hypervisor.Flags.Value
Value: 0
Key : Hypervisor.Flags.ValueHex
Value: 0x0
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Version
Value: 7.1.7601.24384
BUGCHECK_CODE: a
BUGCHECK_P1: 0
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff800032b4cc0
FILE_IN_CAB: 010826-6224-01.dmp
FAULTING_THREAD: fffffa8012876040
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800034b6300
GetUlongPtrFromAddress: unable to read from fffff800034b62f0
GetUlongPtrFromAddress: unable to read from fffff800034b64a8
0000000000000000
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
IP_IN_PAGED_CODE:
nt!ExInterlockedRemoveHeadList+30
fffff800`032b4cc0 4c8b00 mov r8,qword ptr [rax]
STACK_TEXT:
fffff880`035bcbe8 fffff800`032baf69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`035bcbf0 fffff800`032b8d88 : 00000000`00000000 00000000`00000000 fffffa80`12877100 fffffa80`14478000 : nt!KiBugCheckDispatch+0x69
fffff880`035bcd30 fffff800`032b4cc0 : 00000000`00000246 fffff880`040a2de7 00000000`00000052 fffff800`0328dc16 : nt!KiPageFault+0x448
fffff880`035bcec0 fffff880`040a2de7 : 00000000`00000052 fffff800`0328dc16 ffff01f3`3706fecb 00000000`e0070066 : nt!ExInterlockedRemoveHeadList+0x30
fffff880`035bced0 00000000`00000052 : fffff800`0328dc16 ffff01f3`3706fecb 00000000`e0070066 fffffa80`14478f48 : m4cxwin764+0x15de7
fffff880`035bced8 fffff800`0328dc16 : ffff01f3`3706fecb 00000000`e0070066 fffffa80`14478f48 fffffa80`14478f58 : 0x52
fffff880`035bcee0 00000000`00000001 : 00000000`00000000 00000000`00000000 fffffa80`14478000 fffff880`040965c4 : nt!IoAllocateErrorLogEntry+0x26
fffff880`035bcf10 00000000`00000000 : 00000000`00000000 fffffa80`14478000 fffff880`040965c4 fffffa80`14478000 : 0x1
SYMBOL_NAME: m4cxwin764+15de7
MODULE_NAME: m4cxwin764
IMAGE_NAME: m4cxwin764.sys
STACK_COMMAND: .process /r /p 0xfffffa8012863b00; .thread 0xfffffa8012876040 ; kb
BUCKET_ID_FUNC_OFFSET: 15de7
FAILURE_BUCKET_ID: 0xA_m4cxwin764!unknown_function
OS_VERSION: 7.1.7601.24384
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {3e1dd499-0a52-7402-4452-e73bec897b89}
Followup: MachineOwner
Mir fehlt die Fachkenntnis, um daraus etwas zu schließen. Wenn jemand sich hier auskennt, es wäre toll, wenn sich ein Hinweis zur Behebung des Problems ergeben würde. Danke für jeden Ratschlag!
---------
Zuletzt bearbeitet:
