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

Blue Screen Dont Know What The Problem Is


  • Please log in to reply
6 replies to this topic

#1 Soto

Soto

  • Members
  • 97 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 07 October 2007 - 10:30 PM

Posted Image

had this before changed ram out an everything was fine now every few days this pops up

anyone know what it is?

BC AdBot (Login to Remove)

 


#2 Rollin' Rog

Rollin' Rog

  • Members
  • 52 posts
  • OFFLINE
  •  
  • Local time:04:46 AM

Posted 08 October 2007 - 02:51 AM

I don't see a driver mentioned there, but maybe we can find one:

I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to %systemroot%\minidump and copy the last few minidump files to that folder.%systemroot% is normally c:\windows. They are numbered by date. You can paste that address in address bar to get there.
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder.
4 > use the "manage attachments" in the "add" reply window to upload that zip file here as an attachment.

This might point us to a 3rd party driver causing the error, if one exists for it.




Also:

Windows has a built in driver tester that may find something.
Before using it you must ensure that you can start in Safe Mode and return from it. If verifier issues a STOP screen, rebooting in Safe Mode is the only way to reset it.

In its default configuration verifier tests "unsigned" drivers, but you should have it test all drivers under maximum conditions.

There's less to it than meets the eye in this MS article:

http://support.microsoft.com/default.aspx?...kb;en-us;244617

To run verifier simply go to Start > run and enter:

verifier.exe

and select "standard configuration" and follow the prompts.
It will run on the next reboot. If it finds something you will get a Blue Screen STOP message.
Ignore the STOP parameters -- they are specific to verifier. The only thing important is the driver file name if it finds one.

If you get a STOP screen you will have to reboot to Safe Mode and run verifier again and have it "delete existing settings"

If you do not get a STOP message you can run it again checking all drivers; driver verifier will continue to run on every boot up until you run:

verifier /reset

or use the graphical interface to delete existing settings.

Edited by Rollin' Rog, 08 October 2007 - 02:54 AM.

Microsoft MVP Shell/User

#3 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:46 PM

Posted 08 October 2007 - 02:56 AM

0x000000C2 error messages are typically caused by faulty device drivers or device software.

See the following Microsoft page for more information.

How to interpret a Stop 0xC2 or Stop 0x000000C2 error message on a Windows XP-based computer
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#4 Soto

Soto
  • Topic Starter

  • Members
  • 97 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 08 October 2007 - 11:43 AM

so its a driver situation not a hardware problem?

#5 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:46 PM

Posted 08 October 2007 - 11:55 AM

so its a driver situation not a hardware problem?

Well...it's impossible to say for sure - but it's most likely a driver problem.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#6 Soto

Soto
  • Topic Starter

  • Members
  • 97 posts
  • OFFLINE
  •  
  • Local time:07:46 AM

Posted 08 October 2007 - 11:59 AM

well thats a relief to hear, when i come back from work today im going to do what rollin rog typed up so i can get rid of this problem once and for all.

#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:46 AM

Posted 08 October 2007 - 03:19 PM

Here's a link to a brief description of the error message: http://aumha.org/a/stop.php#0xc2
Here's some more detailed info on it: http://www.osronline.com/ddkx/ddtools/bccodes_8k9z.htm

It is most likely a driver problem. The chances are good that a dump file will reveal the driver that's causing this - but should it not, the Driver Verifier tool will be able to point the way.

Here's some more info on the BSOD, how to locate dump files, and how to generate an analysis of them: http://www.bleepingcomputer.com/forums/top...tml#entry409491
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users