BSOD while browsing internet

[jakoobm]

Hi! I am running Windows 7 Professional x64. I got a few BSODs while using internet browser and i do not know what to do about it. Can anyone help me fix this problem?

 

[zigzag3143]

Hi! I am running Windows 7 Professional x64. I got a few BSODs while using internet browser and i do not know what to do about it. Can anyone help me fix this problem?

Several problems

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place. MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor



Old drivers needing updating

MarvinBus64.sys    9/23/2005 05:17:03 PM    fffff880`04644000    0x00044000    0x433470cf    fffff880`04600000                            
regi.sys    10/31/2006 04:22:11 AM    fffff880`07ae1000    0x00008000    0x454707b3    fffff880`07ad9000                            
AtiPcie.sys    5/5/2009 11:00:22 AM    fffff880`01888000    0x00008000    0x4a005486    fffff880`01880000                            
Rt64win7.sys    5/22/2009 10:52:30 AM    fffff880`04337000    0x00039000    0x4a16bc2e    fffff880`042fe000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

These were cased by your video driver, card, etc. Please re-install the driver using this

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\041711-18891-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0344c000 PsLoadedModuleList = 0xfffff800`03691e90
Debug session time: Sun Apr 17 10:04:23.790 2011 (GMT-4)
System Uptime: 0 days 5:47:18.335
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006dc31b0, fffff880045b43bc, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** 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+73bc )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006dc31b0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880045b43bc, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+73bc
fffff880`045b43bc 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06987898 fffff880`046a1000 : 00000000`00000116 fffffa80`06dc31b0 fffff880`045b43bc 00000000`00000000 : nt!KeBugCheckEx
fffff880`069878a0 fffff880`046a0d0a : fffff880`045b43bc fffffa80`06dc31b0 fffffa80`076a8d50 fffffa80`06668410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`069878e0 fffff880`04747f07 : fffffa80`06dc31b0 00000000`00000000 fffffa80`076a8d50 fffffa80`06668410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06987910 fffff880`04775d5a : 00000000`ffffffff 00000000`0014614e fffff880`06987a70 fffffa80`06668410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`069879f0 fffff880`047716af : fffffa80`06668410 ffffffff`feced300 00000000`00000002 fffffa80`06dfc4c0 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`06987a30 fffff880`04770023 : fffffa80`06668410 00000000`00000002 fffff880`0476fdc0 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`06987b20 fffff880`047702fe : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`06987b50 fffff880`047432c6 : ffffffff`ff676980 fffffa80`06668410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`06987bf0 fffff880`0476fe7a : 00000000`00000000 fffffa80`062ccd50 00000000`00000080 fffffa80`06668410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06987d00 fffff800`03769cce : 00000000`fffffc32 fffffa80`062cbb60 fffffa80`039d6040 fffffa80`062cbb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06987d40 fffff800`034bdfe6 : fffff800`0363ee80 fffffa80`062cbb60 fffff800`0364ccc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06987d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`045b43bc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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