Solved BSOD when watching a video on YouTube, error 0x000000A1

[iTeemu]

Hello.

My computer has started to torture me with this BSOD, again. I get the error usually when I am watching a videon on YouTube. After a couple of BSODs the error disappears and my computer works smoothly. I have checked my PC with multiple anti-virus programs and I've not found a single threat.

I have a picture of the BSOD if it is needed.

Specs

Windows 7 64bit
Ram 6,00gb
CPU: Intel Core 2 Quad CPU 2.67GHz
Graphics card: NVIDIA Geforce GT 230

 

[koolkat77]

Welcome to SevenForums,

Multiple antiviruses would rather create conflicts. So please uninstall any other security software except Microsoft Security Essentials.

Please uninstall the following software:

[LIST=1]
[*]Start Menu\Programs\AVG	Public:Start Menu\Programs\AVG	Public
[*]Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public
[*]Start Menu\Programs\Spybot - Search & Destroy 2	Public:Start Menu\Programs\Spybot - Search & Destroy 2	Public
[/LIST]

1. AVG contributes in BSOD-s and is often a cause of BSOD-s itself.

• AVG | Download tools and utilities

2. Daemon Tools:
Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO

OR, Prefer 7zip out of all:
Download and install 7-Zip, it is free +it can extract any iso file. So you can use it the way you want to. At a max you'll miss some chapter chooser screen of a DVD title.

3. Spybot can slow down the system.

• How to uninstall | Spybot ©
• Removing Spybot - Safer-Networking Forums

Recommended antivirus program for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials - Free Antivirus for Windows (which you already have)
• Malwarebytes - The Free version
• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

:warn: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with Malware Bytes.

You have way too many items at start-up. Free up the start-up, nothing except the antivirus is usually needed.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

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

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

The latest drivers for NVIDIA are a little problematic as I've heard. Click on the Start rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA Reboot the system. Now delete remnants of its drivers using Driver Fusion/Sweeper. Reboot if required

Download and install the drivers from the link of Filehippo bellow:

• Download NVIDIA Forceware 306.97 WHQL Vista 64 - FileHippo.com

Let us know the results of these

Then you may test the RAM with memtest86+:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Hope this helps for now

 

[iTeemu]

Alright. I've done everything you told me and so far my PC seems to be fine. I haven't gotten any BSODs. I will wait a couple of days before I mark this to resolved.

Thanks for the help!

 

[koolkat77]

Thanks for the update.

You can take memtest if you have time (precautionary).

Good luck.

 

[iTeemu]

Okay. My PC worked yestersay completely fine, but today morning it freezed and gave me a new BSOD. 0x0000007E

 

[koolkat77]

Upload the dump file and proceed with memtest.

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

 

[iTeemu]

Looks like my computer didn't create one, I was told that when it gave the blue screen of death it froze. At least for now, but I'll do memtest again.

 

[iTeemu]

Here's another blue screen of death, which I got. I will run memtest tonight when I have time

 

[koolkat77]

I will take a look at them soon.

 

[iTeemu]

I did the memtest twice and I got no errors. I just got on my PC and my taskbar started flashing, I moved my cursor on it stopped flashing. After a couple of seconds I got another BSOD. 0x0000000A


Here's the dumpfile

 

[koolkat77]

How many sticks of RAM do you have. Errors are often detected after 8 passes too. The latest dumps does not reveal anything specific.

Upload a screenshot of your hard disk using crystal disk info and "Summary" tab using Speccy:

• Speccy - System Information - Free Download
• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run these tools and delete anything they may find:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Edit: The previous dump states what exactly is causing the BSOD-s so I need to know how many sticks of RAM you have and how many passes you took memtest for.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8887, fffffa8003fd7fd0, fffffa8003fd3290, 604}

Probably caused by : [COLOR="Red"]hardware_ram ( ZEROED_PAGE_CORRUPTED )[/COLOR]

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008887, The subtype of the bugcheck.
Arg2: fffffa8003fd7fd0
Arg3: fffffa8003fd3290
Arg4: 0000000000000604

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_8887

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`055567c8 fffff800`02e927ce : 00000000`0000001a 00000000`00008887 fffffa80`03fd7fd0 fffffa80`03fd3290 : nt!KeBugCheckEx
fffff880`055567d0 fffff800`02eb23fb : fffffa80`03fd7fd0 fffffa80`0a729ec8 fffffa80`03fbb260 fffffa80`0a729ec8 : nt!MiUnlinkPageFromLockedList+0x1de
fffff880`05556850 fffff800`02e9fed5 : 00000000`00000000 00000001`547ff860 00000000`00000000 fffffa80`0a729ec8 : nt!MiResolveTransitionFault+0x16b
fffff880`055568e0 fffff800`02e9e893 : 00000000`00153e62 000007fe`f9155124 fffff683`ff7c8aa8 fffffa80`0a729ec8 : nt!MiResolveProtoPteFault+0x325
fffff880`05556970 fffff800`02e8e549 : 00000000`00000000 000007fe`f9155124 00000000`039bf630 fffff880`00000000 : nt!MiDispatchFault+0x1c3
fffff880`05556a80 fffff800`02e800ee : 00000000`00000008 000007fe`f9155124 00000000`0027bc01 00000000`020db0e0 : nt!MmAccessFault+0x359
fffff880`05556be0 000007fe`f9155124 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`039bf618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f9155124


STACK_COMMAND:  kb

SYMBOL_NAME:  ZEROED_PAGE_CORRUPTED

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED

BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED

Followup: MachineOwner
---------

 

[iTeemu]

Hello!

I ran the virus scanners and I found no threats on my computer.

I did the Hard Drive Diagnostic Procedure twice and I didn't get any errors.

I also ran 7 passes.I will run 8 or more passes tonight.

..And here are your pictures.

 

[koolkat77]

Thanks. Take them this way:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

:tip: Errors are sometimes found after 8 passes.
:tip: Do this test overnight, before going to bed.

 

[iTeemu]

All right. I just did the memtest and I ran 11 passes and recieved no errors.

 

[koolkat77]

How many sticks do you have?
Test the one stick in different slots. Do the same with all.

 

[iTeemu]

Oh. I forgot to do seven passes on each ram stick. Oh God..

I'll start doing that now.

 

[iTeemu]

Okay. I did the test and I didn't find any errors on my RAM, also my PC has started to work a lot better and has not given me BSODs

 

[koolkat77]

I see. Thanks for the update.

How many sticks of ram do you have?

 

[iTeemu]

I have four

 

[koolkat77]

Driver Verifier

Use verifier for 36 hours. Then send us the BSOD reports

Driver Verifier
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.
Driver Verifier - Enable and Disable