BSOD

Sekce pro řešení potíží s BSOD (tedy pády Windows do tzv. modré smrti)

Moderátoři: Mods_senior, BSOD team

Kazuolol
nováček
Příspěvky: 1
Registrován: srpen 22
Pohlaví: Nespecifikováno
Stav:
Offline

BSOD

Příspěvekod Kazuolol » 25 srp 2022 17:01

Dobrý den, poslední dobou se mi dost často stává že mi PC hazí BSOD mohl by mi prosím někdo poradit? přikládám minidumb já se v tom bohužel vůbec nevyznám tak kdyby byla možnost a mohl by mi někdo pomoct co s tím...

Předem děkuji za pomoc
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80353c3d20c, The address that the exception occurred at
Arg3: ffffaa0ef4c59998, Parameter 0 of the exception
Arg4: ffffd480d05fe900, Parameter 1 of the exception

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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: ContextRecord ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5421

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 8832

Key : Analysis.Init.CPU.mSec
Value: 1046

Key : Analysis.Init.Elapsed.mSec
Value: 74331

Key : Analysis.Memory.CommitPeak.Mb
Value: 179

Key : Bugcheck.Code.DumpHeader
Value: 0x1e

Key : Bugcheck.Code.Register
Value: 0x1e

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 082222-6187-01.dmp

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80353c3d20c

BUGCHECK_P3: ffffaa0ef4c59998

BUGCHECK_P4: ffffd480d05fe900

EXCEPTION_PARAMETER1: ffffaa0ef4c59998

EXCEPTION_PARAMETER2: ffffd480d05fe900

WRITE_ADDRESS: fffff8034ff05450: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffd480d05fe900

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: steam.exe

