SuperMechaCow
I have a Hercules RMX and Vista Home Premium, and the two are giving me trouble.
The first time I ever tried to install the drivers for the RMX from the provided disc I got a registry corruption. I tried a second time by downloading the drivers from the Hercules website and it worked flawlessly. I recently changed hard drives, and when I went to reinstall the drivers for the RMX again and rebooted I got an error (similar to this) during startup.
"windows\system32\<some folder>\system\wdf0001.sys
Error: 0cx0000098
Windows cannot boot because the registry file is corrupt or missing"
Like I said, that's not EXACTLY what it said, but I prefer not to spend an hour repeating the process for the exact details.
This has happened more times than I can count. I honestly do not know what to do at this point. It has worked a SINGLE time, and I don't know what is making it not work or what made it work before. If I wanted to buy a $300 brick, I would have bought a lump of silver. It has better resale value.
The first time I ever tried to install the drivers for the RMX from the provided disc I got a registry corruption. I tried a second time by downloading the drivers from the Hercules website and it worked flawlessly. I recently changed hard drives, and when I went to reinstall the drivers for the RMX again and rebooted I got an error (similar to this) during startup.
"windows\system32\<some folder>\system\wdf0001.sys
Error: 0cx0000098
Windows cannot boot because the registry file is corrupt or missing"
Like I said, that's not EXACTLY what it said, but I prefer not to spend an hour repeating the process for the exact details.
This has happened more times than I can count. I honestly do not know what to do at this point. It has worked a SINGLE time, and I don't know what is making it not work or what made it work before. If I wanted to buy a $300 brick, I would have bought a lump of silver. It has better resale value.
Inviato Tue 17 Jan 12 @ 9:11 pm
DJ Phatso
This problem occurs when Windows is unable to update the Kernel Mode Driver Framework (the wdf0001.sys file in question).
I've sent you a private message so we can figure that one out.
I've sent you a private message so we can figure that one out.
Inviato Wed 18 Jan 12 @ 6:52 am
SuperMechaCow
For the sake of other people that may be able to help:
Phatso said:
"Here is how you can solve this problem:
1) Start cmd.exe as *Administrator*,
- Right-click on your desktop and select NEW > Shortcut
- In the window that appears, type CMD, then next then Finish.
- Right-click the new shortcut created on your desktop and select Run as administrator
2) Enter the following lines:
takeown /f C:\Windows\System32\drivers\Wdf01000.sys
takeown /f C:\Windows\System32\drivers\WdfLdr.sys
icacls C:\Windows\System32\drivers\Wdf01000.sys /grant <yourusername>:f
icacls C:\Windows\System32\drivers\WdfLdr.sys /grant <yourusername>:f
3) Overwrite the files in C:\Windows\System32\drivers\ with the new ones provided here:
http://www.mediafire.com/?ym4vpvgdjbfm60w
4) Reboot the computer.
5) Connect the console to the computer. It should allow you to install it.
Let me know if you have any problems"
I replied:
"All I got on reboot was
"File: Windows\system32\config\system
Error 0xc00000e9"
Missing or corrupt blah blah.
I hadn't even tried the installation yet.
I usually get that error after trying to do a system restore after the wdf01000.sys error, but this time it just skipped right to it.
Maybe something in my windows installer is just corrupt?
And why do I need to replace those files?"
"
Phatso said:
"Here is how you can solve this problem:
1) Start cmd.exe as *Administrator*,
- Right-click on your desktop and select NEW > Shortcut
- In the window that appears, type CMD, then next then Finish.
- Right-click the new shortcut created on your desktop and select Run as administrator
2) Enter the following lines:
takeown /f C:\Windows\System32\drivers\Wdf01000.sys
takeown /f C:\Windows\System32\drivers\WdfLdr.sys
icacls C:\Windows\System32\drivers\Wdf01000.sys /grant <yourusername>:f
icacls C:\Windows\System32\drivers\WdfLdr.sys /grant <yourusername>:f
3) Overwrite the files in C:\Windows\System32\drivers\ with the new ones provided here:
http://www.mediafire.com/?ym4vpvgdjbfm60w
4) Reboot the computer.
5) Connect the console to the computer. It should allow you to install it.
Let me know if you have any problems"
I replied:
"All I got on reboot was
"File: Windows\system32\config\system
Error 0xc00000e9"
Missing or corrupt blah blah.
I hadn't even tried the installation yet.
I usually get that error after trying to do a system restore after the wdf01000.sys error, but this time it just skipped right to it.
Maybe something in my windows installer is just corrupt?
And why do I need to replace those files?"
"
Inviato Thu 19 Jan 12 @ 9:23 am
evantanski
This problem occur because the previous driver were installed using another console model, and you are now trying to install the new driver using another console.
_______________
[Link removed]
_______________
[Link removed]
Inviato Fri 20 Jan 12 @ 1:12 am
Moderation staff
@evantanski: Despite being previously warned, you have yet again posted a prohibited 3rd party download link to a tool commonly used to download music illegally, which is against the forum rules.
Your account has now been locked.
Your account has now been locked.
Inviato Fri 20 Jan 12 @ 8:00 am
SuperMechaCow
Oh snap, son.
Well, I know your account is locked and so you can't really respond, but no. That is not what is happening. On a fresh install of Windows Vista I use the installer package from the Hercules website, and wait until it prompts me to plug in the device so that it only installs for the RMX.
How the hell is it I can modify this post but not previous ones.
Well, I know your account is locked and so you can't really respond, but no. That is not what is happening. On a fresh install of Windows Vista I use the installer package from the Hercules website, and wait until it prompts me to plug in the device so that it only installs for the RMX.
How the hell is it I can modify this post but not previous ones.
Inviato Fri 20 Jan 12 @ 12:53 pm
kradcliffe
You can only modify a thread for a certain time to correct typing etc. then it becomes permanent.
Regards
Keith
Regards
Keith
Inviato Fri 20 Jan 12 @ 2:50 pm
Support staff
Users are allowed to edit their posts for a short period of time after posting, but after that the message is permanent and cannot be changed.
Inviato Fri 20 Jan 12 @ 3:01 pm
SuperMechaCow
I don't really know if it was Phatso's solution, my solution or both, but it's working now.
What I did was I Installed all of the drivers with the device unplugged. When the installer asked me to plug in all Hercules consoles, I plugged in the RMX but DID NOT HIT NEXT. I waited for Windows to install the drivers completely before hitting next. Windows told me to reboot before the installer had completed and I said no. Once it completed it asked me to reboot again and I said no. I went to the device manager and double-checked that the device status said "Requires restart". I found that if it said, "corrupt or missing" I was going to have problems no matter what.
Also, it seems that I may have a corrupt bios, and I am "STRINGENTLY" locked out of it. I can't flash it by conventional means. This is also causing registry errors when I do a Windows Update. I THINK the two might have been related.
What I did was I Installed all of the drivers with the device unplugged. When the installer asked me to plug in all Hercules consoles, I plugged in the RMX but DID NOT HIT NEXT. I waited for Windows to install the drivers completely before hitting next. Windows told me to reboot before the installer had completed and I said no. Once it completed it asked me to reboot again and I said no. I went to the device manager and double-checked that the device status said "Requires restart". I found that if it said, "corrupt or missing" I was going to have problems no matter what.
Also, it seems that I may have a corrupt bios, and I am "STRINGENTLY" locked out of it. I can't flash it by conventional means. This is also causing registry errors when I do a Windows Update. I THINK the two might have been related.
Inviato Sun 22 Jan 12 @ 9:22 pm