Windows 7: BSODs playing flash games in Facebook and others

Update:

I have run the Driver Verifier (as a matter of fact is still running at the time of this post).

So far over 12 hours without a BSOD, however I've been having severeal since my last post.

I attach the updated Windows_NT6_BSOD_jcgriff2 and System Health Report.

I will keep it running just in case...



Please let me know if you can get anything new out of this new System Health Report.

One thig I have noticed; even if I am not using the computer (only switched on), sometimes, out of nowhere, a BSOD happens... don't understand...

Thanks in advance for all your help...

New Update:

Tonight I had some new minidumpfiles to add...

I send them in attachement.

During the process of using the Windows_NT6_BSOD_jcgriff2, it said that it could not perform the msinfo32 procedure. It said the process was being used by the system.

Any ideas please...

Hello amss1976 and welcome to Sevenforums.

NFO file needed

BSOD Analyse

SFC /scannow

We usually ask people to do this command to check if Windows is corrupted. It's the most common one used to check if the Windows files are corrupted. If it'll find errors, it'll restore them.



Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

Malwarebytes

To ensure that your system isn't suffering of malware, do a full scan with Malwarebytes.

Malwarebytes : Free anti-malware download

Best Regards,
Frederik.

Hi all,

Today I returned from hollidays and run again the Windows_NT6_BSOD_jcgriff2 and the program smoothly this time.

I also run the System Health Report and the verifier is still running as requested by you before.

I attach the new files I got today.

What's the results of post #14?

Best Regards,
Frederik.

The Malwarebytes test was not performed as the problems started right after installing Windows 7.

The NFO file is attached as well as the log of the SFC.

Hope this can help to try to solve all these problems.

Thank you!

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.


To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

Best Regards,
Frederik.

On post #6 I run the Memtest86+ (on the two RAM's at the same time) and they turned out with no faults.

Do you still advise these one by one testing on the RAM's and on the slots?

Thanks for the help.

Alright, I'm sorry I wasn't aware. You can skip those steps.

Do you have any additional dumps to upload?

Best Regards,
Frederik.