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

Display Driver Keeps crashing (NVidia)


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

#1 SashyCakes

SashyCakes

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:00 PM

Posted 02 January 2013 - 01:14 AM

Hi there, hope I started this topic in the right manner. Here are the computer specs:

Vista Home Basic (6.0 Build 6002)
System Manufacturer: Gigabyte Techonology Co., LTD
System Model: p55m-UD2
BIOS: Award modular Bios v. 6.00PG
Processor: Intel Core i7 cpu 860 @ 2.80 GHz (8 CPU's) ~2.8 GHz
Memory: 4090MB RAM

When I play league of legends sometimes the game will freeze up, the screen will go blank for a few seconds, then it will resume, but I will get an error message saying that the nvidia display driver has crashed. This has been happening for the past month or so, but theres a lot of things wacky with this computer. I just ran combo fix, malware bytes, adw cleaner, and scanned with avast which showed up a lot of files that needed to be deleted, so this computer is a mess in general (its my friends). Sometimes it blue screens, but it hasnt since I started attempting to clean it out.

So I guess Im asking: What else should I run to get this computer clean? Is there anyway to address the graphics problem directly or should I just continuing cleaning and if so how? Thanks! (Ive already updated the graphics driver)

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:00 PM

Posted 02 January 2013 - 07:35 AM

If you suspect malware you should post in the Am I Infected forum on this site.

#3 SashyCakes

SashyCakes
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:00 PM

Posted 02 January 2013 - 12:21 PM

I dont think spyware is the issue but I started cleaning it anyway. I have no idea how to address the driver card failing issue =/.

#4 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:00 PM

Posted 02 January 2013 - 12:35 PM

1) You said there is a lot "whacky" with the computer without describing anything specific

2) You ran combofix

3) You said Avast found "files that needed to be deleted". Again, without being specific.

Based solely on the above I suggested you post in the Am I Infected forum.

#5 SashyCakes

SashyCakes
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:00 PM

Posted 02 January 2013 - 12:40 PM

I have posted there, but I honestly don't believe malware is tied to the video card issue: this is the error I get from the video card: ""Display Driver nvlddmkm Stopped Responding" then it says it has recovered.

I also got a blue screen error last night:

Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.2
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C000001D
BCP2: FFFFF80003AB3C4E
BCP3: FFFFFA60081B1230
BCP4: 0000000000000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Is this more useful?

It also will only boot into a black screen and a mouse cursor half the time... I turned the computer on, showered for about half an hour and came back and it still hadn't booted, so I had to restart to get it to boot to the desktop.

Edited by SashyCakes, 02 January 2013 - 12:41 PM.


#6 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:00 PM

Posted 02 January 2013 - 12:44 PM

1) Does the video card issue happen only when you play that game?

2) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

3) Do you have Windows Update set to download only critical updates? You should NEVER allow Windows Update to install new drivers.

4) Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#7 SashyCakes

SashyCakes
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:00 PM

Posted 02 January 2013 - 12:54 PM

1.) It happens most frequently with that game, but that's currently the only game being played right now and it happens sporadically in it, I can't seem to find a way to trigger it. However it also happens sometimes when a youtube page + facebook are opened in quick sucession.

2.) Nothing-- this game was installed in September and the issue started in November. Avast had to be reinstalled as it stopped working recently and ADW cleaner and combofix were downloaded but this was within the past few days, so I don't think they caused the issue.

3.) Windows was set to download updates and install them ( I changed that to download but let me choose when to install), but it said updates were last installed "never" which is weird.

4.) I'm pasting all the BSOD errors within the past month... there were 793 errors that came up when blue screen viewer loaded them all.

==================================================
Dump File : Mini010213-01.dmp
Crash Time : 1/2/2013 12:28:34 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff800`03ab3c4e
Parameter 3 : fffffa60`081b1230
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+57ad0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini010213-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 280,840
==================================================

==================================================
Dump File : Mini010113-01.dmp
Crash Time : 1/1/2013 10:35:52 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`00293224
Parameter 3 : fffffa60`0d10a970
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+203224
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini010113-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 287,584
==================================================

==================================================
Dump File : Mini122712-04.dmp
Crash Time : 12/27/2012 1:30:25 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005002
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`00013b20
Parameter 4 : 40014172`fffffffe
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+57ad0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122712-04.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 283,480
==================================================

==================================================
Dump File : Mini122712-03.dmp
Crash Time : 12/27/2012 1:13:15 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffffa60`02a9aa8d
Parameter 3 : fffffa60`0da89070
Parameter 4 : 00000000`00000000
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+8fa8d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122712-03.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 290,408
==================================================

==================================================
Dump File : Mini122712-02.dmp
Crash Time : 12/27/2012 11:11:57 AM
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00000000`76ed6f9a
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`ffffffff
Parameter 4 : fffffa60`0b130ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+57ad0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122712-02.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 280,744
==================================================

==================================================
Dump File : Mini122712-01.dmp
Crash Time : 12/27/2012 11:10:06 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03aae794
Parameter 3 : fffffa60`0cc726c8
Parameter 4 : fffffa60`0cc720a0
Caused By Driver : swenum.sys
Caused By Address : swenum.sys+8e77900
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+68794
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122712-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 290,408
==================================================

