BSOD - Visiting websites.

Code:

BugCheck 116, {fffffa80046bb010, fffff88003bb045c, 0, 2}

This bugcheck indicates that an attempt to reset the display within the allocated time interval failed, hence the bugcheck.
This isn't a typical bugcheck in terms that this only happens when the graphics card doesn't respond either because of a bad driver or the GPU is faulty.

Code:

2: kd> KnL
 # Child-SP          RetAddr           Call Site
00 fffff880`05a7a1c8 fffff880`0414b054 nt!KeBugCheckEx <-- The BSOD crash
01 fffff880`05a7a1d0 fffff880`0414ad5e dxgkrnl!TdrBugcheckOnTimeout+0xec <-- Instruction telling the system to crash if the graphics card doesn't respond.
02 fffff880`05a7a210 fffff880`0400ff13 dxgkrnl!TdrIsRecoveryRequired+0x1a2 <-- Telling the system to run a display recovery.
03 fffff880`05a7a240 fffff880`0403ded6 dxgmms1!VidSchiReportHwHang+0x40b <-- This reports the graphics card has hung.
04 fffff880`05a7a320 fffff880`04023ce9 dxgmms1!VidSchWaitForCompletionEvent+0x196
05 fffff880`05a7a360 fffff880`04026be7 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
06 fffff880`05a7a460 fffff880`040252d8 dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
07 fffff880`05a7a4a0 fffff880`0402522e dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
08 fffff880`05a7a630 fffff880`0402e77e dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
09 fffff880`05a7a6a0 fffff880`0402e527 dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
0a fffff880`05a7a6f0 fffff880`0402decb dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
0b fffff880`05a7a750 fffff880`040218a4 dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
0c fffff880`05a7a790 fffff880`0401e257 dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
0d fffff880`05a7a7d0 fffff880`040387d9 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
0e fffff880`05a7a9a0 fffff880`04038514 dxgmms1!VidSchiSubmitRenderCommand+0x241
0f fffff880`05a7ab90 fffff880`04038012 dxgmms1!VidSchiSubmitQueueCommand+0x50
10 fffff880`05a7abc0 fffff800`02f6e2ea dxgmms1!VidSchiWorkerThread+0xd6
11 fffff880`05a7ac00 fffff800`02cc28e6 nt!PspSystemThreadStartup+0x5a
12 fffff880`05a7ac40 00000000`00000000 nt!KiStartSystemThread+0x16

Obviously your display driver will get blamed but lets take a look at the timestamp...

Code:

2: kd> lmvm atikmpag
start             end                 module name
fffff880`03ba9000 fffff880`03bf9000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Apr 20 02:22:32 2011 (4DAE3558)
    CheckSum:         00050398
    ImageSize:        00050000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As you can see it's very outdated.

I take it you're using a desktop, if so then update your driver here:

Drivers | GeForce

If you're using a laptop then remove all AMD software followed by a reboot, then run Windows Updates and use the driver that windows supports.

Post back the results.

Code:

BugCheck 116, {fffffa80044824e0, fffff8800422cf94, 0, 2}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+6f94 )

Code:

2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`021391c8 fffff880`02c66054 : 00000000`00000116 fffffa80`044824e0 fffff880`0422cf94 00000000`00000000 : nt!KeBugCheckEx <-- BSOD
fffff880`021391d0 fffff880`02c65d5e : fffff880`0422cf94 fffffa80`044824e0 fffffa80`0424bd50 fffffa80`0565d410 : dxgkrnl!TdrBugcheckOnTimeout+0xec <-- the recovery has failed, the display driver didn't respond in the allocated time interval
fffff880`02139210 fffff880`02d0cf13 : fffffa80`044824e0 00000000`00000000 fffffa80`0424bd50 fffffa80`0565d410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 <-- a TDR recovery has been called
fffff880`02139240 fffff880`02d3aed6 : fffffa80`ffffffff 00000000`00122b8f fffff880`02139390 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b <-- The GPU has hung
fffff880`02139320 fffff880`02d20ce9 : fffffa80`0571d000 ffffffff`feced300 00000000`00000002 fffff880`02139698 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02139360 fffff880`02d23be7 : 00000000`00001e78 00000000`00000000 00000000`00000000 fffff8a0`0ae686d0 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`02139460 fffff880`02d222d8 : fffff8a0`0ae686d0 00000000`00000000 fffffa80`0571d000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7
fffff880`021394a0 fffff880`02d2222e : 00000000`00000000 00000000`00000001 fffffa80`0571d000 fffff880`02d20b56 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34
fffff880`02139630 fffff880`02d2b77e : fffffa80`05418ea0 00000000`00000001 00000000`00000001 fffff800`02c875f2 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`021396a0 fffff880`02d2b527 : fffff8a0`0ae686d0 00000000`00001000 fffffa80`05418ea0 fffff8a0`0ae686d0 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`021396f0 fffff880`02d2aecb : fffff8a0`0ae686d0 fffffa80`0571dc80 00000000`00000000 fffffa80`0571dc80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b
fffff880`02139750 fffff880`02d1e8a4 : fffffa80`0571d000 fffffa80`0571d000 fffffa80`0571dc80 fffffa80`0571d000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf
fffff880`02139790 fffff880`02d1b257 : 00000000`00000000 00000000`00000000 00000000`00000029 fffffa80`0571d000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc
fffff880`021397d0 fffff880`02d357d9 : 00000000`00000000 fffff8a0`0ce22d70 fffffa80`00000000 fffffa80`0636a610 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f
fffff880`021399a0 fffff880`02d35514 : fffff880`009f2f40 fffff880`02d34f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02139b90 fffff880`02d35012 : 00000000`00000000 fffffa80`056bed50 00000000`00000080 fffffa80`0565d410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02139bc0 fffff800`02f2e2ea : 00000000`fffffc32 fffffa80`054178b0 fffffa80`0396eb30 fffffa80`054178b0 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02139c00 fffff800`02c828e6 : fffff880`009ee180 fffffa80`054178b0 fffff880`009f8fc0 fffffa80`04f7bc60 : nt!PspSystemThreadStartup+0x5a
fffff880`02139c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

You said you had updated the drivers?

Code:

2: kd> lmvm atikmdag
start             end                 module name
fffff880`04809000 fffff880`04fde000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Nov 17 03:06:43 2010 (4CE346C3)
    CheckSum:         00785F14
    ImageSize:        007D5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You've rolled it back, this is a laptop correct?
If so remove ALL AMD software then run Windows update to install the basic driver which has never known to cause issues, let us know how that goes.