R710 / Win 2008 R2 out of coverage and EOL on OS. Getting a BSOD noting Bxois.sys. Even booting into Safe Mode BSOD. Any suggestions would be great as this Server is running a legacy application that we use for Automated Reporting. The Application is no longer available (to be loaded onto a newer/current Server), so we really need to get this working.
That link looks good. Try renaming the driver and not deleting it.
The BSOD referencing bxois.sys on your Dell PowerEdge R710 running Windows Server 2008 R2 is likely related to a driver or firmware conflict, particularly involving Broadcom network drivers
If you have a Windows Server 2008 R2 installation DVD or ISO, you can use it to access recovery tools.
Steps:
Boot from the Windows Server 2008 R2 DVD.
Choose Repair your computer.
Select the OS installation > Click Next.
Choose Command Prompt.
In Command Prompt:
Rename the problematic driver:
cd C:\Windows\System32\drivers ren bxois.sys bxois.old
Reboot the system.
This prevents the driver from loading and may allow Windows to boot.
DELL-Charles R
Social Media and Communities Professional Dell Technologies | Enterprise Support Services #IWork4Dell
Did I answer your query? Please click on ‘Accept as Solution’. ‘Thumbs up’ the posts you like!
Yes, I was able to rename the bxois.sys to bxois.sys.old via Command Prompt and the Server booted up properly. With pressing my luck, I went into Device Manager and noted a problem with the Drivers. Went to Dell site, entered in my Service Tag, downloaded the Broadcom drivers, pointed to the unzipped folder for the drivers, said :"Windows has determined the driver software for your device to upto date." However, still on conflict. Deleted both the attached drivers, and did a hareware scan, found the drivers, no conflicts. Everything in Device Manager looked proper so I Power cycled....BSOD for Bxois.sys again. So now back to no bxois.sys file and Server is up. But upon attempting to run my Reporting Software, the web gui is failing. So looks like the Storage Controllers driver is causing my application to not run properly (due to reference configuration not located on C:, rather another HD on this Server). This is kinda of assuming at this point, but prior to the BSOD, our automated reports have been working for many years.
Any additional thoughts on how to get these drivers active?
Currently the Server is/has been up with no Bxio.sys file. All my NIC's are proper (been RDP'd into it since yesterday), its only the Storage Controllers in question.
With that being said, continue with the above process to run suulauncher.exe?
I by default would agree...if its not broken, dont fix it. But my Application is not running as it was prior to the above BSOD. What is the actual purpose of the Storage Controllers noted above with conflicts? As I dont think so (since App working prior to BSOS), but wondering if im chasing my tail here.
mthompson239
1 Rookie
•
6 Posts
•
2 Points
0
0
Posted June 17th, 2025 14:43
I did note this link, but on the fence to delete a *.sys file.