spl3001

I will try to do a scan, but as I said, the system is not connected to the Internet. Not sure Malwarebytes will work with out it (the install is 2.8 MB, which says to me "no data, just online installer")

Hi everyone, Trying to fix a computer at work with the following issues: Dell Optiplex 9020 Desktop tower. Computer boots to Windows 10 Login. Mouse moves to random points on screen, as in does not travel to them, just random locations. If logged in as the normal user, it continues this behavior as well as randomly right clicking and left clicking (which occurs in log in, just not as apparent). Forcing system to boot in Safe Mode with Networking (or just plain Safe Mode), this behavior is no longer present. System is not connected to the network or internet in any way and hasn't been for at least several months. Behavior started yesterday, operator indicated it happened while he was sitting there running software. There is not a track pad installed and this behavior continues whether a mouse is plugged in or not. My best guess is malware, and ITs solution here is to reimage, but I'm not IT and this computer isn't entirely under their purview as its a lab machine with special software on it that isn't apart of the standard image (i.e. it needs to be fixed, not reimaged). Any ideas?

I'm afraid the vendor most likely has all the software cards up its sleeve. The hope was it could be repaired without resorting to a $1350 300 GB hard drive and a $1350 Dell UCS-61 RAID controller card (actual quoted prices from the CT vendor, labor NOT included [another $3,000]). In any other sane situation, I'd whole sale replace the system with modern computer hardare, failing that, rebuilding the system on a new drive/controller (combined price of ~$70). Kinda got my hands tied. And this was just a last ditch effort to avoid those costs, so we may have to go that route anyway. My extremely optimistic hope would be to get the system to some kind of working order and then make a dozen clones of the working drive.

This story begins Monday morning. I'm informed that there is a problem with one of our CT computers and it has a BSOD. I had just sat down for the day, and I got the feeling this was going to foreshadow the rest of the week. Patient's vitals: Windows XP (unsure of service pack version) Dell Precision T5500 (6 core Intel Xeon) 12 GB DDR3 ECC RAM (don't have spares I can test at the moment) 300 GB Fujitsu SAS Hard Drive connected to a... Dell USC-61 (made by LSI) RAID controller card Two DVD writer drives Patient's initial symptoms included: STOP: 0x0000008E (0xC0000005,0xE0D02E33,0xF26889B8,0x00000000) With a memory dump that I thought I'd be able to get to in short order, but that would not be the case. A Google search indicated that this stop code is related to PAGE_FAULT_IN_NON_PAGED_AREA. Or some general posts I found talked about the memory modules having gone bad. I took photo evidence of the error and rebooted. Windows XP booted up to the login screen. I attempt to log in with the correct credentials. The computer thought about this for a minute and decided it was not interested in logging in today: CONFIG_INITIALIZATION_FAILED STOP: 0x00000067 (0x00000001,0x0000000F,0xC000009A,0x00000000) Ok, new error. This seemed to be pointing to either more memory trouble OR some issue with the registry being corrupted (or both, who knows). Let's try safe mode first: Windows could not start because the following file is missing or corrupt: system32\DRIVERS\isapnp.syk You can attempted to repair this file by starting Windows Setup using the original Setup CD-ROM. Select 'r' at the first screen to start repair That is NOT a type. It said isapnp.syk and NOT isapnp.sys. I tried googling for that exact phrase but could not find ANYTHING closely relevant. This is where things started to get...complicated. So I thankfully found an ISO for Windows XP SP2 that I had laying around from a decade or so ago. I used the Rufus utility to make a bootable USB flash drive and walked back to the computer and used Dells F12 menu to select USB Device as the boot option. To my surprise (but later I learned at least why this happened), I got another kind of BSOD: STOP: 0x0000007B (etc.) If I remember correctly, this had to do with boot media not being present. This is really a side note because it had to do with the BIOS being in RAID (and NEEDING to be in RAID because of the system drive being on a RAID controller), and not something like compatibility/IDE mode (this also seems to happen when AHCI is selected on older systems). With that brushed aside mentally, I started to hunt for a burnable CD, thinking I might be out of luck because CDs are soooooo 2000s! Deep in an office cabinet I found an unmistakeable 100 DVD-R (and turns out a mix of CD-Rs) plastic cylinder. I whisk away the whole thing and make a Windows XP SP2 CD for the first time in more than 10 years. Disc in drive. Boot up. Press any key. Press F6 for third party drivers prompt. Don't need em. Wait. Wait. Wait. No drive found. Uh oh...I need third party drivers. Google for the Dell UCS-6 Windows XP drivers for nearly an hour because who would have THAT any more? I actually found them but learned a terrible bit of information in the process. Windows XP Setup will ONLY load third party drivers with the F6 prompt from the A: drive. This computer: 1.) Doesn't have a floppy drive 2.) Who on the entire planet has a floppy? Because our entire lab operates on a shoestring budget and equipment from 1995, a coworker not only had a USB floppy drive, but a perfectly functional 3.25" floppy I could borrow because he still transfers files from a lab machine to his computer with it. I didn't have much hope, but cutting to the chase, I booted ALL the way into the Recovery Console. chkdsk found errors and repaired (why doesn't it give more detail than that?). I ran it again. No errors the second time. Wish I could could have done a system file checker command (can't remember what the command is at the moment), but that's not apart of Windows XP Recovery Console. I closed the system and ran MemTest86+ for 18 hours overnight. All tests passed. I eventually find out that problems have cropped up before when "the drive fills up". It has two partitions, a 20 GB for C:\, and approximately 260 GB for what appears to be a weird RAID setup (Linux showed an LBA over a NTFS partition?). I booted into Ubuntu from a USB (with no issue) to examine the layout, but I didn't take a picture. I moved some files onto a USB hard drive, but couldn't clear out too much space on C (it currently has 12 GB free) as most of the folders are special/weird and I don't want to screw this up more than it already is. Could the page file not have room to be created/used any more? I learned about Hiren Boot CD near the end of the day today and tried the latest version, but realized it is a Windows 10/PE environment and may not be suitable for repairing Windows XP. I started downloading version 15.2 from their archive which appears to be around circa 2012 and may work based on a forum post I found using it to fix a similar issue to the one this computer has. It has some registry back up recovery abilities apparently. I did try a system restore early in the process but that gave me either one of the above BSODs or the isapnp.syk error (I can't keep track any more). I did copy isapnp.sys to the drivers folder (keeping the old one), but it had no affect. Sorry to drag this out, but I wanted to detail all the attempts made so far and to provide a relatively complete picture of problem. Is there anything I should try next? Hiren "Registry Repair Wizard"? Some other utility to try to restore the registry? Manually restore it? Are there even backups of the registry on Windows XP? I've considered imaging the disk with an offline utility and seeing if it can boot from that, but I'm going to wait until tomorrow. Any help or suggestions are greatly appreciated.

Ok, I'm about a third through the image/driver removal process. DISM and Windows PE is all new to me, but I'm making my way through semi-successfully. I've made an image of the system partition and mounted it to a directory on another partition for servicing. I did a: dism /Image:D:\mount /Get-Drivers to see what to remove, but the list is longer than can be displayed and scrolled through (must be a line limit in the Windows PE command environment, not sure how to change). From what I can see, there are a LOT of third party drivers for various things and a LOT of EDAX related drivers. Are there any filtering/wildcard commands to get a list of the non-EDAX drivers (like: *ed?x*) And if so, can I compile this list as input into the: dism /Image:d:\mount /Remove-Driver /Driver:etc.inf /Driver:etc2.inf (and so forth) command I will need to call next to strip them out? Because there are probably several dozen drivers that could be stripped out. By the way, I'm using this site for my DISM guide (and the various pages linked from there for other DISM steps and procedures): https://technet.microsoft.com/en-us/windows/dn898469(v=vs.60) And I know this is a "long, long, long" shot, but any guidance to get this to a testing point is appreciated.

I don't have the "No Fixed Disk" issue any more. I've got an "INACCESSIBLE_BOOT_MEDIA" mixed with a "CorruptRegister" issue with the drive. I am going to attempt TheDelphiDude's plan of attack and see where that gets me.

If the registry is really corrupt, won't I just be cloning a system with a corrupt registry? I'm willing to go through the process, I'm just not sure what the likelihood of success will be. I do see if there is a driver issue causing all the problems how it might be circumvented though. Is there any relationship between the BSOD "INACCESSIBLE_BOOT_MEDIA" and the Automatic Repair complaining about a corrupt registry?

Ok, so some updates: After resetting the BIOS password via jumper, I changed the drive controller from RAID+AHCP to just AHCP. This allowed all the Windows 7 boot media to then recognize the drives and the Windows install on the boot drive. After repeating the bootrec commands, I had no success. I allowed the system to boot normally, as far as it could and noticed a flash of a BSOD. I recorded via video and got a 0x0000007b error: INACCESSIBLE_BOOT_MEDIA. I tried Startup Repair again, and this time Window says: Startup Repair cannot repair this computer automatically Under details: AutoFailover and CorruptRegistry are some of the ProblemSignatures that seem important. I'm pretty sure there isn't a backup of the registry or a System Restore point, so at this point I think I am up the creek without a paddle. Is there anything left to do besides a clean install?

There appears to be no firmware updates available, and suggests to look for "CERTIFICATE" Firmware Update below the firmware section, and there doesn't appear to be any of that either. I've done a chkdsk with no errors. I've moved the drives to different SATA ports and have swapped in different SATA cables. I really need to be able to run a Windows 7 Boot USB and see those drives as I can at least attempt a Startup repair, but only the Windows 10 Boot USB can see the drives. Unfortunately, from what the Windows 10 USB boot drive can surmise, there doesn't appear to be any System Restore Points. I've encountered this before and am astonished that automatic/regular system restore points weren't DEFAULT in Windows 7 (are they even default in Windows 10?). Are there some kind of drivers I can use with the Windows 7 boot USB to force these drives to be detected? Motherboard/disk controller drivers? I didn't find any for the FBM-1101 that would work (mentioned in original post). And Seagate doesn't appear to have any for the two serial numbers I checked with that utility above that seagate_surfer mentioned.

Trying to diagnose problem with the following system: HP Z420 Workstation (Motherboard model: FMB-1101) System has two 1 TB Seagate SATA hard drives plugged into the motherboard. Windows 7, vers 7600 as far as I can tell. One is a boot drive and the other is a data drive. System was booting correctly approximately one week ago. Hard drives are detected during post. BIOS is password protected so I cannot get further details. One drive appears to have a recovery partition as the system goes into recovery mode after failing to boot. However, recovery mode does not detect the Windows installation and a diskpart command in the command line reveals NO FIXED DISK. I've tried both a Windows 7 7600, and what I believe was Windows 7 SP 1 USB boot drive. Diskpart in these two only shows the USB boot drive in the list. However, when I use diskpart on the latest Windows 10 Boot Media USB (made today), it shows all disks (the two 1 TB disks and the USB drive). Partitions and volumes all look healthy, and the C: drive is present and labeled as "System". The contents all appear there as well. I tried to do a bootrec /fixboot but get an "Access is denied" message. I only performed this after apparently successfully performing a bootrec /rebuildbcd and bootrec /fixmbr. Note: I did have to do the old rename and change attribute trick to the existing bootbcd folder. I downloaded the storage drivers from HPs website and put them on a separate USB drive and attempted to load them during the Windows 7 repair process, but none of the "Setup Information" files are valid hardware drivers according to the Windows 7 "Load drivers" dialog. Is there another way to get the storage drivers loaded? I'm not sure if that's even the issue. Needless to say, I'm stuck. This is not a system I am familiar with and was only brought in yesterday to take a look. It is an equipment manufacturer computer designed to interface with an SEM EDAX, and we decided to forego the maintenance contract this year... Any help is appreciated.