Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

problem with windows xp sp3


  • This topic is locked This topic is locked
13 replies to this topic

#1 nuic

nuic

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:09:13 AM

Posted 03 January 2010 - 09:23 AM

i download accidentally a program for chips on texas hold'em poker on facebook
now when i want start my PC this picture show up
http://it.tinypic.com/view.php?pic=514wt3&s=6
i can start my PC only in debugging mode and when i start some program my computer freeze
so can anyone help me without reinstalling windows

BC AdBot (Login to Remove)

 


#2 OldGrumpyBastard

OldGrumpyBastard

  • Members
  • 781 posts
  • OFFLINE
  •  
  • Location:"Way South of 'da Bridge"
  • Local time:03:13 AM

Posted 03 January 2010 - 09:31 AM

Read this:

http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

Download the debugging tools...Run it...Post your log here and we will try and diagnose possible causes.
Does this look like an OldGrumpyBastard or what?

#3 nuic

nuic
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:09:13 AM

Posted 03 January 2010 - 11:02 AM

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini122209-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 22 21:46:39.515 2009 (GMT+1)
System Uptime: 0 days 2:04:57.067
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {89bd12a0, 89b98510, 89042460, 1}

Probably caused by : nv4_disp.dll ( nv4_disp+ee830 )

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

this is log vat i get from debugger
and down is after i analyze it
it was minidump file i debugged last one
do i need analyze all or this is enough?



Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini122209-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Dec 22 21:46:39.515 2009 (GMT+1)
System Uptime: 0 days 2:04:57.067
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {89bd12a0, 89b98510, 89042460, 1}

Probably caused by : nv4_disp.dll ( nv4_disp+ee830 )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 89bd12a0, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 89b98510, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 89042460, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

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


FAULTING_THREAD: 89bd12a0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: iw3mp.exe

LAST_CONTROL_TRANSFER: from bf100637 to bf100830

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b04cd668 bf100637 400013e1 00000001 00000000 nv4_disp+0xee830
b04cd66c 400013e1 00000001 00000000 e173c960 nv4_disp+0xee637
b04cd76c bf8edd6b b04cd82c e16b9714 e1270018 0x400013e1
b04cd7a4 bf009530 b04cd82c e1e20488 e16b9714 win32k!WatchdogDdDestroySurface+0x38
b04cd860 bf009684 e16b9008 e1270018 00000000 dxg!vDdDisableSurfaceObject+0x294
b04cd8a0 bf009812 e1e20488 e12dc998 00000000 dxg!vDdDisableAllDirectDrawObjects+0xa8
b04cd8c4 bf8adeac e16b9008 00000000 b04cd900 dxg!DxDdSuspendDirectDraw+0xb4
b04cd8d4 bf93e70e e16b9008 00000000 e12dc998 win32k!GreSuspendDirectDraw+0x1c
b04cd900 bf8a367e e16b9008 00000000 b04cdaa8 win32k!DrvDisableDisplay+0x1a
b04cd934 bf8a428f e189b988 e2fd9638 e4f42818 win32k!hCreateHDEV+0x151
b04cdaac bf8aabd2 00000000 00000000 00000001 win32k!DrvCreateMDEV+0x4dc
b04cdba0 bf8ace3d 00000000 e16b9008 00000000 win32k!DrvChangeDisplaySettings+0x251
b04cdbe4 bf8bc1b9 00000000 00000000 00000000 win32k!xxxUserChangeDisplaySettings+0x141
b04cdc24 bf819cd4 00000001 b04cdc4c bf819d98 win32k!xxxDestroyThreadInfo+0x189
b04cdc30 bf819d98 89bd12a0 00000001 00000000 win32k!UserThreadCallout+0x4b
b04cdc4c 805d2477 89bd12a0 00000001 89ccf760 win32k!W32pThreadCallout+0x3d
b04cdcf0 805d27e9 40010004 b04cdd4c 804ff93f nt!PspExitThread+0x3f1
b04cdcfc 804ff93f 89ccf760 b04cdd48 b04cdd3c nt!PsExitSpecialApc+0x23
b04cdd4c 80541687 00000001 00000000 b04cdd64 nt!KiDeliverApc+0x1af
b04cdd4c 7c90e4f4 00000001 00000000 b04cdd64 nt!KiServiceExit+0x59
0fd5ff44 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: .thread 0xffffffff89bd12a0 ; kb

FOLLOWUP_IP:
nv4_disp+ee830
bf100830 7234 jb nv4_disp+0xee866 (bf100866)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_disp+ee830

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 49b4618c

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2009_03_09

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2009_03_09

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

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,290 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:13 AM

Posted 03 January 2010 - 11:34 AM

I would boot into safe mode...then go to Device Manager and uninstall the video drivers...then reboot and see if that changes things.

It appears that the driver may be damaged, functioning inappropriately.

Louis

#5 nuic

nuic
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:09:13 AM

Posted 03 January 2010 - 11:39 AM

but i have problem i can't boot into safe mode
i can only into debuging mode

when i go to safe mod
when it is booting pc freeze here
http://it.tinypic.com/view.php?pic=10ichv6&s=6
picture is bad because i took it whit mobile phone


Edit: Edited to remove unnecessary quote. ~ tg

#6 nuic

nuic
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:09:13 AM

Posted 04 January 2010 - 05:47 AM

refresh of my problem
do anyone know solution of my problem

#7 Nikas

Nikas

  • Members
  • 650 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Singapore
  • Local time:04:13 PM

Posted 04 January 2010 - 07:19 AM

You can choose to do a repair of your Windows provided that you have the disc with you.

The log that you posted, suggest that your graphic card drive might have some issue. Do a update of your drive to the latest version through nvidia website.

#8 nuic

nuic
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:09:13 AM

Posted 04 January 2010 - 11:19 AM

i have newest drivers but it still don't work

#9 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:04:13 AM

Posted 04 January 2010 - 11:31 AM

Boot up in whatever mode you can. Go into Add/remove Programs and uninstall all NVIDIA Video Drivers only. Reboot your computer and let it boot normally. If your computer will start in normal mode, download the previous version Nvidia Drivers from here. Install the Drivers and reboot your machine.

IF upon reboot, your computer once again blue screens with the 0X24 error, you may need to replace your video card.

Hope this helps,
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca

#10 nuic

nuic
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:09:13 AM

Posted 04 January 2010 - 01:34 PM

it didn't help
i uninstal drivers and restart my pc but then again same blue screen
i don't think that problem is in graphic card i think it is in that virus
i downoad saome program for chips then when i started it nothing hapened and after that i shut down pc
in morning i turn on pc but then show up blue screen and after then i can only run my pc in debuging mode
so is this unsolvable problem?

Edited by nuic, 04 January 2010 - 01:35 PM.


#11 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:04:13 AM

Posted 04 January 2010 - 02:21 PM

You may want to try running Malwarebytes on your computer.

Scan for Spyware/Adware

Malwarebytes' Anti-Malware a.k.a. MBAM - Download Free Version - Homepage
Why? Malwarebytes' Anti-Malware is very good at removing the zlob trojan, virtumonde, and most other current infections. This single tool has replaced multiple tools that have been required in the past.
  • 1. Double-click mbam-setup.exe and follow the prompts to install the program. At the end, confirm a check mark is placed next to the following:
    • Update Malwarebytes' Anti-Malware
    • Launch Malwarebytes' Anti-Malware
  • 2. At the end, confirm a check mark is placed next to the following:
  • 3. Then click Finish.
  • 4. If an update is found, it will download and install the latest version.
  • 5. Once the program has loaded, select Perform quick scan, then click Scan.
  • 6. When the scan is complete, click OK, then Show Results to view the results.
  • 7. Be sure that everything is checked, and click Remove Selected.
  • 8. When completed, a log will open in Notepad. The rogue application should now be gone.
Note: Some infections will prevent MBAM from running. If MBAM won't run, try renaming the file mbam-setup.exe to a random name, and then try again.

Give this a shot and let us know.
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca

#12 nuic

nuic
  • Topic Starter

  • Members
  • 29 posts
  • OFFLINE
  •  
  • Local time:09:13 AM

Posted 05 January 2010 - 12:48 PM

i had trouble with installing but i done it after same time
when i scanned my pc there were 10-15 viruses mostly trojans
i deleted them and restarted pc
and again blue screen
i still can only enter debuging mode
and every time i scan my pc anti-virus find 2 new virus
i scan it with MBAM and eset nod32

#13 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:04:13 AM

Posted 05 January 2010 - 02:17 PM

To Help the HJT Team please read the following instructions and post your results in the HijackThis Logs and Virus/Trojan/Spyware/Malware Removal forum. When you post the log, also put a link to this post so the HJT Team knows what all has been done to your computer before posting to the HijackThis Logs and Virus/Trojan/Spyware/Malware Removal forum.

Please be patient as the HJT team is quite busy sometimes and it may take a day or even a few for someone to pickup your log but someone will get back to you.

We need to see some information about what is happening in your machine. Please perform the following scan:
  • Download DDS by sUBs from one of the following links. Save it to your desktop.
  • Double click on the DDS icon, allow it to run.
  • A small box will open, with an explanation about the tool. No input is needed, the scan is running.
  • Notepad will open with the results.
  • Follow the instructions that pop up for posting the results. Post both logs (no need to zip attach.txt).
  • Close the program window, and delete the program from your desktop.
Please note: You may have to disable any script protection running if the scan fails to run. After downloading the tool, disconnect from the internet and disable all antivirus protection. Run the scan, enable your A/V and reconnect to the internet.

Information on A/V control HERE
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca

#14 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 37,011 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:04:13 AM

Posted 07 January 2010 - 08:47 AM

Hello,

Now that you have posted a log here: http://www.bleepingcomputer.com/forums/t/284973/blue-screen-error/ you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a HJT Team member, nor should you ask for help elsewhere. Doing so can result in system changes which may not show in the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the HJT Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the HJT Team members are EXTREMELY busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the HJT Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another HJT Team member is already assisting you and not open the thread to respond.

Please be patient. It may take several days, up to two weeks perhaps less, to get a response but your log will be reviewed and answered as soon as possible. I advise checking your topic once a day for responses as the e-mail notification system is unreliable.

To avoid confusion, I am closing this topic. Good luck with your log.

Orange Blossom :thumbsup:
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users