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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
it did not help
Therefore as mentioned above the SFC /SCANNOW will scan and repair your Windows system files from corruption, if that's the case.
However, another possibility is a virus infection, trying to rootkit your Windows OS. Windows will be attempting to security block it's access which inturn causes the crashing to occur. A malicious application or virus is trying to access the Kernel core of Windows.
It might not be malicious, which in that case, could be your graphic card drivers, encryption software, anti-virus scanner, video codex, or similar drivers which also attempt to access the Windows core. Even faulty hardware or their device drivers.
You should be able to see a "LoadedModule" path - this should point you directly to it.
Start > Run > Type "Event Viewer" without the quotes and select it from the list.
Under Event Viewer (Local) > Custom Views > Administrative Events
Look for any red errors and find their root causes (Faulting module path). It should provide you information as you provided in the crash log, but hopefully some additional details.
Scan your PC with something like Spybot to ensure it's clean of malware:
http://www.safer-networking.org/mirrors/
Those should be your two starting points.
Such as these:
Malwarebytes Anti-Malware[www.malwarebytes.org] < Don't click to activate the 14-day Trial during install. That is optional and if needed u can activate that at a later time.
Malwarebytes Anti-Exploit[downloads.malwarebytes.org]
Malwarebytes Anti-Rootkit [downloads.malwarebytes.org]
c:\Win\syswow64\KERNELBASE.dll. over and over again. I Have Kaspersky anti-virus and iobit and both say my pc is clean. Is there anything other than a Windows reinstall I can do ?
I've seen windows have issues with files on bad sectors - windows will load but you get constant errors.
http://www.sevenforums.com/tutorials/179159-troubleshoot-application-conflicts-performing-clean-startup.html
Left click and Run as Administrator (I know it was mentioned about, but just make sure it's run under an admin-elevated command prompt)
Type "SFC /scannow" (without the quotes)
If that doesn't repair, do all these command (in order / also under the admin command prompt):
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
It will grab an online image of your Windows from Microsoft to compare/repair yours. It might save you a reinstall.
- scanning might take a while, give it time to complete
ps: Also "c:\Win\syswow64\KERNELBASE.dll" you just typed shorthand right? It's under your Windows folder directory in the correct location?
Make sure there's one active real-time background scanner (Kaspersky), make sure the other(s) are on manual scan only.
Start > Run > Type "Msconfig" and select from the list, under the Startup tab what background applications do you have running on Windows start? As mentioned above, something might be conflicting in startup or a background service.
Is your Windows location:
C:\Windows\
or
C:\Win\
If it's location is default ( C:\Windows ), then do you also have a folder called ( C:\Win )? You understand what I'm getting at here? It's not the default windows location, which might be fine if your changed it during installation. However, just make sure it's not a fake file injected in, corrupted registry, or some application looking for it in the wrong place.
You will get the logs for that Dism command here:
C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\DISM\dism.log
Are you using Win 7 or Win 8.1?
win7
Then run Spybot and Malwarebytes scans.
Re-immunize while in Safe Mode w/ Spybot incase it missed adding a registry entiry it otherwise might not have been able too.