BSOD (ntoskrnl.exe) after boot/idle/playing browser flash games

[Akherousia]

I have been getting the BSODs for 3 days now (started on 19/07/2013).
They happened more or less at random times.
First time right after boot I launched a browser flash game and that killed it.
Then I was changing settings of Steam and it died again
One more time happened while I was waiting for it to boot, was not touching anything even.
Next time I did not launch any games, was just doing browsing. It was fine for 40 minutes, then I risked starting a flash game again, played for 7 minutes - bsod again.
I don't think all of these got logged, but should be around 6-7 by now.

Used the BlueScreenView tool to see that the problem was caused by ntoskrnl.exe.

Tried uninstalling the latest windows update (critical update installed on 19/07/2013), but that did not solve the problem.
Reinstalling Windows is NOT an option for me since my Windows came on some restore CD thing that formats everything.

P.S. Sorry my Windows is in Russian, so some of the log files ended up having a lot of Russian in it as well as some weird symbols, caused most probably by some encoding errors.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000096[/COLOR], fffff800032c5e47, fffff88008eea5e0, 0}

Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+a7 )

Usual causes:  System service, Device driver, graphics driver, memory

Update:

1: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`04832000 fffff880`05298000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="Red"]Thu Nov 10 02:52:46 2011[/COLOR] (4EBB3C7E)
    CheckSum:         00A1B01E
    ImageSize:        00A66000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your graphics card driver seems to be possible cause, and rather outdated, please update here - AMD Graphics Drivers & Software

WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104

Remove:

Start Menu\Programs\Alcohol 120%	
Start Menu\Programs\DAEMON Tools Lite

Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Daemon Tools and Alcohol 120% both use a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove these programs, and use Windows own in-built features or ImgBurn.

 

[Akherousia]

Thank you for your reply.

Before I read your reply I had another bsod "spike", the pc went to system restore and had another bsod and then shut down with beeps coming out of the tower.

Then I managed to switch the pc back on, did the steps that you suggested, rebooted and then the pc worked stable for a couple of hours. Hoping that all was fixed I switched the pc off and went to bed.

In the morning I tried to switch on the pc but it couldn't load Windows - BSOD at launch, BSOD during system restore and then another shutdown with beeps. On the third try I managed to do system restore without bsod and Windows launched. So here I am again.

I am attaching another diagnostics file if that helps. I don't think all bsods got logged, I made some photos of the screen (if that's good for anything).

Thank you for your help.

P.S. I am ready to reinstall Windows but will that even help?..

 

[x BlueRobot]

Thanks for the information, the BSODs look mostly memory/driver related, but unfortunately the dump file seems to be corrupt, and since it tends to show POST Beeps and BSOD at boot, then there is a strong possibility it may be RAM related.

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

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.