安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
举报此帖
That is a hardware failure that might not be in a game's log file. Where to look for a hardware failure? Event Viewer is somewhere to start troubleshooting.
As for the access denied error that's a known and common Windows error in File and Folder permissions. To correct it you can:
1. Try navigating to the file using a different path. For example if it's in the Documents folder and you're clicking on the Documents quick access link go the long way:
C:\Users\YOUR USERNAME\Documents
2. You can attempt correcting the issue by looking up how to adjust File and Folder Permission settings. I've tried this several times when it's happened to me with Windows and after changing the settings they change them selves right back to denying access immediately after closing the settings Window so it didn't work for me, any of the times I tried it.
3. Re-install Windows.
Find out what the hardware issue is that caused the Blue Screen of Death and care for that first. Re-installing windows and setting file permissions doesn't and won't fix a hardware issue.
Read the error code, look it up.
Bsod are info screens. Dont worry at one.
It did indeed auto reboot before I got chance the read any meaningful part of it ! So, how/where do I find the setting so it doesn't auto restart in future ?
Tried checking permissions last night, but the dump appeared to have the correct permissions as all was ticked, except the 'Special Permissions' option.
Think it is my first BSOD. I did get a crash a few months back (not a BSOD), though can't remember the reason for that. Mm, the PC is over 5 years so maybe it's telling me it's time is up. :(
It could have been blue screen of crash info.
Several ways to disable the auto restart.
https://www.tenforums.com/tutorials/69012-enable-disable-bsod-automatic-restart-windows-10-a.html
The error message does not necessarily be always the right hint. But by collecting them, it might tell.
Could be anything, even an antivirus.
Laptop or desktop? Laptops don't tend to last as long as desktops for the same reason(s), while they're surely getting there, they're not the best to use for PC games or video editing because they're compact. Because they're as compact as they are they tend to have issues with heat more than a desktop does - there's almost no space for air to move around in a laptop.
As muppet suggested the reason for the blue screen can be anything (hardware). 35+ years working with computers I've never once seen any software failure produce a blue screen. BSOD's are hardware failures. Hardware failure could be caused by software but the BSOD is info about the hardware that went splat.
Computers can last a pretty long time if they're maintained. They're a machine. I have multiple computers that I've had for nearing 15 years that still run great. We have to upgrade them now and then and parts failing happens - they can be fixed by replacing the wonky parts.
One BSOD isn't much to worry about. It could have been a one time thing because it heated up causing the hardware to shut down. If that's what it was cooling it off is all it needed and it did that by restarting. Do disable the auto-restart option but unless blue screens become more frequent I wouldn't worry about it.
Auto restart is now switched off.
It is a Desktop. When I logged in as the admin user I did notice some Windows report process running. After a few minutes it popped up a message saying something like 'failure has successfully been recovered'. I didn't notice the fan spinning up so maybe not heat related. Still not found a way to view the log to get an exact description of the failure so Guess I will never know. But at least if there is a next time I should get chance to read the BSOD.
In the Event viewer there is a single 'Critical' entry which contains info: Event ID 41, Task Category (63) and BugcheckCode 59. I didn't find anything helpful trying to google these.
https://www.partitionwizard.com/partitionmagic/windows-10-crash-log.html
Hopefully that at least gives you peace of mind that you investigated it as much as you could.
Event Viewer logs are sometimes hard to translate. Some of the errors it displays are common Windows errors that have existed since Windows was created. This is why some tech nerds aren't fans of Windows Operating Systems and choose to use alternatives like "Linux" operating systems because they're more stable and much less erroneous.
Category 63 indicates a hardware failure. Another step you can take to try and prevent it from happening again is to insure all your drivers are up to date and you have all of the windows updates. Common reasons for hardware failures are overclocking (disable it if you've overclocked anything), overheating (covered...you don't think that's it), driver issues (updating or rolling back to older is all you can do).
These things happen. Tech's don't raise concern about them unless they happen frequently. Without it happening frequently it's really difficult to track down.
If it was a part going bad there would be something easy to translate in Event Viewer that would plainly say *this* "failed and shut down unexpectedly" (as an example). Don't concern yourself with Event Viewer reports that aren't plain English "This went splat".
Bsod are not only for hardware.
I dont remember a hardware failure causing a bsod. I mean, i never had to replace hardware to fix a bsod.
So to say.
Software can cause this kind of error. I've stated that. Read what you quoted.
It does not report software failure. Logs we can access from Event and Reliability Viewer do that.
The experience you had was not an anti-virus producing the blue screen it was the anti-virus causing a critical error in the operating system which shut hardware down. Hardware shutting down is what caused the blue screen.
That was my point.
The software got bad, i removed it, porblem solved.