Windows 10: About Windows Crash

Hey guysthese days my Windows crashes a lot . can anyone help me?



Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Windows\Minidump\121920-10234-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP 16 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff804`4ba00000 PsLoadedModuleList = 0xfffff804`4c62a2b0

Debug session time: Sat Dec 19 18:46:12.534 2020 UTC + 8:00

System Uptime: 1 days 3:54:46.953

Loading Kernel Symbols

..



Press ctrl-c cdb, kd, ntsd or ctrl-break windbg to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.



.............................................................

................................................................

................................................................

..............................................

Loading User Symbols

Loading unloaded module list

...............

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff804`4bdf5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8b01`5756be20=0000000000000133

13: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



DPC_WATCHDOG_VIOLATION 133

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

component can usually be identified with a stack trace.

Arg2: 0000000000000501, The DPC time count in ticks.

Arg3: 0000000000000500, The DPC time allotment in ticks.

Arg4: fffff8044c6fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout



Debugging Details:

------------------



*** WARNING: Unable to verify timestamp for iaStorAC.sys

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: TickPeriods ***

*** ***

*************************************************************************



KEY_VALUES_STRING: 1



Key : Analysis.CPU.mSec

Value: 2436



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on NERXCET



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.mSec

Value: 66366



Key : Analysis.Memory.CommitPeak.Mb

Value: 82



Key : Analysis.System

Value: CreateObject





ADDITIONAL_XML: 1



OS_BUILD_LAYERS: 1



DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



BUGCHECK_CODE: 133



BUGCHECK_P1: 0



BUGCHECK_P2: 501



BUGCHECK_P3: 500



BUGCHECK_P4: fffff8044c6fa320



DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: System



STACK_TEXT:

ffff8b01`5756be18 fffff804`4be3a988 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffff8b01`5756be20 fffff804`4bc6f9a3 : 00004cf6`3c75c2a3 ffff8b01`57552180 00000000`00000000 ffff8b01`57552180 : nt!KeAccumulateTicks+0x1c8788

ffff8b01`5756be80 fffff804`4bc6f48a : ffffe387`e3d1c900 ffff8605`4b0f6e20 00000000`00000200 00000000`000070c8 : nt!KeClockInterruptNotify+0x453

ffff8b01`5756bf30 fffff804`4bd27ef5 : ffffe387`e3d1c900 00000000`00000000 00000000`00000000 ffff94b0`7eb42d07 : nt!HalpTimerClockIpiRoutine+0x1a

ffff8b01`5756bf60 fffff804`4bdf722a : ffff8605`4b0f6e20 ffffe387`e3d1c900 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

ffff8b01`5756bfb0 fffff804`4bdf7797 : 00000000`00000000 00001f80`002002b0 000000e9`f6e1d418 fffff804`502062b0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffff8605`4b0f6da0 fffff804`50136110 : fffff804`50150035 000000e9`fcd7b518 ffffe388`023aefb0 ffff8605`4b0f7028 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffff8605`4b0f6f38 fffff804`50150035 : 000000e9`fcd7b518 ffffe388`023aefb0 ffff8605`4b0f7028 fffff804`4bd3baed : iaStorAC+0xb6110

ffff8605`4b0f6f40 000000e9`fcd7b518 : ffffe388`023aefb0 ffff8605`4b0f7028 fffff804`4bd3baed 00000000`00000000 : iaStorAC+0xd0035

ffff8605`4b0f6f48 ffffe388`023aefb0 : ffff8605`4b0f7028 fffff804`4bd3baed 00000000`00000000 ffffe387`e89c61a0 : 0x000000e9`fcd7b518

ffff8605`4b0f6f50 ffff8605`4b0f7028 : fffff804`4bd3baed 00000000`00000000 ffffe387`e89c61a0 00000004`00000019 : 0xffffe388`023aefb0

ffff8605`4b0f6f58 fffff804`4bd3baed : 00000000`00000000 ffffe387`e89c61a0 00000004`00000019 000000e9`f6e43672 : 0xffff8605`4b0f7028

ffff8605`4b0f6f60 ffffe388`02593fe8 : 00000000`00000002 ffffe387`00000001 00000000`00000000 fffff804`501b2020 : nt!MmGetPhysicalAddress+0x1d

ffff8605`4b0f6f90 00000000`00000002 : ffffe387`00000001 00000000`00000000 fffff804`501b2020 00000000`00000001 : 0xffffe388`02593fe8

