Articles

Solved How do I fix my blue screen of death?

March 18, 2012 at 20:16:42
Specs: Windows XP, 3.8 GHz / 3070 MB

I've been having frequent BSOD's and I'm not sure what's the cause, I don't believe it's a hardware issue though. Another thing that may be related is that Chrome crashes a lot with Microsoft Visual C++ Runtime Error and Chrome Has Encountered a Problem.

See More: How do I fix my blue screen of death?

Report •


✔ Best Answer
March 18, 2012 at 22:04:56

"" quote the STOP: 0X......... error
(we don't need the stuff in brackets to the right of that)""

"It's STOP: 0x0000000A (0x00000007, 0x00000002, 0x00000001, 0x804E2EF) "

What part of (we don't need the stuff in brackets to the right of that) do you not understand !
The stuff in brackets is usually specific only to your computer, and useless regarding searching the web with it.

You can get the IRQL_NOT_LESS_OR_EQUAL error from many causes, but sometimes it can be just because the ram module contacts are not getting a good connection - this worked for me when I got that error:

A common thing that can happen with ram, even ram that worked fine previously, is the ram has, or has developed, a poor connection in it's slot(s).
This usually happens a long time after the ram was installed, but it can happen with new ram, or after moving the computer case from one place to another, and I've had even new modules that needed to have their contacts cleaned.

See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
http://www.computing.net/hardware/w...

For a laptop, or netbook, you must remove both its main battery and AC adapter before you do that.

For a brand name computer, see the Owner's or User's manual if you need to - how to remove or replace the ram is usually in that - it may already be in your installed programs. If you can't get into Windows, it may be on a disk that came with the computer, or you can go online and look at it or download it - it's in the downloads for your specific model.

For a generic desktop computer, see the mboard manual if you need to - how to remove or replace the ram is usually in that.
..............


The dump file is useless as is. It has to be "translated"

Search for: WhoCrashed on the web, download it, install it.

If you can still get into Windows on your own computer sometimes, install WhoCrashed on your own computer, run it, click on Analyze at the top of it. It finds dump files automatically.

If you can't get into Windows, the dump file can be copied (if you boot the computer from something such as a Windows CD or a Linux disk) and placed on another computer that's running Windows in a certain folder and WhoCrashed can analyze it on that computer.

Sometimes the info WhoCrashed provides about the error is specific, which is useful, sometimes it's generic, which is not.
That's just the way it is for dump files.



#1
March 18, 2012 at 20:36:18

If the message stays on the screen,
- quote the STOP: 0X......... error
(we don't need the stuff in brackets to the right of that)
- quote ANY_MESSAGE_IN_CAPITALS_WITH_UNDERLINES_BETWEEN
- if there is a problem file named, it's often near the end of the text - quote that if you see it.
- tell us whether it says it made a memory dump.
(The memory dump file can be analyzed.)
....

If the message does NOT stay on the screen, the computer Restarts

- if Windows works okay sometimes

Win XP is set by default to automatically Restart when it encounters an unrecoverable error.

To have XP possibly display an error message you can investigate instead of the computer rebooting:

1. Click Start, and then right-click My Computer.
2. Click Properties.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. Under System failure, click on the small box beside Automatically restart to remove the checkmark.
5. Click OK, and then click OK.

If you then get an error message, look at all of it's details.
.....

- If you can't get into Windows, or if you can but you get the blue screen too soon and the computer restarts

Press F8 while booting the computer, don't hold down the key, and when the Advanced.... menu appears, choose
Disable auto restart.......
(it's a one time setting - you must choose it each time)

When you get an error message, look at all of it's details.
.................

"Another thing that may be related is that Chrome crashes a lot with Microsoft Visual C++ Runtime Error and Chrome Has Encountered a Problem."

You may need to un-install Chrome and install it again properly, or un-install
Microsoft Visual C++ and install it again properly.

NOTE that sometimes the resident module(s) of anti-malware programs - a part that runs all the time scanning for suspicious activity - will interfere with the proper installation of third party software, or major Microsoft updates that cannot be installed automatically by Automatic Update, the software will not install properly, and you may get no indication of that at all while installing the software.
To avoid that possibilty, you should always DISABLE the resident module(s) of anti-malware programs, BEFORE you install third party software (software other than most Microsoft Updates, etc., that did not come with Windows ), especially when it's a major or complicated software package.
E.g. if you are using the free or paid version of AVG, you should disable the Resident Shield in AVG's 's settings in Windows (in AVG 2012 that's done under the title AntiVirus). In Norton (Symantec) products, there may be several things you need to disable, or set so they don't load for a specific short amount of time.
If you don't know how to do that, tell us which anti-malware software you are using.
When you are sure the software has installed correctly, re-enable the resident module(s).

Further info...

How to disable your security applications
http://www.techsupportforum.com/for...


Report •

#2
March 18, 2012 at 20:58:18

It's STOP: 0x0000000A (0x00000007, 0x00000002, 0x00000001, 0x804E2EF) or so and the message is irql_not_less_or_equal

Report •

#3
March 18, 2012 at 21:12:03

The dmp file is here

http://www.mediafire.com/?kmm3n8t2f...

I have also disabled the resident shield for AVG but I also have Malwarebytes running


Report •

Related Solutions

#4
March 18, 2012 at 21:36:29

Your disk might have bad sectors or has physical damages.

You should run a bad sector repairing or replace disk to try whether the disk error.


Report •

#5
March 18, 2012 at 21:42:29

As I said, I don't believe it to be a hardware issue as I have already double checked on that, I'll try again though.

Report •

#6
March 18, 2012 at 22:04:56
✔ Best Answer

"" quote the STOP: 0X......... error
(we don't need the stuff in brackets to the right of that)""

"It's STOP: 0x0000000A (0x00000007, 0x00000002, 0x00000001, 0x804E2EF) "

What part of (we don't need the stuff in brackets to the right of that) do you not understand !
The stuff in brackets is usually specific only to your computer, and useless regarding searching the web with it.

You can get the IRQL_NOT_LESS_OR_EQUAL error from many causes, but sometimes it can be just because the ram module contacts are not getting a good connection - this worked for me when I got that error:

A common thing that can happen with ram, even ram that worked fine previously, is the ram has, or has developed, a poor connection in it's slot(s).
This usually happens a long time after the ram was installed, but it can happen with new ram, or after moving the computer case from one place to another, and I've had even new modules that needed to have their contacts cleaned.

See response 2 in this - try cleaning the contacts on the ram modules, and making sure the modules are properly seated:
http://www.computing.net/hardware/w...

For a laptop, or netbook, you must remove both its main battery and AC adapter before you do that.

For a brand name computer, see the Owner's or User's manual if you need to - how to remove or replace the ram is usually in that - it may already be in your installed programs. If you can't get into Windows, it may be on a disk that came with the computer, or you can go online and look at it or download it - it's in the downloads for your specific model.

For a generic desktop computer, see the mboard manual if you need to - how to remove or replace the ram is usually in that.
..............


The dump file is useless as is. It has to be "translated"

Search for: WhoCrashed on the web, download it, install it.

If you can still get into Windows on your own computer sometimes, install WhoCrashed on your own computer, run it, click on Analyze at the top of it. It finds dump files automatically.

If you can't get into Windows, the dump file can be copied (if you boot the computer from something such as a Windows CD or a Linux disk) and placed on another computer that's running Windows in a certain folder and WhoCrashed can analyze it on that computer.

Sometimes the info WhoCrashed provides about the error is specific, which is useful, sometimes it's generic, which is not.
That's just the way it is for dump files.


Report •

#7
March 18, 2012 at 22:21:57

WhoCrashed helped clarify the .dmp files, thanks.

Report •

#8
March 18, 2012 at 23:08:08

This site may help: http://aumha.org/a/stop.php

Report •

#9
March 19, 2012 at 07:22:47

Thanks for the thanks.

If cleaning the contacts on the ram modules and re-seating them doesn't help, provide the info about what WhoCrashed said.


Report •

#10
March 19, 2012 at 15:43:26

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Mon 3/19/2012 4:39:20 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-06.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x2A017)
Bugcheck code: 0x1000000A (0x7, 0x2, 0x1, 0xFFFFFFFF804E22EF)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 3/19/2012 4:18:38 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-05.dmp
This was probably caused by the following module: npfs.sys (Npfs+0x5F94)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8054ACC7, 0xFFFFFFFFAF812AA8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that a kernel-mode program 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 3/19/2012 4:05:35 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73FCB)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8054AFCB, 0xFFFFFFFFAFF79864, 0x0)
Error: KERNEL_MODE_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 kernel-mode program 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.


On Mon 3/19/2012 2:55:40 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x42E6E)
Bugcheck code: 0x1000000A (0xFFFFFFFFC790600D, 0x2, 0x0, 0xFFFFFFFF80519E6E)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 3/19/2012 1:33:15 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x22AC9)
Bugcheck code: 0x1000000A (0x4D403FDD, 0x2, 0x0, 0xFFFFFFFF804E4CB7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 3/18/2012 11:12:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-01.dmp
This was probably caused by the following module: Unknown (0x77F159E8)
Bugcheck code: 0x100000D1 (0x4226DA, 0x1D, 0x0, 0x77F159E8)
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: Unknown .
Google query: Unknown CUSTOM_ERROR

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown


That is what I got from WhoCrashed.


Report •

#11
March 19, 2012 at 20:44:34

The info provided by WhoCrashed is rather generic.
If it had named whatever "uknown" is that may be the cause of your problem.

There's probably nothing wrong with ntfs.sys or ntoskrnl.exe - they're standard Windows files. When Windows can't tell you specifically what is wrong it often lists files that are affected by the problem.


Have you tried cleaning the contacts on the ram modules and re-seating them yet ?

If no, DO THAT FIRST !
....

You have listed WhoCrashed analysis results for only 6 crash dump files, over two days.

Is it only 6 times you have gotten a BSOD ?

Do you know when it was you first got the BSODs ?

Was it after you had installed a device, or the drivers for a device, or software ?

Was it after you changed which ram you have installed ?

"Another thing that may be related is that Chrome crashes a lot ..."

Was it after you installed Chrome ?
If yes, un-install Chrome in Control Panel - Classic view - Add/Remove Programs .
If NO. try un-installing it anyway.

Try your computer for a while without it to see if you still get the BSODs.

If you get no BSODs, disable the resident modules from running in ALL of your anti-malware software BEFORE you install it again.

"I have also disabled the resident shield for AVG but I also have Malwarebytes running"

The free and paid versions of AVG's resident module, the Resident Shield, can interfere with with the installation, or possibly the un-installation. of software.

The free version of Malwarebytes has no resident module that can interfere with the installation, or possibly the un-installation, of software. The paid version of it DOES.
.....

Copy down the days and times you got those crash dumps.

Go to the Event Viewer

e.g. - Start - Run - type: eventvwr.msc (click OK or press Enter)

Look under the Applications and System headings.
See if there are any errors or warnings that occurred at a time just before a crash dump day and time

If there are such, double click on the line,
- copy down the (error or warning) Event ID number

- and copy the Description text in the grey box, ABOVE the line
"For more information, see Help and Support Center at "

Select and highlight the text, press Crtl+C (copy)
(Hold down Ctrl, type c, let go of the keys, don't type the +)

Go to Notepad,
- type the (error or warning) Event ID number you copied down for it.

- place your cursor where you want the description text to start.
Press Ctrl+V (paste)

Copy the same things for any Warning or Error that is occurring over and over again recently.

Copy the resulting text to a post here.


Report •

#12
March 19, 2012 at 21:47:29

I had more crash dump files, however, I used ccleaner which deleted them. I've tried re-installing my graphics drivers but to no avail. I'll check the Event Viewer.

What I got from the Event Viewer, most of it is from chrome crashing

4356

The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-

6E8BAC8BDD70}!new:{6295DF2D-35EE-11D1-8707-00C04FD93327}. CoGetObject returned HRESULT 8000401A.

4356

The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-

6E8BAC8BDD70}!new:{6295DF2D-35EE-11D1-8707-00C04FD93327}. CoGetObject returned HRESULT 8000401A.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1517

Windows saved user SUPPORT-01\Others registry while an application or service was still using the registry during

log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no

longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the

LocalService or NetworkService account.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.


1000

Faulting application chrome.exe, version 17.0.963.79, faulting module chrome.dll, version 17.0.963.79, fault address

0x0000eab0.

1

This event has been logged by the BugSplat crash reporting library (http://www.bugsplatsoftware.com) in partnership

with your vendor lol_beta_riotgames_com. A crash report from the application 'LOL_Public' has been successfully

logged into the BugSplat database with id=9227380.

1517

Windows saved user SUPPORT-01\Others registry while an application or service was still using the registry during

log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no

longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the

LocalService or NetworkService account.

2

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.

2

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.

2

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.

2

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.

2

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.

2

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.

2

The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.

1

The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found. The local computer may not have the

necessary registry information or message DLL files to display messages from a remote computer. You may be able to

use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information

is part of the event: NVIEW : regsvr32: Shared heap exhausted or damaged, process ID ac0, total alloc:0...
.

1

The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found. The local computer may not have the

necessary registry information or message DLL files to display messages from a remote computer. You may be able to

use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information

is part of the event: NVIEW : regsvr32: Shared heap exhausted or damaged, process ID ac0, total alloc:0...
.

1

The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found. The local computer may not have the

necessary registry information or message DLL files to display messages from a remote computer. You may be able to

use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information

is part of the event: NVIEW : regsvr32: Shared heap exhausted or damaged, process ID ac0, total alloc:0...
.

1101

.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Program Files\Driver

Manager\Driver Manager\DriverManager.exe . Error code = 0x80131047

0

All compilation assembly nodes do not exist in System.Web section group.

0

All compilation assembly nodes do not exist in System.Web section group.

0

All compilation assembly nodes do not exist in System.Web section group.

0

All compilation assembly nodes do not exist in System.Web section group.

0

All compilation assembly nodes do not exist in System.Web section group.

0

All compilation assembly nodes do not exist in System.Web section group.

0

All compilation assembly nodes do not exist in System.Web section group.


Report •

#13
March 20, 2012 at 08:15:39

You haven't answered some of my questions.

"Have you tried cleaning the contacts on the ram modules and re-seating them yet ?

If no, DO THAT FIRST ! "


" Do you know when it was you first got the BSODs ?"

If you DO know that, loading a previous System Restore restore point dated just before you first got the BSODs may cure your problem.

Was it after you had installed a device, or the drivers for a device, or software ?

Was it after you changed which ram you have installed ?

"Another thing that may be related is that Chrome crashes a lot ..."

Was it after you installed Chrome ? "
...........

Obviously, try this...

"...un-install Chrome in Control Panel - Classic view - Add/Remove Programs "

"Try your computer for a while without it to see if you still get the BSODs.

If you get no BSODs, disable the resident modules from running in ALL of your anti-malware software BEFORE you install it again. "

It's a very good idea to do that whenever you install software yourself
I recommend you do that when you get a pop up window that says some software wants to install an update. E.g. Usually it's easy to disable the Resident Shield from loading in AVG before you give permission for the update to be installed.
Also, if you have the choice of either running a program installation or downloading it and then installing it yourself, I recommend you do the latter and disable your anti-malware resident module(s) before you install it.

Note that it's possible the Chrome version had bugs. Installing a newer version, if available, may get rid of whatever the problem was
.....

Thanks for copying the info about the Events.

The ones that were errors are more important than the ones that were warnings.
Often the ones that were warnings are for things that load normally most of the time.

Did any of them have a date and time close to that of the crash dumps ?

For the time being, you can ignore error Events that have a data and time before you first got the BSODs, if you know when that was.

In the same Description box, you can click on the link below
"For more information, see Help and Support Center at "
to see if Microsoft has further info about the error, or possibly a suggested fix, but usually that doesn't help.
.....

If your problem is caused by something in the specific video drivers, in this case NVidia's, if you start up Windows so it loads in Enable VGA mode, you will NOT get the BSODs.

Press F8 repeatedly while booting, don't hold down the key, and when the Windows "Advanced...." menu appears, choose Enable VGA mode.

That loads everything that is loaded when you boot normally, except that the video is forced to use default VGA drivers.
....

If you still get the BSODs in Enable VGA mode, try pressing F8 while booting and choosing

Safe mode
or - Safe mode with networking (mode), if you want to be able to access the internet. .

Safe mode also forces the video to use default VGA drivers and it also doesn't load a lot of things that are loaded when you load Windows normally.
If you get no BSODs in Safe mode, your problem is caused by one of the things Safe mode doesn't load.
.....

I haven't had much experience with NVidia software but the experiences I've had when I had problems haven't been good.
Apparently they don't seem to care whether their software works properly with all the systems it can be used on, as long as it works fine with the majority of them.

On the other hand ATI / AMD seems to remove buggy versions of their software in a relatively short time from the AMD web site, once enough people have reported problems with a particular version to them, and they come out with a newer version that doesn't have the same bugs.

Note that when you have installed software from the disk that came with the mboard or the video card, it's more likely to have bugs, and the software on the maker's web site is less likely to have bugs.

ATI / AMD usually has separate video "drivers" installations but NVidia often doesn't and instead has a MUCH larger download that installs both main chipset and video adapter software.

You may NOT be able to un-install existing NVidia software in Safe mode or Safe mode with networking (mode), but if you can't un-install it in normal mode, usually you can un-install it in Enable VGA mode.

Note that in most cases installing newer drivers is more likely to work fine if you un-install the existing drivers BEFORE you install the newer ones.

The video drivers may be "tied" to some other part of the video related software.
E.g.
In ATI / AMD's case, the video drivers version is matched to the Catalyst version.
The video drivers version changes more often than the Catalyst version, but if the video drivers version isn't one that is matched to the existing Catalyst version, you're likely to have problems, so rather than just installing newer video drivers, both the video drivers and the matching Catalyst version should be installed.



Report •


Ask Question