BSOD when trying to boot normally.

[Silven]

After a few minutes of playing Guild Wars 2 my computer Blue Screened and now every time I try to restart or boot my PC it just blue screens after showing the Windows 7 'Starting' Logo everytime. Apparently it has something to do with the Display Driver or something. All I can do to bypass this is to boot in safe mode or go to the Bios and switch my Graphics mode from Switchable to Integrated.
Ive already tried updating my drivers and it says they're up to date.

Thanks for your help.

 

[ICIT2LOL]

Hello and welcome Sileven now you have an issue with thegraphics driver and I am going to suggest you uninstall the Catalyst ControlCentre and driver and reinstall the driver from here http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64 <it is the 64 bit version as I am not sure if you are running a 32bit or64bit OS.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=red]VIDEO_TDR_FAILURE (116)[/COLOR]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80087003a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800475ca1c, 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+7a1c
fffff880`0475ca1c 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`08788888 fffff880`0555b134 : 00000000`00000116 fffffa80`087003a0 fffff880`0475ca1c 00000000`00000000 : nt!KeBugCheckEx
fffff880`08788890 fffff880`0555ae3e : fffff880`0475ca1c fffffa80`087003a0 fffffa80`084f5010 fffffa80`084e3010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`087888d0 fffff880`0540ff13 : fffffa80`087003a0 00000000`00000000 fffffa80`084f5010 fffffa80`084e3010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`08788900 fffff880`05439cf1 : 00000000`ffffffff 00000000`0000047b 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`087889e0 fffff880`05438437 : 00000000`00000102 00000000`00000008 00000000`0000047b 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`08788a10 fffff880`0540b2d2 : ffffffff`ff676980 fffffa80`084e3010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`08788ab0 fffff880`05437ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`07d3a168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`08788bc0 fffff800`03172456 : 00000000`026243be fffffa80`084f7610 fffffa80`042ccb10 fffffa80`084f7610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`08788c00 fffff800`02eca2c6 : fffff880`009ea180 fffffa80`084f7610 fffff880`009f4fc0 fffffa80`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`08788c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+7a1c
fffff880`0475ca1c 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+7a1c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  [COLOR=red]atikmpag.sys[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4ddc68a6
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x116_IMAGE_atikmpag.sys[/COLOR]
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
Followup: MachineOwner

You will see from the msinfo pic verification there is a problem.
Now to find out about the components in the machine see my ditty and let us know the mobo etc

UsingHW Info

PART A:

You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 -Download < download the right bit version andclose the right hand window select Sensors and scroll down to the power sectionwhere you will see what the volts are doing see my pic. In my pic the section (Nuvoton) with VBATT is a dead give awayyou are in the section for the rail voltages. There are other section titlesand one that pops up often is ITE

Now the voltage on the different rails have to be within 5% =+/-of what is required or the machine will not work properly if at all.

See this for the rail voltage info

http://www.tomshardware.com/reviews/power-supply-specifications-atx-reference,3061.html (Section 2.)

The original right hand window shows the machine running and ishandy for that but for looking at the components in some detail close it anduse the main left hand side panel

FOR OTHERCOMPONENTS

PART B:

Open each small square with + in it on the section thecomponents are in and then click on the individual component/s (it will highlight in blue) - in the righthand side will appear all sorts of details including brands speeds and otheressential info that particular device. See pic for example.
Use PART B: (see pic for example)

Now if you can also get into safe mode it would not be a bad idea to run these too


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

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2

 

[Silven]

Heres my voltage levels. Not sure what they mean.

Also, i have uninstalled and reinstalled the Catalyst Control Center and the AMD Drivers. Nothing has changed.

My Radeon 6650M GPU no longer shows up in my Devices list anymore. Just the Intel Graphics Family :\

 

[ICIT2LOL]

The battery voltage is low as I think is comfortable - as the supply voltage to any machine - generallyspeaking has to be within +/- 5% of the required voltage and I have no doubtthis applies to laptop batteries.

A reference for this http://www.tomshardware.com/reviews/power-supply-specifications-atx-reference,3061-2.html itapplies mainly for checking desktop PSU's but the principle I am going out on alimb to say the supply here in your battery is too low or at least right on the edge of too low and maybe time for a newone.

If that doesn't work then time to look at the charging circuitry in themachine - or the adaptor output.

 

[ICIT2LOL]

Hello again look I forgot to include a shot of mine and this a five year old battery - look at the volts and the Wh (Watts / hour) Battery Definitions ? Battery University a lengthy read but explains it is just the ability to deliver power and is related to milliamp / hours.

You will see yours are all over the place compared to mine.