ffff8605`4b0f6f98 ffffe387`00000001 : 00000000`00000000 fffff804`501b2020 00000000`00000001 fffff804`501b2020 : 0x2

ffff8605`4b0f6fa0 00000000`00000000 : fffff804`501b2020 00000000`00000001 fffff804`501b2020 ffff8605`4b0f70a0 : 0xffffe387`00000001





SYMBOL_NAME: iaStorAC+b6110



MODULE_NAME: iaStorAC



IMAGE_NAME: iaStorAC.sys



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: b6110



FAILURE_BUCKET_ID: 0x133_DPC_iaStorAC!unknown_function



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {6959f419-2954-fbde-7328-35f9ba64ee7a}



Followup: MachineOwner

---------



13: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



DPC_WATCHDOG_VIOLATION 133

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

component can usually be identified with a stack trace.

Arg2: 0000000000000501, The DPC time count in ticks.

Arg3: 0000000000000500, The DPC time allotment in ticks.

Arg4: fffff8044c6fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout



Debugging Details:

------------------



*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files such as the public OS symbols do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: TickPeriods ***

*** ***

*************************************************************************



KEY_VALUES_STRING: 1



Key : Analysis.CPU.mSec

Value: 2000



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on NERXCET



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.mSec

Value: 1996



Key : Analysis.Memory.CommitPeak.Mb

Value: 82



Key : Analysis.System

Value: CreateObject





ADDITIONAL_XML: 1



OS_BUILD_LAYERS: 1



DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



BUGCHECK_CODE: 133



BUGCHECK_P1: 0



BUGCHECK_P2: 501



BUGCHECK_P3: 500



BUGCHECK_P4: fffff8044c6fa320



DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: System



STACK_TEXT:

ffff8b01`5756be18 fffff804`4be3a988 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffff8b01`5756be20 fffff804`4bc6f9a3 : 00004cf6`3c75c2a3 ffff8b01`57552180 00000000`00000000 ffff8b01`57552180 : nt!KeAccumulateTicks+0x1c8788

ffff8b01`5756be80 fffff804`4bc6f48a : ffffe387`e3d1c900 ffff8605`4b0f6e20 00000000`00000200 00000000`000070c8 : nt!KeClockInterruptNotify+0x453

ffff8b01`5756bf30 fffff804`4bd27ef5 : ffffe387`e3d1c900 00000000`00000000 00000000`00000000 ffff94b0`7eb42d07 : nt!HalpTimerClockIpiRoutine+0x1a

ffff8b01`5756bf60 fffff804`4bdf722a : ffff8605`4b0f6e20 ffffe387`e3d1c900 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

ffff8b01`5756bfb0 fffff804`4bdf7797 : 00000000`00000000 00001f80`002002b0 000000e9`f6e1d418 fffff804`502062b0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffff8605`4b0f6da0 fffff804`50136110 : fffff804`50150035 000000e9`fcd7b518 ffffe388`023aefb0 ffff8605`4b0f7028 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffff8605`4b0f6f38 fffff804`50150035 : 000000e9`fcd7b518 ffffe388`023aefb0 ffff8605`4b0f7028 fffff804`4bd3baed : iaStorAC+0xb6110

ffff8605`4b0f6f40 000000e9`fcd7b518 : ffffe388`023aefb0 ffff8605`4b0f7028 fffff804`4bd3baed 00000000`00000000 : iaStorAC+0xd0035

ffff8605`4b0f6f48 ffffe388`023aefb0 : ffff8605`4b0f7028 fffff804`4bd3baed 00000000`00000000 ffffe387`e89c61a0 : 0x000000e9`fcd7b518

ffff8605`4b0f6f50 ffff8605`4b0f7028 : fffff804`4bd3baed 00000000`00000000 ffffe387`e89c61a0 00000004`00000019 : 0xffffe388`023aefb0

ffff8605`4b0f6f58 fffff804`4bd3baed : 00000000`00000000 ffffe387`e89c61a0 00000004`00000019 000000e9`f6e43672 : 0xffff8605`4b0f7028

ffff8605`4b0f6f60 ffffe388`02593fe8 : 00000000`00000002 ffffe387`00000001 00000000`00000000 fffff804`501b2020 : nt!MmGetPhysicalAddress+0x1d

