Blue screen at startup

[Guest]

My comp config, mother board ASUS M2N-E SLI, AMD Athlon64X2 Dual Core 4400+,
2Gb RAM, Windows Vista Home Premium 32-bit. I've got a problem with USB
devices. When any of USB devices are conneted (DSL Modem Thomson st330,
Logitche QuickCam Messenger)during startup I've gote BSOD. When this devices
are not connected System strat's without any problems. Drivers for this
devices was downoladed from my internet provider web site for modem, and from
Logitech web site.
Where is the problem??

 

[Meinolf Weber]

Hello OLO,

How is BIOS startup order?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

 

[Chad Harris]

Hi OLO--

I don't know which driver might be causing the BSOD, assuming the driver is
the cause of the BSOD. I don't know what the stop error says, and lately
we've had reminders to examine and debug the minidump folders but I don't
see that as necessary or doable or particularly changing the methods you'd
employ to fix Vista for the vast majority of users.

What's the stop error on the BSOD?

You say that you downloaded your driver for the Thomson DSL Modem from the
ISP web site which makes sense, but I'd try going to Thomson's site to see
what the latest driver for your modem is and also check on Logitech's site
to see what the lastest driver is for your Quick Cam.

CH

 

[Guest]

I will re-write the BSOD message in few minutes and Ipost it here. According
The web cam drivers i downloaded it 2 or 3 days ago. The same situation is
with modem i tried with drivers from Thomson web site and from my ISP.

 

[Guest]

Stop error on the BSOD is 0x0000007F (0x00000000 0x00000000 0x00000000
0x00000000)

 

[Guest]

CR-ROM then Hard Disk

Hello OLO,

How is BIOS startup order?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

 

[Chad Harris]

OLO--

When I asked for the stop error message I meant the words not just the
numbers. Every stop error has some words with it however often useless or
cryptic. They are broad umbrella categories of stop error usually that in
your case might be more specific mentioining a driver problem.

I'd just do this below and see if it helps if you are certain you have the
newest appropriate drivers from the respective device manufacturer's
sites--in your case Logitech and Thomson.

***SFC as a Remedy***:

SFC or System File Checker is a bit like the spare tire in your car or a
backup battery I suppose. In Vista of course, they have changed it somewhat
and come up with a new name--Redmond stands for name it something different
twice a year and now it's part of WRP or Windows Resource Protection. It
scans protected resources including thousands of files, libraries, critical
folders, and essential registry keys, and it replaces those that are
corrupted with intact ones. It fixes a lot of problems in Windows XP, OE,
Windows Vista, Win Mail, IE6, and on Vista or if it is installed on XP, IE7.
It protects these things from changes by any source including
administrators, by keeping a spare of most of them.


How to Run SFC:

Type "cmd" into the Search box above the Start Button>and when cmd comes up
at the top of the Start menu>right click cmd and click "run as Admin" and
when the cmd prompt comes up at the cmd prompt type "sfc /scannow" no quotes
and let it run. This may fix things quite a bit. It replaces corrupt files
with intact ones, if you're not familiar with it.

***Startup Repair from the Vista DVD***

How to Use The Vista DVD to Repair Vista (Startup Repair is misnamed by the
Win RE team and it can be used to fix many Vista components even when you
***can boot to Vista):

http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

If you elect to run Startup repair from the Vista DVD (it can fix major
components in Vista--I've verified this many many times; it's good for more
than startup problems, and the Win RE team simply screwed up when they named
it not understanding its full functionality):

Startup Repair will look like this when you put in the Vista DVD:

http://www.vistaclues.com/wp-content/uploads/2006/12/click-repair-your-computer.png

You run the startup repair tool this way (and system restore from here is
also sometimes effective):

http://support.microsoft.com/kb/925810/en-us

How To Run Startup Repair In Vista Ultimate (Multiple Screenshots)
http://www.windowsvista.windowsreinstall.com/vistaultimate/repairstartup/index.htm

It will automatically take you to this on your screen:

http://www.vistaclues.com/wp-content/uploads/2006/12/click-repair-your-computer.png

That will allow you to go to the Vista setup that has a Repair link on
thelower left corner>click it and then you'll see a gray backgrounded list
and I want you to click Startup Repair from it and follow the directions.

The gray screen after you click the first link in the above pic will look
like this:

http://www.windowsreinstall.com/winvista/images/repair/staruprepair/Image17.gif

Click Startup Repair, the link at the top and after it scans>click OK and
let it try to repair Vista. It will tell you if it does, and if it
doesn't, try System Restore from the Recovery Link on the DVD. If these
don't work booting into Safe Mode by tapping the F8 key and using System
Restore from one of the safe modes besides VGA may work. That means you
have the option to try 4 different safe modes to get to system restore, (one
from the Recovery link on the DVD) and sometimes one will work when the
others won't.


You could also try a Repair Install with Vista which is done exactly the
same way as in XP:

***Repair Install Steps*** (can be used for Vista) MVP Doug Knox
http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/tips/doug92.mspx


***Using the F8 Environment***

***Taking Full Advantage of the F8 Options (Windows Advanced Options Menu)
by starting the PC and tapping F8 once per second when the firmware screen
with the pc manufacturer's name shows a few seconds after restarting***:

The F8 options in Vista are the same as XP, and the link for Safe Mode Boot
options is labled XP by MSFT but they are the same for Vista (they haven't
updated to add Vista to the title as they have with several MSKBs that apply
to both).

Again, pressing F8 repeatedly when you seem the firmware screen may be is a
generic way to launch Windows RE on some OEM Vista computers.

You could also:

Think: I have 4 different ways to get back my XP at F8 and try 'em in order.
1) Safe Mode 2) Safe Mode with Cmd to Sys Restore which is simply a cmd
prompt in safe mode 3) Safe Mode with Neworking 4) LKG or Last Known Good
Configuration


Try to F8 to the Windows Adv Options Menu>try 3 safe modes there (I don't
use WGA) and Last Known Good>then I go to Win RE in Vista. That gives you a
choice of Safe Mode, Safe Mode with Networking,and Safe Mode with Command
Prompt.

These methods are outlined in

A description of the Safe Mode Boot options in Windows XP/and Vista
http://support.microsoft.com/kb/315222/

Frequently Asked Questions Regarding System Restore from MSFT:

http://www.microsoft.com/technet/prodtechnol/winxppro/plan/faqsrwxp.mspx

System Restore can be run from the Win RE recovery environment from the same
link as Startup Repair, and sometimes it will work from one F8 safe mode
location or from the Win Recovery Environment when it won't work from other
locations.

How to start the System Restore tool at a command prompt in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;304449

Good luck,

CH

 

[Chad Harris]

OLO--

This modification also might prevent a BSOD of the type you're describing
although I'd like to see the words with the numbers that are on your BSODs.
I understand you're blue screening when you plug the respective usbs in for
two specific devices. I want you to reconfigure Verifier Manager to stop
the inspection of antivirus software drivers in driver verifier and to stop
deadlock detection. This won't interfere with the running of your AV, and
sometimes when you're getting BSODs you think are driver induced this stops
them.

Many Stop Error Messages are blamed on corrupt HDW drivers when this is
simply not the case. What is really going on is that the Verifier tool-- is
inspecting software drivers from 3rd parties like Norton (5 drivers).

Someone at MSFT wrote this and some people made that tool described in these
two links: http://www.microsoft.com/whdc/DevTools/tools/Verifier.mspx
http://www.microsoft.com/whdc/devtools/ddk/default.mspx

They need to talk to the people who are writing MSKBs blaming hardware
drivers in the kernel stack for the blue screens/stop errors.

This becomes significant when MSFT has speakers and many MVPs who espouse
the idea that 60%-80% of blue screens are because of drivers. I have seen
this said by MSFT at a meeting at MSFT several times during Windows XP.
That's just not the case. The errors say something ridiculous like "A kernel
stack driver is corrupt so Windows Was Shut Down." If you do a driverquery
by typing "driverquery" at the command prompt without the quotes, you can
find 100-200 kernel stack drivers or more. ***If it were a HDW driver how
would you determine which one?*** Trial and error would be time consuming.
And it isn't necessary. It's a matter in most cases of configuring the
verifier tool not to inspect the offending driver.

So do this to stop Deadlock Detection

Type verifier in the run box. That will bring up Verifier Manager which
most people don't know exists and never will but it can stop blue screens
that claim some drivers are causing them some times. When you get to the
step where you click or check the drivers you want to verify, leave the
drivers with the name of your Antivirus Program unchecked (for inspection).

1. Click Start, click Run, and then type verifier.
2. After Driver Verifier Manager starts, click Display Existing Settings,
and then confirm that Deadlock Detection is turned on.
3. Click Back.
4. Click Create Custom Settings, and then click Next.
5. Click Select Individual settings from a full list, and then click Next.
6. Click the settings that you want to turn on, make sure the Deadlock
Detection check box is not selected, and then click Next.
7. Click the drivers that you want to verify, and then click Next or Finish
if you choose all drivers on your computer.
8. Restart the computer.

Good luck,

CH

 

[Guest]

This is the major things from blue screen I think
"Run a system diagnostic utility supplied by your hardware manufacturer. In
particular run memory check and check for faulty or mismatched memory. Try
changing video adapters
Disable or remove any newly installed hardware and drivers. Disable or
remove any newly instaled software If you need to use safe mode to remove or
disable components restart your computer press F8 to select ASO and then
select safe mode.
Technical
0x0000007F(0x00000000 0x00000000 0x00000000)
And then are text about succesfully dumping phisical memory to disk.

 

[Guest]

I've just run SFC and I received info that failed files was found but is
unable to repair it and then that the details are in CBS.log file