==================================================
Dump File : Mini122212-02.dmp
Crash Time : 12/22/2012 7:25:26 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffffa60`011b460b
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : ecache.sys
Caused By Address : ecache.sys+860b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122212-02.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 280,992
==================================================

==================================================
Dump File : Mini122212-01.dmp
Crash Time : 12/22/2012 7:22:56 PM
Bug Check String : DRIVER_PORTION_MUST_BE_NONPAGED
Bug Check Code : 0x000000d3
Parameter 1 : fffff960`00357d33
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`03a84545
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+277d33
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini122212-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 290,064
==================================================

==================================================
Dump File : Mini121312-01.dmp
Crash Time : 12/13/2012 4:34:34 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03a794c5
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+57ad0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+57ad0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini121312-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 6002
Dump File Size : 280,992
==================================================

#8 rotor123

rotor123

  • Moderator
  • 8,093 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:00 PM

Posted 02 January 2013 - 02:39 PM

Since there is a topic open in the "Am I Infected" forum, Please make no changes in the computer except by direction of the helper there. Working in two different messages will cause confusion and slow the repair down.

As a result I am closing this one down until the all clear from the Am I Infected forum.

If you would rather work here or feel this closure is in error please PM myself or another moderator to reverse the closure.

Roger

Sorry Allan, If You would like it reopened please PM me.
Happy New Year

Edit: Reopening this one at SashyCakes request.
Roger

Edited by rotor123, 04 January 2013 - 01:58 PM.

Fortune Cookie says: Fortune not Found: Abort, Retry, Ignore?

Sent from my All-In-One Desktop. Perfect for Internet, Not for heavy usage or gaming however.

How Does a computer get Infected? http://www.bleepingcomputer.com/forums/t/2520/how-did-i-get-infected/
Forum Rules,    The BC Welcome Guide

167 @ June 2015


#9 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:00 PM

Posted 04 January 2013 - 02:23 PM

Your errors are multiple and varied. Two frequent causes are major hardware failure (including mobo or cpu) or malware. i continue to suspect malware. However, there are some other things we can try while you're waiting for a reply in the malware forum:

1) Look in device manager - are there any yellow or red symbols?

2) Let's check the ram: download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

3) Next is checkdisk: right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

4) Download and run Mike Lin's Startup Control Panel (mike lin's startup control panel). Look at all the tabs and see if there is anything you aren't familiar with. If not, uncheck everything on all tabs and reboot. Now play your game and see if the system blue-screens.


#10 rotor123

rotor123

  • Moderator
  • 8,093 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:00 PM

Posted 04 January 2013 - 10:30 PM

As has been said Malware is high on the list of suspects for the Blue screen problem.

Since you ran Combofix what I'd like to see happen is that you open a post in the Virus, Trojan, Spyware, and Malware Removal Logs I believe this will result in the fastest fix of your problem.

Follow the Preparation Guide
From the Preparation guide please read and follow these steps.
step 1 Backup your data!
Step 4 Enable topic reply notification by default.
Step 5 Enable a firewall

Step 6 Download and Run DDS which will create a log of programs running on your computer.
Step 7 Create a new malware removal topic and post the DDS logs
Step 8 What to expect now that you have created your topic.

Post Your Combofix Log also since it was run. The log should be located at C:\ComboFix.txt

Please let me know when this has been accomplished.

Thank You
Roger

Edited by rotor123, 04 January 2013 - 10:31 PM.

Fortune Cookie says: Fortune not Found: Abort, Retry, Ignore?

Sent from my All-In-One Desktop. Perfect for Internet, Not for heavy usage or gaming however.

How Does a computer get Infected? http://www.bleepingcomputer.com/forums/t/2520/how-did-i-get-infected/
Forum Rules,    The BC Welcome Guide

167 @ June 2015


#11 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:00 PM

Posted 05 January 2013 - 08:01 AM

In addition to what Rotor said, Combofix is a fairly powerful tool that can make changes you may not be aware and may cause additional problems if you aren't used to using it. The malware specialists on this site are well trained and highly equipped to deal with such issues.

#12 SashyCakes

SashyCakes
  • Topic Starter

  • Members
  • 18 posts
  • OFFLINE
  •  
  • Local time:03:00 PM

Posted 05 January 2013 - 12:08 PM

Your errors are multiple and varied. Two frequent causes are major hardware failure (including mobo or cpu) or malware. i continue to suspect malware. However, there are some other things we can try while you're waiting for a reply in the malware forum:

1) Look in device manager - are there any yellow or red symbols?

2) Let's check the ram: download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

3) Next is checkdisk: right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

4) Download and run Mike Lin's Startup Control Panel (mike lin's startup control panel). Look at all the tabs and see if there is anything you aren't familiar with. If not, uncheck everything on all tabs and reboot. Now play your game and see if the system blue-screens.



1.) There aren't.

2.) I'll need to get a blank CD to do this.

3.) I ran this and there was no change.

4.) Everything seems to be fine, all the weird things I see I googled and seem to be part of the sound card here.

I ran combofix with the help of a friend who I think is moderately versed in this stuff-- but he was at a loss for what to do because the problem still exists. However the computer does boot faster now, though it still has all of it's issues besides. Rotor I'll open up a topic there.

Thanks for all your help, I am super frustrated with this computer.

#13 hamluis

hamluis

    Moderator


  • Moderator
  • 56,286 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:00 PM

Posted 05 January 2013 - 12:57 PM

Reference: http://www.bleepingcomputer.com/forums/topic480751.html/page__p__2939419#entry2939419

Now that you have properly posted a malware log topic, 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 MRT 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 MRT 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 MRT 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 MRT 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 MRT Team member is already assisting you and not open the thread to respond.

It may take several days 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.

If HelpBot replies to your topic, PLEASE follow Step One so it will report your topic to the team members.

To avoid confusion, I am closing this topic.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users