ffff8605`4b0f6f90 00000000`00000002 : ffffe387`00000001 00000000`00000000 fffff804`501b2020 00000000`00000001 : 0xffffe388`02593fe8

ffff8605`4b0f6f98 ffffe387`00000001 : 00000000`00000000 fffff804`501b2020 00000000`00000001 fffff804`501b2020 : 0x2

ffff8605`4b0f6fa0 00000000`00000000 : fffff804`501b2020 00000000`00000001 fffff804`501b2020 ffff8605`4b0f70a0 : 0xffffe387`00000001





SYMBOL_NAME: iaStorAC+b6110



MODULE_NAME: iaStorAC



IMAGE_NAME: iaStorAC.sys



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: b6110



FAILURE_BUCKET_ID: 0x133_DPC_iaStorAC!unknown_function



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {6959f419-2954-fbde-7328-35f9ba64ee7a}



Followup: MachineOwner

---------



another crash:

Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\122620-13093-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 16 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalMachine Name:Kernel base = 0xfffff800`41c00000 PsLoadedModuleList = 0xfffff800`4282a2b0Debug session time: Sat Dec 26 18:39:21.048 2020 UTC + 8:00System Uptime: 6 days 18:47:12.977Loading Kernel Symbols..Press ctrl-c cdb, kd, ntsd or ctrl-break windbg to abort symbol loads that take too long.Run !sym noisy before .reload to track down problems loading symbols..................................................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`41ff5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff606`2e856b90=000000000000000a3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL d1An attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: 00000000000000d0, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff8004795d5b5, address which referenced memoryDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3562 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on NERXCET Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 111740 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: d1BUGCHECK_P1: d0BUGCHECK_P2: 2BUGCHECK_P3: 0BUGCHECK_P4: fffff8004795d5b5READ_ADDRESS: fffff800428fa390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8004280f330: Unable to get Flags value from nt!KdVersionBlockfffff8004280f330: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse 00000000000000d0 CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemDPC_STACK_BASE: FFFFF6062E857FB0TRAP_FRAME: fffff6062e856cd0 -- .trap 0xfffff6062e856cd0NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=00000000000001e8 rbx=0000000000000000 rcx=ffffac83bdcc1c20rdx=fffff606358d77f0 rsi=0000000000000000 rdi=0000000000000000rip=fffff8004795d5b5 rsp=fffff6062e856e60 rbp=ffffac83bdcc1b50 r8=ffffac83bfc90008 r9=fffff6062e856f10 r10=fffff606358d75c0r11=fffff6062e856e10 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz ac pe cyiaStorAC+0xdd5b5:fffff800`4795d5b5 488b86d0000000 mov rax,qword ptr [rsi+0D0h] ds:00000000`000000d0=????????????????Resetting default scopeSTACK_TEXT: fffff606`2e856b88 fffff800`42007769 : 00000000`0000000a 00000000`000000d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckExfffff606`2e856b90 fffff800`42003a69 : 00000000`0000002a 00000000`00000000 00000000`00000034 00000000`0000000c : nt!KiBugCheckDispatch+0x69fffff606`2e856cd0 fffff800`4795d5b5 : fffff606`2e856eb0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469fffff606`2e856e60 fffff606`2e856eb0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : iaStorAC+0xdd5b5fffff606`2e856e68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`478859e2 : 0xfffff606`2e856eb0SYMBOL_NAME: iaStorAC+dd5b5MODULE_NAME: iaStorACIMAGE_NAME: iaStorAC.sysSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: dd5b5FAILURE_BUCKET_ID: AV_iaStorAC!unknown_functionOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {2c48c538-0bdc-1937-76bb-851b68345fca}Followup: MachineOwner---------

:)

 

all games crash!

I suggest you run rthdribl > http://www.daionet.gr.jp/~masa/archives/rthdribl_1_2.zip
Increase the window size step by step and watch your vga temps permanently.
What happens?
If it crashes, run at stock speeds as suggested before and retry.

P.S.: When your system locks, does the display signal turn off after a time?
Stuttering sound or no sound at all when freezing?
What X1800XT model do you own exactly?

 

all games crash!

ive watch my temps and both the cpu and gpu are within normal ranges. when it freezes it simply freezes the image and stops the sound. i must reboot to get back to windows.

 

windows xp installation and dual core am

could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx