Vista Users! How to / Problems

PC eye · 01-04-2008, 07:10 AM

Using the driver removal tool provided NVidia and going for update that may see a correction would likely see better results. A newer version usually will remove the existing drivers as part of the installatio process however.

Kornowski · 01-04-2008, 12:16 PM

I have the latest nVidea drivers, I also had the ones that came with my card on a CD, I was getting the BSOD with them too, so I got the newest ones, and it still happens?

PC eye · 01-04-2008, 11:30 PM

I ran into that when first getting the new build up and running here with the ATI model used. The drivers on the cd were useless and the Catalyst 7.9 was also a headache for both XP and Vista alike. You are not the only one with an 8800 to be running into this either.

The 7,10 to later come after the patch ATI released for the 7.9 cleaned things up for Vista while XP still suffered from partial washouts of the Start taskbar. The 7.11 finally saw a working set for XP there.

Apparently you will have to keep an eye out for the next update and save it to a folder somewhere once found to have a working set of drivers in that. The main problem being seen all this time is simply the rush to get new models out before seeing working driver sets available!

Kornowski · 01-09-2008, 01:44 AM

So, do you think if I remove all the Windows Updates and install them one-by-one I can find out which one it is?

PC eye · 01-09-2008, 02:30 AM

Forget Vista's SP1 when that comes out then. The latest NVidia drivers could very well be the problem rather then any MS updates for seeing the BSODs there. I've heard from a few running into the same driver problem with 8800s as was seen here with the AYI model.

The next release may clean all of the problems there right up. Keep an eye for the next update that follows the one you just installed to see if that is the problem. You can try rolling back the updates and try each one by itself. But the blue screens always seem to fall back on device drivers of some type.

SirKenin · 01-09-2008, 03:09 AM

You don't have to do that. Tell the guy to read a computer book or two and actually get with the program. The guy is stuck in the 80's.

All you have to do is go to the event viewer and find out what date and time the error started happening. Then, go into Control Panel > Windows Update and click on "View Update History". Remove anything installed after that time and you'll find out whether it's a Windows Update that's causing the problem.

First, though, from the Event Viewer tell us what the exact error is.

If you take any advice from that guy he'll have you out buying a new computer, throwing yours out the window in frustration, or both.

Kornowski · 01-09-2008, 01:40 PM

There's a lot of Volcum Shadow Copy errors, but there's also a ton of others, I mean a load!

Is there any way that I can upload them so that people who know what to look for can see?

The BSOD has been happened after I used MS Update, it was like the first day I got Vista installed...

Dave, I have the latest nVidea drivers, I've also tried older ones but I get the same problem.

PC eye · 01-10-2008, 01:40 AM

You may have seen a bad install of Windows itself. Have you been able to remove the updates by going back at all? The problem with BSODs is not being able to use a screen capture utility to take a snapshot of the actual information seen for the brief moment.

Being fast and hitting the pause/break key can sometime freeze everything so you can write down the information displayed. What the MS updates may have also seen is the autpmatic download of the wrong drivers for something if one of the security updates didn't go on backwards.

Make a note on the latest NVidia driver set's version number and still keep an eye out for a patch or the next if it does turn out to be a problem with the drivers. But you may end up having to go ahead with a total fresh install of Windows all over again in order to get things running the way they should. It's time consuming but often cleans up the problem easier in the long run if you can't isolate the problem to one thing.

Kornowski · 01-10-2008, 08:53 AM

I have a picture of the BSOD, it's a few pages back...

PC eye · 01-11-2008, 12:28 AM

That will be two pages back with this reply for sure.

Without being able to see the left side of the screen to see if anything more like "unexpected_kernal_mode_trap" is seen along with the rest of the error the following information points out the likely cause for seeing this other then any video driver issue.

Symptoms

You may receive get the error on Windows:
”STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP) “
Cause

This can arise if the either of following circumstances arise:

>Computer has hardware/software issues

>Computer's processor speed has been altered (e.g. processor is set at 150 MHz running at 187 MHz).

The STOP error above is due to a trap having occurred in kernel mode. The most common causes of ‘STOP 0x7F’ are:

>Low-level hardware corruption (corrupt memory)
>Mismatched memory modules
>Faulty motherboard

To determine an approximate cause, examine the parameters at the top of the STOP screen:
**STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000)
UNEXPECTED_KERNEL_MODE_TRAP

The most important parameter is the first (0x0000000X) which can contain various different values. This occurs depending on the value of the parameter. Traps that cause a ‘STOP 0x7F’ are found in the Intel x86 microprocessor manual. http://www.accessdatabaserepair.com/kb/Q137539.htm

You did mention ocing already with the new build there. The information seen there also confirms the MS information on this type of error message at http://support.microsoft.com/kb/137539

CAUSE

This error message can occur if either of the following conditions exists:
•Your computer has hardware or software problems (hardware failure is the most common cause).
•You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ).

The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal.

The most common causes of a STOP 0x7F are:
•Low-level hardware corruption, such as corrupt memory (RAM)
•Mismatched memory modules
•A malfunctioning motherboard

01-04-2008, 07:10 AM	#71 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 19,226	Using the driver removal tool provided NVidia and going for update that may see a correction would likely see better results. A newer version usually will remove the existing drivers as part of the installatio process however. __________________ Turning auto exhaust into a new energy source http://abcnews.go.com/Technology/Ahe...ory?id=5552209 Ahead of theCurve: Extreme gamers play 45hrs. a week http://blogs.abcnews.com/aheadofthec...extreme-g.html

