Is there an event logger that works?

Birk,

What I think happened was that
- Deleting the driver set the display to use Windows' 'Basic display driver', which has very limited capabilities, and deleted the installed driver's files.
- Running 'Scan for hardware changes' forced Windows to look all over for the most suitable driver and it found that earlier one [perhaps from your earlier download, perhaps from the driver store in which the earlier one's files were still hanging around, I'm not sure]. Rebooting would have had the same effect.

I hope this sorts your problem out.

Do you know about driver backups?
Backup and Restore Device Drivers - TenForumsTutorials
I suggest you make a backup now. I make a new backup every time I install or update a driver and I keep the last few backups.

Best of luck,
Denis

Ghot - I've copied your DDU instructions. My only note about using it had been a link to a WindowsQuestions thread to which you & OldMike had contributed. Thanks.

The older Intel display driver is held in the System32\DriverStore\FileRepository folder as a backup, but also as a rollback option, when you update the display driver there are two packages held in the FileRepository folder, old and new.
When the OP uninstalled the new one Windows installed the old one from the FileRepository.

I have found the most reliable way to clear out all versions of the Intel display driver is to use RAPR (driver store explorer) run as admin, choose old drivers option to remove the old Intel driver, then check mark the current driver and remove that. This gives you a clean starting point.
The above should only be done once the Microsoft default display driver is in place, also should be done without internet connected.
DDU is brilliant for uninstalling the current in use drivers but doesn't always/ if at all touch the rollback versions in FileRepository.

The OPs issue though seems to be driver or application related, if the memory and disk system seem to pass at least cursory error checking then the sort of system freeze/ lockup being experienced suggests maybe private memory space being overwritten by some errant piece of software.
I would suggest setting up a new user account, removing as many 3rd party apps and services from the mix as possible using Task Manager's start up tab and Autoruns. Maybe using the services console to temporarily disable loading of other 3rd party services, unplug all unnecessary hardware especially wireless/ Bluetooth devices, receivers, in order to get to as clean a system as possible without a re install for testing.

Those are interesting points.

Birk - I've just re-read the thread and I can't see that you've already tried Safe mode for a while to see if the fault happens there as well. I appreciate that it's an intermittent fault so you might get very bored waiting for nothing for a long period.
Safe mode - ElevenForumTutorials

Best of luck,
Denis

@

Birk​

thanks for asking :)

@ f14tomcat​

thank for this

firas465 said:

I just ran the Event logger and it is showing 92000 items

Click to expand...

It is Windows that logs events not the NirSoft tool. It is merely a viewer, just like the built-in Event viewer.
Events are being recorded all the time so there's nothing significant in their number.
Events are not necessarily indicators of faults. They are just events. They can be useful in diagnosing faults that have observable symptoms but are rarely of significance in their own right.

If you want to investigate your game crashes then I urge you to start a thread of your own instead of complicating Birk's current thread.


All the best,
Denis

Try3 said:

It is Windows that logs events not the NirSoft tool. It is merely a viewer, just like the built-in Event viewer.
Events are being recorded all the time so there's nothing significant in their number.
Events are not necessarily indicators of faults. They are just events. They can be useful in diagnosing faults that have observable symptoms but are rarely of significance in their own right.

If you want to investigate your game crashes then I urge you to start a thread of your own instead of complicating Birk's current thread.


All the best,
Denis

Click to expand...

ok thanks

should i remove my last post ?

Try3: Thanks for that reference to the Backup/Restore drivers process. I have not seen that before and will set it up now. It looks like a very clean way to deal with drivers that does not require an external piece of software.

firas465 said:

should i remove my last post ?

Click to expand...

It wouldn't hurt. It would keep things simple.
Perhaps delete all but the first line, "Ok Guys I just ran the Event logger and it is showing 92000 items" because it & my reply might help others who try viewing events.

All the best,
Denis

Try3 said:

There's some confusion evident here. NirSoft FullEventLogView does not log any data at all. It reads & presents Windows' logs.

I use FullEventLogView during fault investigations and it can be useful because its chronological display allows me to see what happened [in all logs] immediately before & after some event I have previously identified using Event viewer.

In your case, I'd start by looking for the Event log service starting & stopping to give me a timeframe for when the freeze happened. I don't know how helpful this will be because freezing is not an event so there will not necessarily be anything usefully diagnostic recorded in the run-up to the freeze happening.
Log name - System
Source - EventLog
EventID - 6005,6006 {for starts & stops respectively}

I really don't know if event logging is going to progress things or not. If you want to try then I can help.
I can give you a set of Event viewer, Custom view definitions that I would check in the hope of finding something useful.
I can also explain how to import those definitions into your Event viewer.
Do you want to proceed with this?

All the best,
Denis

Click to expand...

Sorry, small typo on my part. I know it itself does not log anything, but presents the logged data. Sorry, I should have been more careful, and I have corrected the confusion.

The hangups persisted even after backing up one version of the Intel display driver. So I did an in place Windows update with no trouble other than having to manually download and install the latest Windows update. I should know in a day or so if the system hangs still happen. I've been seriously thinking about updating my motherboard and CPU, so that may be the only option I have left.

I really can't bear the thought of a clean install.

I've looked through the posts on this thread and see no reference to a possible physical malfunction between the motherboard and its separate components. I vaguely remember experiencing a similar problem many years ago, where the RAM modules were losing or making poor contact in their slots. I took them out and "rotated" them one position in their slot location, which stopped the problem. Worth a try?