STACK_TEXT:
ffffd480`d05fe048 fffff803`4f766e9b : 00000000`0000001e ffffffff`c0000005 fffff803`53c3d20c ffffaa0e`f4c59998 : nt!KeBugCheckEx
ffffd480`d05fe050 fffff803`4f633856 : ffffd480`d05fe900 fffff803`4f52d525 ffffaa0e`f4c59bd0 fffff803`53c3d20c : nt!KiFatalFilter+0x1f
ffffd480`d05fe090 fffff803`4f5da542 : fffff803`00000001 ffffaa0e`f4c59998 ffffaa0e`f4c55000 ffffaa0e`f4c5b000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffd480`d05fe0d0 fffff803`4f621582 : ffffaa0e`f4c59998 ffffd480`d05fe6e0 ffffd480`d05fe1e0 ffffd480`d05fe1e0 : nt!_C_specific_handler+0xa2
ffffd480`d05fe140 fffff803`4f4de877 : ffffd480`d05fe6e0 fffff803`4f4e4b48 ffffaa0e`f4c59de0 ffffd480`d05fe1e0 : nt!RtlpExecuteHandlerForException+0x12
ffffd480`d05fe170 fffff803`4f4e27c1 : ffffffff`ffffffff ffffaa0e`f4c59a40 ffffaa0e`f4c59a40 ffffd480`d05fe900 : nt!RtlDispatchException+0x2d7
ffffd480`d05fe8d0 fffff803`4f618c52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1b1
ffffd480`d05fefb0 fffff803`4f618c20 : fffff803`4f62aac7 00000000`00000000 00000000`00000000 ffffe682`ffffffff : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffaa0e`f4c59858 fffff803`4f62aac7 : 00000000`00000000 00000000`00000000 ffffe682`ffffffff fffff803`00000001 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffaa0e`f4c59860 fffff803`4f62668f : 00000000`00000010 00000000`00000000 5b92532e`2d401ee7 25994b88`6b2d43fe : nt!KiExceptionDispatch+0x107
ffffaa0e`f4c59a40 fffff803`53c3d20c : fffff803`0017ba3a ffffe682`4fda1000 00000000`00000bb8 fffff803`616cab3d : nt!KiGeneralProtectionFault+0x30f
ffffaa0e`f4c59bd0 fffff803`53c13438 : fffff803`00000000 00000000`00000000 00000000`00000014 fffff803`53f06050 : NETIO!WfpNblInfoInit+0x29dcc
ffffaa0e`f4c59c00 fffff803`53d777d8 : ffffd480`d190548e fffff803`0000000e ffffd480`d18e1e66 00000000`00000000 : NETIO!NetioInitializeNetBufferListAndFirstNetBufferContext+0x78
ffffaa0e`f4c59c30 fffff803`53d773e0 : ffffe682`510144c0 ffffe682`510778a0 ffffe682`4f45cd01 00000000`00000006 : tcpip!FlpValidateNetBufferListChain+0x318
ffffaa0e`f4c59de0 fffff803`4f4e4b48 : 00000000`00000004 fffff803`53d77310 ffffe682`541f3080 00000000`00000002 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xd0
ffffaa0e`f4c59f20 fffff803`4f4e4abd : fffff803`53d77310 ffffaa0e`f4c5a0d0 ffffe682`4ad14010 fffff803`4f619f24 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffaa0e`f4c59f90 fffff803`53d032cd : 00000000`00000000 00001f80`00000200 00000083`db5c0011 ffffe682`638e3100 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffffaa0e`f4c59fd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!NetioExpandKernelStackAndCallout+0x8d


SYMBOL_NAME: NETIO!WfpNblInfoInit+29dcc

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

IMAGE_VERSION: 10.0.22000.832

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 29dcc

FAILURE_BUCKET_ID: AV_NETIO!WfpNblInfoInit

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5e2049af-0bcf-1c4f-2572-dd747a491783}

Followup: MachineOwner

Reklama
Uživatelský avatar
ITCrowd
Tvůrce článků
Guru Level 13.5
Guru Level 13.5
Příspěvky: 23605
Registrován: březen 10
Pohlaví: Muž
Stav:
Offline

Re: BSOD

Příspěvekod ITCrowd » 25 srp 2022 17:16

Vítej na PC-HELP!
1. Je tu sekce BSOD, kam patří i tvůj dotaz.
2. Hned v úvodu sekce je návod: viewtopic.php?f=118&t=129195
3. dokud nedodáš vše, co je požadováno, těžko někdo pomůže.

//přesunuto ze sekce Problémy s HW

//mmm
Zkusili jste to vypnout a zapnout? Problémy řeším pouze v tématech. Do SZ mi proto píšete zbytečně.
Základní diagnostika WiFi Jak na diagnostiku sítě Router jako switch Proč je nesmysl chtít router s velkým dosahem Vybíráme router


  • Mohlo by vás zajímat
    Odpovědi
    Zobrazení
    Poslední příspěvek
  • bsod při hře Příloha(y)
    od matesfox » 06 led 2024 12:46 » v BSOD (Blue Screen Of Death)
    4
    1609
    od matesfox Zobrazit poslední příspěvek
    13 led 2024 19:41
  • Náhodné BSOD Příloha(y)
    od TheSalon112 » 21 úno 2024 18:32 » v BSOD (Blue Screen Of Death)
    0
    496
    od TheSalon112 Zobrazit poslední příspěvek
    21 úno 2024 18:32
  • Pád PC po spuštění hry be BSOD
    od Radoozek » 07 pro 2023 15:00 » v Problémy s hardwarem
    4
    1436
    od Radoozek Zobrazit poslední příspěvek
    08 pro 2023 16:45
  • BSOD problémy (několik) Příloha(y)
    od inripuff » 19 úno 2024 15:06 » v BSOD (Blue Screen Of Death)
    10
    2083
    od inripuff Zobrazit poslední příspěvek
    27 úno 2024 14:18
  • Zamrznutí obrazu a BSOD Příloha(y)
    od zele44 » 02 úno 2024 15:10 » v BSOD (Blue Screen Of Death)
    5
    1145
    od zele44 Zobrazit poslední příspěvek
    03 úno 2024 10:14

Zpět na “BSOD (Blue Screen Of Death)”

Kdo je online

Uživatelé prohlížející si toto fórum: Žádní registrovaní uživatelé a 2 hosti