01-04-2008, 11:30 PM	#73 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 19,226	I ran into that when first getting the new build up and running here with the ATI model used. The drivers on the cd were useless and the Catalyst 7.9 was also a headache for both XP and Vista alike. You are not the only one with an 8800 to be running into this either. The 7,10 to later come after the patch ATI released for the 7.9 cleaned things up for Vista while XP still suffered from partial washouts of the Start taskbar. The 7.11 finally saw a working set for XP there. Apparently you will have to keep an eye out for the next update and save it to a folder somewhere once found to have a working set of drivers in that. The main problem being seen all this time is simply the rush to get new models out before seeing working driver sets available! __________________ Turning auto exhaust into a new energy source http://abcnews.go.com/Technology/Ahe...ory?id=5552209 Ahead of theCurve: Extreme gamers play 45hrs. a week http://blogs.abcnews.com/aheadofthec...extreme-g.html

01-09-2008, 02:30 AM	#75 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 19,226	Forget Vista's SP1 when that comes out then. The latest NVidia drivers could very well be the problem rather then any MS updates for seeing the BSODs there. I've heard from a few running into the same driver problem with 8800s as was seen here with the AYI model. The next release may clean all of the problems there right up. Keep an eye for the next update that follows the one you just installed to see if that is the problem. You can try rolling back the updates and try each one by itself. But the blue screens always seem to fall back on device drivers of some type. __________________ Turning auto exhaust into a new energy source http://abcnews.go.com/Technology/Ahe...ory?id=5552209 Ahead of theCurve: Extreme gamers play 45hrs. a week http://blogs.abcnews.com/aheadofthec...extreme-g.html

01-10-2008, 01:40 AM	#78 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 19,226	You may have seen a bad install of Windows itself. Have you been able to remove the updates by going back at all? The problem with BSODs is not being able to use a screen capture utility to take a snapshot of the actual information seen for the brief moment. Being fast and hitting the pause/break key can sometime freeze everything so you can write down the information displayed. What the MS updates may have also seen is the autpmatic download of the wrong drivers for something if one of the security updates didn't go on backwards. Make a note on the latest NVidia driver set's version number and still keep an eye out for a patch or the next if it does turn out to be a problem with the drivers. But you may end up having to go ahead with a total fresh install of Windows all over again in order to get things running the way they should. It's time consuming but often cleans up the problem easier in the long run if you can't isolate the problem to one thing. __________________ Turning auto exhaust into a new energy source http://abcnews.go.com/Technology/Ahe...ory?id=5552209 Ahead of theCurve: Extreme gamers play 45hrs. a week http://blogs.abcnews.com/aheadofthec...extreme-g.html

01-11-2008, 12:28 AM	#80 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 19,226	That will be two pages back with this reply for sure. Without being able to see the left side of the screen to see if anything more like "unexpected_kernal_mode_trap" is seen along with the rest of the error the following information points out the likely cause for seeing this other then any video driver issue. Symptoms You may receive get the error on Windows: ”STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP) “ Cause This can arise if the either of following circumstances arise: >Computer has hardware/software issues >Computer's processor speed has been altered (e.g. processor is set at 150 MHz running at 187 MHz). The STOP error above is due to a trap having occurred in kernel mode. The most common causes of ‘STOP 0x7F’ are: >Low-level hardware corruption (corrupt memory) >Mismatched memory modules >Faulty motherboard To determine an approximate cause, examine the parameters at the top of the STOP screen: STOP 0x0000007F (0x000000XX, 0x00000000, 0x00000000, 0x00000000) UNEXPECTED_KERNEL_MODE_TRAP The most important parameter is the first (0x0000000X) which can contain various different values. This occurs depending on the value of the parameter. Traps that cause a ‘STOP 0x7F’ are found in the Intel x86 microprocessor manual. http://www.accessdatabaserepair.com/kb/Q137539.htm You did mention ocing already with the new build there. The information seen there also confirms the MS information on this type of error message at http://support.microsoft.com/kb/137539 CAUSE This error message can occur if either of the following conditions exists: •Your computer has hardware or software problems (hardware failure is the most common cause). •You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ). The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are: •Low-level hardware corruption, such as corrupt memory (RAM) •Mismatched memory modules •A malfunctioning motherboard __________________ Turning auto exhaust into a new energy source http://abcnews.go.com/Technology/Ahe...ory?id=5552209 Ahead of theCurve: Extreme gamers play 45hrs. a week** http://blogs.abcnews.com/aheadofthec...extreme-g.html

01-09-2008, 03:09 AM	#76 (permalink)
SirKenin banned Join Date: Aug 2006 Posts: 4,711	You don't have to do that. Tell the guy to read a computer book or two and actually get with the program. The guy is stuck in the 80's. All you have to do is go to the event viewer and find out what date and time the error started happening. Then, go into Control Panel > Windows Update and click on "View Update History". Remove anything installed after that time and you'll find out whether it's a Windows Update that's causing the problem. First, though, from the Event Viewer tell us what the exact error is. If you take any advice from that guy he'll have you out buying a new computer, throwing yours out the window in frustration, or both.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Vista theme for everybody!	Kornowski	Desktop Computers	257	03-31-2008 12:03 PM
For all Vista users. Update Display Drivers. and a good vista site.	alexandergre	Operating Systems	1	03-07-2007 12:10 AM
Problems with vista burning DVD's????	moremgd32	CD/DVD Technology	0	02-23-2007 06:05 AM
Vista Upgrade Problem - All Help Appreciated - 'damsel in distress'	Redtiz	Operating Systems	6	01-22-2007 01:27 AM
Windows Vista problems	Absum!	Desktop Computers	9	04-29-2006 08:20 AM