XP BSOD problems 2

[ostrich69]

I just got a custom built computer 2 days ago. Everything had been working fine up until yesterday. I was just using the computer, and all of a sudden I saw a BSOD error screen flash for less then a second and my PC rebooted.

The computer rebooted fine with no errors during POST, and XP loaded fine.

When I got to my desktop I saw a message waiting "Welcome to the Found new hardware wizard. Can Windows connect to Windows Update to search for software?

Yes, this time only
Yes, now and every time I connect a device
No, not this time.

On the taskbar it prompts me that windows found new hardware "PNP Bios" If I click cancel to the new hardware wizard menu, on the taskbar it said "Windows had problems finding and installing the new hardware.

When I go to device manager there is a yellow exclamation mark on:

SCSI and raid controllers, ST3WOLF SCSI controller.

Can anyone help out? I have no idea what is going on and how to solve the situation.

 

[ski]

If it's under warranty, then send it back to the supplier to deal with the problem.
If you bought it 2nd hand and it came with driver software, then install the SCSI drivers from the supplied driver CD or driver floppy.

 

[ceh4702]

If it is under warranty, I suggest you contact the people who sold it to you and inform them of the problem. Do not open the case yourself if it is under warranty, as this may void your warranty.

BSOD is a hardware error. It can often be caused by substandard RAM or possibly a bad motherboard or any other type of hardware you might have. A video card can cause problems and even a faulty power supply can cause problems.

If you do not like my post feel free to point out your opinion or my errors.

 

[ceh4702]

So are you using SCSI Drives?

If you do not like my post feel free to point out your opinion or my errors.

 

[paparazi]

ostrich69
After the BSOD I bet your bios has defaulted and that's the reason it found new hardware, when it booted back into Windows it found devices that had otherwise been disabled.

As ceh4702 said, most likely poor quality ram, better let the supplier sort it out though!

Martin

We like members to GIVE and not just TAKE.
Participate and help others.

 

[kmcferrin]

BSOD is not always a hardware problem, it can also be caused by driver problems. If you are using a SCSI controller that has an onboard BIOS, I would suspect that something weird happened with the SCSI drivers, the system crashed, rebooted, and detected the SCSI controller again. Put that's just speculation.

 

[ostrich69]

Thanks for the replies everyone. What I don't understand is, I don't have a SCSI HD. Here are the specs of the system:

Asus A8N-E motherboard
AMD Athlon 64 X2 4200
Windows XP Pro SP2
BFG GeForce 7900 GT
Seagate Barracuda 7200.7 SATA 160 GB hardrive, plus a 120 GB IDE hardrive
Sony Dvd burner
Corsair 2 GB - 1024 x 2 PC3200 RAM
500 Watt PSU

I have 2 hardrives, but one is SATA and the other is an IDE one. I don't have a SCSI hardrive.

 

[paparazi]

Yes the bios just classes SCSI and Raid into one group, kind of either or, so it sounds like SATA Raid was disabled but defaulted back to enabled after the BSOD, something like that!
Cosair value CL3? we had a few problems last month with this brand on any Nforce4 platform we were building.
We ended up changing brand to stop the random BSOD and other anomolies that were occuring (Kingston value Cas2.5 works well).
Corsair has always been a safe bet so it could just have been one of those things.
500watt but what? I cannot understate the value of a quality PSU with such high end components.
Martin





We like members to GIVE and not just TAKE.
Participate and help others.

 

[BadBigBen]

Certain Burn Softwares install a pseudo SCSI device, ie. Alcohol and NERO... usually to support Virtual CD/DVD roms...

So from what I gathered you tried to install Daemon Tools and it went awry... am I correct?

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[ostrich69]

BadBigBen,


Yes, you're right, I was trying to install Daemon Tools, however I didn't know that there was any possible dangers from installing it.

Will uninstalling it fix the problem? Everytime I reboot now, the 'windows has found new hardware' message shows up. Also there is still the yellow exclamation mark in device manager.

 

[BadBigBen]

Well, it seems that you may have installed an older version of the Daemon Tools, which causes problems with some installs...

here is the FIX:

1.) Search in the Driver Folder for the following file and delete it: ST3Wolf.sys

2.) go to the Device Manager and Uninstall the ST3Wolf Scsi device...

3.) reboot...

4.) if you want to use DaemonTools then DL the latest version, it is safe to use...

http://www.daemon-tools.cc/dtcc/download.php?mode=ViewCategory&catid=5

just make sure that all other Virtual CD/DVD drivers are inactive...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[BadFrog]

Certain Burn Softwares install a pseudo SCSI device, ie. Alcohol and NERO... usually to support Virtual CD/DVD roms...

So from what I gathered you tried to install Daemon Tools and it went awry... am I correct?

Sir you deserve a star for that. Good catch!

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[ostrich69]

BadBigBen,

I tried what you suggested, however in Device Manager, in the "System devices" section there is a yellow exclamation mark under PNP Bios still.

What can I do about that?

 

[BadBigBen]

@Ostrich69 - Hope this helps, follow the quoted text below, before installing v 4.0x...

1. Open device manager (SCSI/RAID Controllers section) and delete SCSI controller with name corresponding with name of Daemon driver (miniport driver name). If you have problems doing it (eg. system crashes) then start from step 3 (skip steps 1 and 2).

2. Open device manager (System devices section) and delete device with driver corresponding with Daemon driver (bus driver name). In current versions of Daemon Tools it is 'PnP BIOS Extension' but most likely it may change in next versions. Again, if you have some problems doing it, skip this step

3. Find Daemon driver files in Windows\System32\Drivers folder
(in Win95/98/ME also check Windows\System\IOSUBSYS folder).
Make sure your system is configured to display system files (ControlPanel->Tools->FolderOptions->View) in order you can see them. Delete Daemon driver files.
default v3.46 driver file names are d346bus.sys and d346prt.sys
default v3.47 driver file names are d347bus.sys and d347prt.sys

4. In WinNT/2000/XP/2003 open registry editor and check
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es
for entries with same names as Daemon driver files (i.e. standard = d347bus and d347prt). Delete these keys.

5. Reboot your system. If you executed steps 1 and 2 then you don't need to do anything anymore. Otherwise proceed to next step.

6. Go to device manager - you may see some device with yellow mark.
This is most likely Daemon device which cannot start because it's drivers are deleted. Delete this device from Device Manager.

The same procedure may be used also for complete removal of Alcohol drivers from system.

Source: DaemonTools Forum...

@BadFrog - the driver name sounded familiar, as I experience d the same problem once before...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."