Merhaba.Merhabalar,
Bilgisayarım kendi halinde açıkken hatayı alıp reslediğini farkettim. Minidump dosyasını bırakıyorum, teşekkürler.
CRITICAL_STRUCTURE_CORRUPTION (109)
This BugCheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fdf616f38d57b, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 0eee5fe2ef982ae7, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region,
STACK_TEXT:
ffff8b87`24d6fe28 00000000`00000000 : 00000000`00000109 a39fdf61`6f38d57b 00000000`00000000 0eee5fe2`ef982ae7 : nt!KeBugCheckEx
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x109_101_ANALYSIS_INCONCLUSIVE!unknown_function
6: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 133909337167593033
PnpEventInformation: 6
PnpEventInProgress : 0
PnpProblemCode : 10
PnpVetoType : 0
DeviceId : USB\VID_2357&PID_0109\6&34ced5b7&0&8
VetoString :
Merhaba.Merhabalar,
Bilgisayarım kendi halinde açıkken hatayı alıp reslediğini farkettim. Minidump dosyasını bırakıyorum, teşekkürler.
CRITICAL_STRUCTURE_CORRUPTION (109)
This BugCheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fdf616f38d57b, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 0eee5fe2ef982ae7, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region,
STACK_TEXT:
ffff8b87`24d6fe28 00000000`00000000 : 00000000`00000109 a39fdf61`6f38d57b 00000000`00000000 0eee5fe2`ef982ae7 : nt!KeBugCheckEx
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x109_101_ANALYSIS_INCONCLUSIVE!unknown_function
6: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 133909337167593033
PnpEventInformation: 6
PnpEventInProgress : 0
PnpProblemCode : 10
PnpVetoType : 0
DeviceId : USB\VID_2357&PID_0109\6&34ced5b7&0&8
VetoString :Evet sistemim bu şekilde ve bahsettiğiniz Wi-Fi alıcısını kullanmaktayım. Geçtiğimiz aylarda yine bu alıcıyla alakalı başka mavi ekran hataları da almaktaydım uzun bi süredir almamıştım sorun çözüldü zannettim, bugüne kadarmış. Alıcıyı ortadan kaldırarak sorunu çözüyorum sanırım
