It is telling me it a graphics device driver. My video card is updated, so I was wondering what else a graphic driver would relate to. I can't get my symbols to work so I am unable to use the debugging program by windows. can anyone help?

It is telling me it a graphics device driver. My video card is updated, so I was wondering what else a graphic driver would relate to. I can't get my symbols to work so I am unable to use the debugging program by windows. can anyone help?

Have you tried reinstalling the driver? Check the card to make sure it is properly seated. That would be my first step...doc

What is telling you it is a Graphics driver? Is a driver listed in the STOP error?

When does the error occur?
And what is the full error: parameters and driver?

When did the problem start, and did you try a System Restore?

no driver was listed. I wish it did. The error occurs usually when pages are loading, but sometimes it is random. I haven't received it in awhile since I haven't been online, but when I get it again I will post the parameters. I haven't tried a system restore, but I tried a clean install of xp again a few days, and I still got it then.

It will on occasion say "graphic device driver", but not all the time. Do I only need to run those memory tests once? I bought a new stick, a 256mb sometime back, but took it back when I kept getting the errors with the new stick as well. I put my 512mb back in. I will run the tests again though. I think it's hardware though too.

Ok, now I have the verifier running. No probs booting into safe mode . I am not able to do a memory test at the moment because my floppy drive won't read any of my floppy's for some reason. I also already have memtest86 on one of them, and the darn thing refuses to read any floppy's. I also followed the instructions for the windows memory tester, to burn it to cd-rom with no luck. *sigh* I'll figure out something.

Also there were a ton, ton probably not even the word, lol, of unsigned drivers

What happened when you tried to burn it? I used Roxio/Easy CD to do mine. I think it automatically associates itself to .iso files and does the right thing by it. You may need to "read the manual" for your burning software.

I have problems with floppies as well on my Dell -- finicky floppy drive; but if I try different branded floppies, I usually get some to work.

By the way once you complete a boot with "verifier.exe", it's done its test. You can still leave it enabled for future boots if you want.

Sigverif does take a bit to complete, however, and is run from within Windows.

What happened when you tried to burn it? I used Roxio/Easy CD to do mine. I think it automatically associates itself to .iso files and does the right thing by it. You may need to "read the manual" for your burning software.

I have problems with floppies as well on my Dell -- finicky floppy drive; but if I try different branded floppies, I usually get some to work.

By the way once you complete a boot with "verifier.exe", it's done its test. You can still leave it enabled for future boots if you want.

Sigverif does take a bit to complete, however, and is run from within Windows.

I got the memory test to work. I tried a different burning prgram. Turns out the program wasn't burning it right. I had it pass through all 8 tests 1x, I didn't get one error. But, when I rebooted my processor failed to be detected on boot up. Ya know how it usually comes up above the drives, well it didn't. I'd also like to add this has happened quite a few times, which makes me kinda wonder. But I was wondering if there is something strange about that in your opinion.

Also for the verifier, do I need to enable it and boot back up in normal mode, or back into safe mode? I booted back into normal after I did it.

Quote:

Sigverif does take a bit to complete, however, and is run from within Windows.

It's getting near my bed time so forgive if I'm asking something that should be obvious -- but I'm not sure what you are referring to here:

You mean your CPU??

Perhaps you have enabled something I haven't had a look at -- are you watching a detection list in the BIOS -- I see this on my Win98 system but not XP.

If you don't want "verifier" to run on every bootup (it's silent unless it detects a problem), just run: verifier /reset from Start > Run.

Quote:

are you watching a detection list in the BIOS

that may be it. It's just a screen that boots up that shows my disk drives and AMD Athlon XP. The Athlon XP is the thing that is not detecting itself sometimes. Is that also called a CPU? sorry I'm a little unfamiliar with the name of things, although I'm pretty sure it's called a processor, lol.

Also at the top it says BIOSTAR, so yeah it could be something in the bios.

The term "cpu" stands for "central processor unit" and in your case that would be the AMD processor; Athlon would be the general chipset model. If the "cpu" truly isn't detected I don't see how Windows could boot at all.

I'm afraid the win32k.sys driver doesn't narrow things much as you can see from this array of similar hits in Google > groups.

THIS THREAD HAS EXPIRED.
Are you having the same problem?
We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.