Ewan ko kung bakit ganyan sya pero hindi naman palaging ganyan mga 2-3 times a day lng.
Attachments
-
You do not have permission to view the full content of this post. Log in or register now.
Done eto syaupdate mo mga driver the rig mo.
Pwede ka din gumamit ng whocrashed dump analyzer.
Computer name: | DESKTOP-CL3ER62 |
Windows version: | Windows 11, 10.0, version 2009, build: 22000 (x64) |
Windows dir: | C:\Windows |
Hardware: | MS-7817, MSI, H81M-E33 (MS-7817) |
CPU: | GenuineIntel Intel(R) Core(TM) i5-4690S CPU @ 3.20GHz 8664, level: 6 |
Processor count: | 4 logical processors, active mask: 15 |
RAM: | 15814.0MB |
Crash dump file: | C:\Windows\Minidump\072122-10406-01.dmp (Minidump) |
Bugcheck code: | 0xD1(0xA, 0x2, 0x0, 0xFFFFF8079C6C5F40) |
Bugcheck name: | You do not have permission to view the full content of this post. Log in or register now. |
Bug check description: | This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
Crash dump file: | C:\Windows\MEMORY.DMP (Kernel memory dump) |
Bugcheck code: | 0xD1(0xA, 0x2, 0x0, 0xFFFFF8079C6C5F40) |
Bugcheck name: | You do not have permission to view the full content of this post. Log in or register now. |
Bug check description: | This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
Crash dump file: | C:\Windows\Minidump\071922-12578-01.dmp (Minidump) |
Bugcheck code: | 0xD1(0xA, 0x2, 0x0, 0xFFFFF8004C115F40) |
Bugcheck name: | You do not have permission to view the full content of this post. Log in or register now. |
Bug check description: | This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
Crash dump file: | C:\Windows\Minidump\071922-36437-01.dmp (Minidump) |
Bugcheck code: | 0xD1(0xA, 0x2, 0x0, 0xFFFFF80699495F40) |
Bugcheck name: | You do not have permission to view the full content of this post. Log in or register now. |
Bug check description: | This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
Crash dump file: | C:\Windows\Minidump\071722-8890-01.dmp (Minidump) |
Bugcheck code: | 0xA(0x14, 0x2, 0x0, 0xFFFFF8013728F294) |
Bugcheck name: | You do not have permission to view the full content of this post. Log in or register now. |
Bug check description: | This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. |
Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
Crash dump file: | C:\Windows\Minidump\071722-15562-01.dmp (Minidump) |
Bugcheck code: | 0xA(0x14, 0x2, 0x0, 0xFFFFF80148A8F294) |
Bugcheck name: | You do not have permission to view the full content of this post. Log in or register now. |
Bug check description: | This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. |
Analysis: | This is a typical software problem. Most likely this is caused by a bug in a driver. |
Crash dump file: | C:\Windows\LiveKernelReports\WATCHDOG-20220707-2326.dmp (Kernel memory dump) |
Bugcheck code: | 0x193(0x815, 0x3, 0xFFFF800E2149B080, 0x0) |
Bugcheck name: | You do not have permission to view the full content of this post. Log in or register now. |
Bug check description: | A livedump triggered by dxgkrnl occurred. You may have problems with your graphics driver or hardware. |
Analysis: | This is a video related crash. |
pocket wifi yung gamit na nakakonnect via usbTS, naka-USB teethering ka para makapag-internet?
[Hidden content]
nopeBlue screen of death na kagad boot?