Skip to main content
gamedev.net
🔒 Locked

Kernel Fault Error?

Started by PumpkinPieman Jun 12, 2006 at 7:17 AM 4 replies 1.3k views
Original Post
PumpkinPieman
PumpkinPieman
I've been checking google but nothing seems to aid to the resolution of my problem. This morning I was going through a data backup CD and came across Daemon Tools, I had recently got a new computer so a fresh copy of windows was just installed. So I started the installation and at the end of it my machine decides to restart, I reboot and ad-aware monitor picks up a registry from windows for a "kernel fault error". It bothers me a bit, then tells me it's loading the SCSI interface which is what Daemon Tools usually does. Finishes then restarts, now it's in a constant loop. I start the computer it loads faulty whatever, then it restarts. I checked on google for this and they say it's linked to failed devices like memory, but my Raid0 checks out on post and a diagnostic was already run on the memory 5 days ago. I started Safe Mode with Networking, and it did the same thing. I'm going to have to take a second look at this and see if there is an option to load specifc hardware. Any idea's what would cause and fix this? System Specs: AMD X2 64 4200+ OCZ Plat 2GB Dual Channel Asus A8N32-SLI Deluxe 2x 320GB SATA Seagate 7200.10 in Raid 0 Asus Geforce 7600GT
Ravuya
Ravuya
Well, your botched install must have gotten wedged and installed a corrupt SCSI driver, which is taking your machine down. The Windows install CD may be able to fix the installation.

On Windows, I think CD burning, CD emulation and SATA are handled through the SCSI driver layer, so that is probably part of your problem.
PumpkinPieman
PumpkinPieman
Thanks for the reply.

That's probably it, but ..
Alright, it installed then restarted. Then when it booted back up it started installing the SCSI interface, but I selected windows update as a source for the driver so it shouldn't be faulty should it?
Ravuya
Ravuya
The driver may not have "fully" installed. I've never had Ad-Aware come up and bitch about the kernel before.
kanzler
kanzler
This page has a link to the installation of the driver portion, SPTDinst X86/X64. I'd suggest first removing the driver with this package, followed by an installation. Hopefully this will solve your problem.
PumpkinPieman
PumpkinPieman
Quote:
Original post by Ravuya
The driver may not have "fully" installed. I've never had Ad-Aware come up and bitch about the kernel before.


Well it didn't complain about the kernel per say, I have ad aware monitor so it tracks registry modifications and catches malware earily. Windows had made a registry change it didn't like, I get the popup from multiple programs as well.

I'll try that program when I get home, if it doesn't work I guess I have no choice but to reinstall windows.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.