Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
Anyway, that being said, every time you restart or do a cold boot Windows 10, your registry gets cleaned up autopmatically during startup.
It'll give you a better idea of what exactly caused the blue screen.
http://www.resplendence.com/whocrashed
-
CCleaner by itself should not cause such a bluescreen, so i dont think that was the specific cause.
-
If you have more than one Antivirus, you only need one. Multiple AVs can cause problems and performance issues.
a critical structure corruption means window detected that one of its files has been modified or the data that one of its files owns in memory has been modified.
So it has something to do with the ntoskrnl execute file?
Also, outside of CCleaner, could defragmenting an SSD also cause this issue?
Could that be a symptom of Meltdown?
OP as i said
download WhoCrashed and analyze the crash dump, itll tell you what caused the bluescreen
Also, I think Nirsoft makes a BSOD detector as well, but I'm not sure if it's up to date.
On Tue 2/20/2018 12:49:42 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022018-38296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)
Bugcheck code: 0x109 (0xA39FE3E5C94F1748, 0xB3B6F06C1BD0C447, 0xFFFFF8012E570000, 0x19)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
Also, when it comes to driver software, the only one you need is Driver Booster from www.iobit.com there are maybe 1 or 2 other decent ones, but thats the 1 i use and have used on other PCs to resolve issues.
Before you decide to format give that a try, see what happens.
Also, for the hell of it Remove 1 RAM stick, use the PC as normal and see if it bluescreens, if so, do the same with the other RAM stick (assuming you have 2 or more)
You'll find out if its RAM related that way, a little more annoying to do but more accurate than doing a memtest in a sense.
Naturally, backup any files you want to safe to a different device before you decide to format
You know...we got into a hole debate (which was deleted by he way due to certain stalker interference) about me stating that CCleaner messes with your rtegistry...you initially said it does not...but now say it does not mess with the registry if you do not use that feature.
Well no kidding it doesn't mess up the registry if you do not use its registry cleaning feature.....Those links I posted...that is what the complaint was...that it messes up the Wiondows 10 registry.