 | |
| |
| 27 Dec 2011 | #1 |
| | BSOD + Flash? I have alsmost new rig: OS  Windows 7 x64 CPU Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz Motherboard Gigabyte GA-H61M-DS2 (rev. 1.0) Memory 6,00 GB Dual-Channel DDR3 @ 665MHz (9-9-9-24) Graphics Card(s) AMD Radeon HD 6700 Series (Sapphire/PCPartner) (6770) Sound Card Onboard Monitor(s) Displays Acer V193HQ Hard Drives 977GB Hitachi Hitachi HDE721010SLA330 ATA Device (SATA) - 1TBAntivirus is AVIRA 12BSOD-s happen only while playing a flash video. Error is related to ntoskrnl.exe+7cc40 While playing games everything works fine (tried COD Modern Warfare 3, newerst Skyrim). Drivers are updated a don`t have a clue whats wrong? Please help |
My System Specs | |
| 27 Dec 2011 | #2 |
| | Hellojoshibeast These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem. If you are overclocking anything reset to default before running these tests. In other words STOP!!! 1-Memtest. Quote: *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 or 6 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. 2-Driver verifier Quote: I'd suggest that you first backup your data 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). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . 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 "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 (an estimate on my part). 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. Further Reading Using Driver Verifier to identify issues with Windows drivers for advanced users |
| My System Specs |
| 27 Dec 2011 | #3 |
| | Thanks JMH for a quick response, Memtest86+ passed a 2 hours run with no errors (for now). Booted from USB stick (new feature from memtest86+) Started driver verifier as suggested. Windows booted just fine. Waiting for a crash to happen again. Just tell me one more stuff (possibly a stupid question): How will I know wich driver caused a crash? |
| My System Specs |
| . |
| |
| 27 Dec 2011 | #4 |
| | 
Quote: Originally Posted by joshibeast  Thanks JMH for a quick response, Memtest86+ passed a 2 hours run with no errors (for now). Booted from USB stick (new feature from memtest86+) Started driver verifier as suggested. Windows booted just fine. Waiting for a crash to happen again. Just tell me one more stuff (possibly a stupid question): How will I know wich driver caused a crash? Not a stupid question at all...  If it finds an error, you will get a BSOD, which should be uploaded for analysis. |
| My System Specs |
| 28 Dec 2011 | #5 |
| | Okay it crashed again afret almost two days. Here is the new file: |
| My System Specs |
| 28 Dec 2011 | #6 |
| |
Quote: Originally Posted by joshibeast Okay it crashed again afret almost two days. Here is the new file: These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem. If you are overclocking anything reset to default before running these tests. In other words STOP!!! 1-Memtest. Quote: *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 or 6 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. 2-Driver verifier Quote: I'd suggest that you first backup your data 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). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . 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 "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 (an estimate on my part). 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. Further Reading Using Driver Verifier to identify issues with Windows drivers for advanced users |
| My System Specs |
| 29 Dec 2011 | #7 |
| | @zigzag3143 Thanks, but i already did memtest + driver verifier. This is the report after the latest crash |
| My System Specs |
| 29 Dec 2011 | #8 |
| |
Quote: Originally Posted by joshibeast @zigzag3143 Thanks, but i already did memtest + driver verifier. This is the report after the latest crash This one was not driver verifier enabled. |
| My System Specs |
| 29 Dec 2011 | #9 |
| | Sorry, i uploaded a wrong file. I downloaded BSOD app on my desktop so it was unable to rewrite old report files. Here is the new one. Also, just minutes ago I expirienced another BSOD, that seems, unrelated to to all the others. |
| My System Specs |
| 29 Dec 2011 | #10 |
| |
Quote: Originally Posted by joshibeast Sorry, i uploaded a wrong file. I downloaded BSOD app on my desktop so it was unable to rewrite old report files. Here is the new one. Also, just minutes ago I expirienced another BSOD, that seems, unrelated to to all the others. !! Also make sure you have the lasted drivers installed. |
| My System Specs |
 |
BSOD + Flash? problems?
| Thread Tools | |
| Similar help and support threads for: BSOD + Flash? | ||||
| Thread | Forum | |||
| flash causes BSOD | BSOD Help and Support | |||
| BSOD while using flash | BSOD Help and Support | |||
| Getting BSOD from flash | BSOD Help and Support | |||
| Flash and BSOD? | BSOD Help and Support | |||
| Users Remain Vulnerable to Flash Exploits After Upgrading Flash Player | System Security | |||
All times are GMT -5. The time now is 09:34 AM.
