Screen Display problems :S Need help please

[masr]

I have Windows 7 professional and it worked perfectly at the beginning until recently i started having problems with the way my screen was displayed. I've tried installing the new display drivers and uninstalling them and reinstalling them but it doesn't seem to solve the problem. My graphics card is ATI Radeon HD 3200 and i have an HP Pavilion tx 2000 tablet. Also I've gotten the blue screen a lot. I really need help fixing this. here are some pictures.

This is how it starts up all the time and it takes me a while to get it to turn on right


after, this comes up




then it usually just restarts and repeats the same thing.

when i actually get it to work this happens after a while



and it ends with this



hopefully this is fixable :S:

 

[Lordbob75]

Hello masr, and welcome.

It would be a big help if you could provide the mini-dump file for the BSoD.
Just to throw it out, my first thought is a dying card. How old is it?

~Lordbob

 

[masr]

The only thing i copied down were
Problem event name: blue screen
Os Version : 6.1.7600.2.0.0.256.48
Locale id: 1033
My card is about a year old so I don't know if the card is actually dying.

 

[Lordbob75]

That is not enough. Try to search your computer for a .dmp file. Look around, I forget where they are located though...

~Lordbob

 

[zigzag3143]

David

Dumps are usually found in c:\windows\minidump and are *.dmp. If not there you can search for *.dmp.

then they can zip the dump file and upload it to us.

 

[Lordbob75]

David

Dumps are usually found in c:\windows\minidump and are *.dmp. If not there you can search for *.dmp.

then they can zip the dump file and upload it to us.

Rawrgh.... So I was close.
Thanks for the update.

~Lordbob

 

[zigzag3143]

Only reason I know is after about 800 of them I finally remember

 

[Lordbob75]

Yeah, I bet.

Apparently I do not even have the folder.......?

~Lordbob

 

[zigzag3143]

It might be in c:\windows and would be called memory.dmp

 

[masr]

this is what appears and its the most recent one

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


Loading Dump File [C:\Windows\Minidump\092909-25849-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Tue Sep 29 19:03:07.144 2009 (GMT-7)
System Uptime: 0 days 1:47:12.202
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8004036010, fffff88003c7e7f8, 0, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Unable to load image dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : atikmdag.sys ( atikmdag+127f8 )

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

 

[masr]

So apparently this might be a hardware issue and I'm sending it in to HP to have it repaired. Thank you guys so much for your time.
thefabe how do i check to see what is the monitor that i am using because it does say Generic PnP Monitor. so now it got me thinking if that could be the problem.

 

[thefabe]

(Edit I removed the original post due to misinformation on my part.)Well since I've realized that your using a laptop. Then it should probably say pnp. So I would turn my attention to either a driver issue with my graphics card or the card itself. You need to use a pogram called gpu-z download it to your desktop and run it, this will tell you exactly what graphics card your using then search for compatible driver for it. You will most likely have to use a Vista driver in compatibility mode. techPowerUp! :: Download TechPowerUp GPU-Z v0.3.5 Or go to HP site and look their for a vista 32 bit or 64 bit driver download it to your desktop.Then uninstall the existing driver. Then go to device mngr> display adapter and click update driver> find it myself and point it to your desktop.

 

[Lordbob75]

So apparently this might be a hardware issue and I'm sending it in to HP to have it repaired. Thank you guys so much for your time.
thefabe how do i check to see what is the monitor that i am using because it does say Generic PnP Monitor. so now it got me thinking if that could be the problem.

Masr, can you simply upload the .dmp file please?

~Lordbob