Solved BSODs playing flash games in Facebook and others

[amss1976]

Hi!
This is my first post here.

I have been having some BSOD problems with my newly built computer.

It is Windows 7 x64.
Just assembled this system with the following new components:
- OS: MS Windows 7 Ultimate 64-bit SP1
- Processor: Intel Core i5 2500K @ 3.30GHz Sandy Bridge 32nm Technology
- MoBo: ASUSTeK Computer INC. P8Z68-V LX (LGA1155)
- RAM: Kingston (KHX1600C9D3B1K2/8G) 8,00 GB Dual-Channel DDR3 @ 1600MHz (9-9-9-24), 1.65v - HyperX Blu [I think this might be the problem, but not sure because they are only working at 1.5v and 1333MHz]
- Sound Card: Realtek High Definition Audio
- HDD:244GB Western Digital WDC WD2500AAKX-001CA0 ATA Device (SATA) [used for the OS]
- Optical Drive: Asus DVD +/-RW

Components I already had:
- Graphics: 256MB GeForce 8400 GS (ASUStek Computer Inc)
- 1954GB Seagate ST2000DL003-9VT166 ATA Device (SATA) [used for storage]
- 78GB Seagate ST380011 SCSI Disk Device (RAID) [used for storage]
- 160GB Maxtor Maxtor 6 SCS [used for storage]
- Case
- PSU: OCZ 600W

This system was assembled last 29 March 2012 (HW and SW).

The problem that I am facing happens when using any browser (IE9, FF, Chrome and Opera - all latest versions) and playing flash based games (mostly on FaceBook) but also on Yahoo and also playing videos. In Chrome, sometimes the flash just stops and the content of the page becomes with a message "the shockwave plugin crashed - reload the page and try again" and a message appears at the top of the window right after the address bar "the following plug-in has crashed: Shokwave Flash".

I have tried to uninstall both the adobe flash and disable/re-enabled the integrated flash in Chrome but the problem still persists.

In IE9 I cannot play any type of flash based content. Haven't figured out what seams to be the problem.

I am also experiencing crashing in the browsers for no apparent reason.

I have performed a memory check with the windows tool but it did not report any problem.

If you nee any further clarifications, please ask.

I am attaching the zip file with the content of Windows_NT6_BSOD_jcgriff2 and System Health Report as instructed.

Please help me to try to solve this situation as this is a brand new computer.

Thanks in advance for all the help and time.

 

[JMH]

1. Avast can be a contributing cause of BSOD'S.
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows


2. If not already done > please run the System Update Readiness Tool (SURT) and then update to SP-1

32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details

Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

 

[zigzag3143]

Please follow JMH's suggestions first as they may well fix this and are easier.
These crashes appear to be caused by various things. To narrow the focus please run these two tests. I know you have run the windows memory test (doesnt stress the memory far enough) and verifier for at least one crash but we need more.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[amss1976]

1. Avast can be a contributing cause of BSOD'S.
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows


2. If not already done > please run the System Update Readiness Tool (SURT) and then update to SP-1

32 Bit

Download: System Update Readiness Tool for Windows 7 (KB947821) [February 2012] - Microsoft Download Center - Download Details

64 Bit

Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2012] - Microsoft Download Center - Download Details

Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

Have uninstalled avast and installed MSE.

I had already updated W7 to SP-1 (BSODs continued)

I will see if now, with MSE, the BSOD's stop.

As soon as I have some news, I'll feedback here.

Thanks for these tips...

Keeping my fingers crossed here...

 

[JMH]

Good luck & keep us posted.

 

[amss1976]

Please follow JMH's suggestions first as they may well fix this and are easier.
These crashes appear to be caused by various things. To narrow the focus please run these two tests. I know you have run the windows memory test (doesnt stress the memory far enough) and verifier for at least one crash but we need more.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

I got one more BSOD after my last post.

This night I let it running the memtest for aprox. 6:30 hours. It made 5 passes and no errors were found. I attach the picture of it.

Can I conclude from this that the RAM is OK? (I noticed that when I hit the Esc key and it restarted the red ligh of "MemOK" on the MoBo blinked for a second... but started smoothly)...

Do you suggest I should run the driver verifier test? As far as I read on your post it is a risky thing to do...

 

[zigzag3143]

Ram looks ok now for verifier

 

[JMH]

Do you suggest I should run the driver verifier test? As far as I read on your post it is a risky thing to do...

Yes we do.
Using Driver Verifier is an iffy proposition.
However we ARE here to help you solve your problem.

As a precaution we suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point. (so you can restore the system using the Vista/Windows 7 Startup Repair feature)

 

[amss1976]

I am not going to try the verifier for the next days as I will have to make a presentation for college and will not take the chance of losing data.

As soon as I'm done with it I will do it and post here the results...

 

[zigzag3143]

I am not going to try the verifier for the next days as I will have to make a presentation for college and will not take the chance of losing data.

As soon as I'm done with it I will do it and post here the results...

Good luck

 

[amss1976]

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...

 

[amss1976]

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.

 

[amss1976]

Any ideas please...

 

[FredeGail]

Hello amss1976 and welcome to Sevenforums.

NFO file needed

To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

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.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

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

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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.

 

[amss1976]

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.

 

[FredeGail]

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.

 

[amss1976]

Hello amss1976 and welcome to Sevenforums.

NFO file needed

To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

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.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

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

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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.

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.

 

[FredeGail]

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.

   Warning

:info: Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

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.

 

[amss1976]

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.

   Warning

:info: Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

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.

 

[FredeGail]

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

Do you have any additional dumps to upload?

Best Regards,
Frederik.