Windows 7 Occasional Bluescreen but always forced restart


New Member
Aug 17, 2019
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 13321

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA80047B4010
BCP2: FFFFF88004036CB0
BCP3: 0000000000000000
BCP4: 000000000000000C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:

There is also an Event on the Eventviewer showing this error at the time of the crash:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Source: WMI
Log Name: Application
Level: Error

It happens very frequently, especially when I'm playing video games.
Sometimes a blue screen happens, sometimes it just freezes and forces a restart


The "freeze" is your graphics taking too long to render. I would check the computer manufacturer site for an updated graphics driver or if they don't have one you can check Intel's site.

According to this website: Link Removed
The 'latest' and only driver available for my integrated graphics card is this
The driver currently installed in mine is, trying to install the above version will result in an error, other steps to try and make it work was unsuccessful, other errors say that the machine does not meet the requirements.. but the driver was supposedly for the cpu I have..?

The Media Accelerator in here: Link Removed
Was also unsuccessful in installing, saying that the machine does not meet requirements as well

Last website here: Intel G41 Drivers Download for Windows 10, 8.1, 7, Vista, XP
provided a version which is seemingly higher than the one I currently have, it has successfully installed and I will update on the situation

After 2 and a half hours of testing, there was no crash happening. While I find it hard to believe it has all been just fixed by a driver issue,that might just have been the case, to which I'm more than willing to accept.

Thanks a lot! for now..

Last edited: