Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

I got these errors


  • Please log in to reply

#1
bbullet

bbullet

    New Member

  • Member
  • Pip
  • 2 posts
So i was checked my computer with WhoCrashed program, and found these errors:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Thu 7/21/2011 13:46:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072111-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0xA6AE6)
Bugcheck code: 0xEA (0xFFFFFFFF891C64B0, 0xFFFFFFFF89B1CCD0, 0xFFFFFFFF8A19C4B0, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 191.07
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 191.07
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 191.07 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation THREAD_STUCK_IN_DEVICE_DRIVER




On Sun 7/17/2011 18:24:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071711-01.dmp
This was probably caused by the following module: pcd65x2.sys (PCD65X2+0xE882)
Bugcheck code: 0x10000050 (0xFFFFFFFFBFF5003C, 0x0, 0xFFFFFFFFA2A95882, 0x2)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: pcd65x2.sys .
Google query: pcd65x2.sys CUSTOM_ERROR




On Fri 6/11/2010 16:10:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061110-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xEF037)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF805C6037, 0xFFFFFFFFB84F3CB0, 0xFFFFFFFFB84F39AC)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



can someone help me to find solution?
  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 22,298 posts
Hi bbullet :)
You need to provide information about your computer, this includes is it
a laptop or desktop, is it a custom build or brand name such as Dell or HP
and if it is provide the model name or series number.
You have requested assistance on the Vista and W7 forum but your profile
lists your OS as XP, please clarify which OS has the issue.
Couple of suggestions to start with 1: Download and save the latest video
card drivers, uninstall the present drivers, download and then run Driver
Sweeper http://phyxion.net/i...er-sweeper.html to make sure there are
no traces of the present Nvidea video drivers remaining, reboot into Safe
Mode and install the latest video drivers that you have just saved.
2: Check your system for any malware by first following the self help guide
http://www.geekstogo...cleaning-guide/ if after following the guide you
suspect there may still be an infection start a new topic on the malware forum
do not post any logs here as they are only dealt with by the malware techs, do
however provide them with a link to this thread so that they are able to see
what if any steps have already been taken.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP