Dell Studio 15 Driver Download
Good day Windows Community.
I am trying to upgrade my Dell Studio 1555 from W7 Pro 64-bit to W10.
Dell Studio 15 T6400
Before I did this, I was aware of a problematic device on my system board. It happens to be the Ricoh Multi-Card Reader. I never use it, but a few years ago the BIOS started to issue the following warnings during power up:
Phoenix BIOS Revision A13
Dell Studio 1555
Below table contains some hot Dell WiFi drivers Driver Talent can download, like Dell Inspiron N5110 WiFi drivers, Dell Latitude D610 wireless driver, Dell Vostro 3550 WiFi drivers, Dell Inspiron 15 3000 WiFi drivers, Dell E6430 WiFi driver, etc.
POST Warnings as follows:
Resource Conflict - PCI on Motherboard
Bus:09, Device:01, Function:00
Resource Conflict - PCI on Motherboard
Bus:09, Device:01, Function:01
Resource Conflict - PCI on Motherboard
Bus:09, Device:01, Function:02
Acer update decrypter executive branch. Resource Conflict - PCI on Motherboard
Bus:09, Device:01, Function:03
Resource Conflict - PCI on Motherboard
Bus:09, Device:01, Function:04
I elect to continue and Windows 7 boots quite happily. Device Manager indicates an issue with the card reader but the computer is perfectly stable in every other respect.
I am able to disable the device and delete the driver (rimspx64.sys) in W7.
I have attempted to re-seat the card reader and verified nothing visibly loose on the system board.
Unless I do remove the driver, the W10 installation aborts during the features and drivers phase and rolls the computer back to W7.
The W10 installation completes provided the driver is not in the system folders. It took me a while to figure this out.
After the W10 installation completes, the next normal boot gives me an IRQL_NOT_LESS_OR_EQUAL BSOD and indicates a problem with rimspx64.sys. The installation must have installed the driver and I assume that the resource conflict error, benign in W7, is a fatal in W10.
W10 produces a memory dump (which I have) and then manages to boot up, albeit extremely slowly. It doesn’t “learn” from whatever it does to boot successfully second time round. In other words, it doesn’t seem able to persist the workaround it’s managed to execute to achieve a healthy boot. If it could do that, I’d be very happy!
Note, if I check the PCI Lock Advanced Boot option, W10 never boots and I have to recover via System Restore. This, I feel, is a strong clue to a potential fix?
The W10 Device Manager reports the problems, but if I attempt to disable or uninstall the driver, I get a runtime SYSTEM_THREAD_EXCEPTION_NOT_HANDLED BSOD with rimspx64.sys again appearing in the on-screen diagnostic.
Provided I don’t attempt any kind of configuration of the problematic driver, W10 appears to perform perfectly in all other respects. By “perfectly”, I mean “as designed” – there are a number of features that to my mind seem retrograde after many years on W7. However, if I perform a normal boot cycle I get the IRQL BSOD and a very slow boot. Interestingly, a Restart doesn’t exhibit the problem.
I have reverted the computer back to W7 but hope I can find solutions to enable a very robust W10 upgrade and all-round experience.
All advice greatly appreciated. I am relatively tech-savvy so please go into as much technical detail as necessary. I have both memory dumps preserved for troubleshooting as required.
Many Thanks in advance.
Stuart