Event Viewer (Win10)

[Old_Geezer]

When I had Win7 I seemed to find it easier to spot a log I was looking for. (Not that I ever knew much what to do with them but at least I had an insight.) It just seems there are so many different 'folders' in Win10 that I can't find anything.

I'm looking for advice on where to check. I can see loads of logs telling me there was an unexpected shutdown (you don't say ? really ?) But look for an error that causes it and it seems either non-existent or well concealed.

I am certain it is to do with the graphics still. Only ever happens during the game I "occasionally" play. Nothing seems to cure it. But I'd like to actually see the logs of the last one to confirm whatever info it has.

Anyone know which part I should be looking in for the "things are going wrong" logs prior to the reboot ?

[AB Editor]

Hi O_G

Have you tried searching using the win10 search bar next to the start? Sometimes it's quite good!

I'm not familiar with the issue you're trying to fix? Have you got a previous Q on the subject?

[Old_Geezer]

Thanks but one needs to know the name of the log one is looking for in order to perform a PC search. Although I can give it a try, I suspect it's unlikely to look into the Event Viewer.

Oh yes, a question regarding of the same fault, but not about the Win10 Event Viewer. (I only changed to Win10 in the vain hope it'd fix this issue.)

http://www.theanswerbank.co.uk/Technology/Computers/Question1462850.html

(I was keeping to the older NVidia driver and getting continually nagged by Win10 to update but then the old one wasn't able to get me over this one part of the game (Hardest Dragon/Nightmare Mode) without crashing so I once more gave the new one a try. After about 2.5 to 3 hours battle (during which time saves are disabled, for a laugh) I was just at the point of finishing the fight and the PC crashed again. I need to do something that works to fix it.)

[CrapAtCryptics]

event viewer is still there - just type it in the "search web and windows" box

[TheChair]

Generally, the 'unexpected shutdown' is recorded AFTER the computer restarts, and indicates that the crash was so catastrophic, that Windows was incapable of recording the cause. So you are unlikely to find anything useful in the event logs. You can find the logs in control panel/administrative tools.

[Old_Geezer]

Thanks. I'm aware that Event Viewer is there. I have it open on the screen. It's finding the relevant logs that is the problem. I used to find the required logs easier in Win7, I just hope someone can help me find the equivalent in the Win10 Event Viewer. They seem to be in numerous categories/'folders' now and it'd be nice to know where I'm supposed to find something in the system not responding type events.

[Old_Geezer]

The logs seem easier to find once one reverts to the older, still crashes but not so often, driver. Windows Logs/System it seems, but for the most recent driver, little to be seen. Maybe they think it's easier once they hide the evidence, to deny anything is wrong.

The Net seems to suggest drivers and overheating are the main causes of Event ID 13 from source nvlddmkm, but the crashes occur regardless which driver, and I've ruled out overheating/dust/etc..

There's the problem, all possible causes, the company involved can deny it's anything to do with them, but the problem still exists. Pity software doesn't exist to monitor things and note exactly what causes an issue (and describe it in simple English).