[Solved] Win 7 x64 - JRAID Error (117) - PnkbstrB.exe hearbeat stopped
Posted: 2010-09-13 00:06
Introduction
Specs:
OS: Win 7 Home Premium x64 EN
Mobo: Gigabyte GA-X58A-UD3R ("GX58AUDR3_FB")
SSD: Kingston SNVP325S264GB (SATA II)
HDD: ST32000641AS (SATA III)
SSD and HDD are both connected to the two SATA III Ports.
Original Mobo Firmware: "GX58AUDR3_FA"
Current Mobo Firmware: "GX58AUDR3_FB"
"Event Viewer" ("Windows Logs/System") reports:
"The driver for device DeviceScsiJRAID1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition."
Error code: 117
The Course:
Short Version:
- Windows Installation
- BIOS update to "FB" (AHCI settings set to "ON")
- PnkbstrB.exe kicks, JRAID error occurrences
- Reinstall attempt of Windows
- SATA Cable Swapping
- successfull Reinstall of Windows (no more JRAID errors, PB-B kicks)
Long Version:
After solving my RAM issue described in this post: https://www.realitymod.com/forum/f358-s ... t-6gb.html
I had been getting Punkbuster's infamous "Pnkbstrb.exe: Heartbeats stopped" kicks on every PB secured BF2 and PR server that I have tried, every time. While I was unable to fix the PB-B kicks I went through a lot of testing to see what might help and noticed a ca. 5 second freeze everytime after the loading of the map finished. At first I related this freeze to be caused by the Punkbuster kick as a common prekick symptom. However when running BF2 in windowed mode I started "Event Viewer" and investigated the events that relate to the punkbuster kick. I soon figured that right after the afore mentioned 5 sec. freeze the "JRAID" error appeared. Googling brought to light that the freez was actually a common Symptom for the "JRAID" error.
At this point I would like to mention that I had been fiddling around with the BIOS in regards of changing around the SATA Controlers' settings from "IDE" to "AHCI".
So far I have not been able to determine whether the JRAID error was caused by the BIOS update or the conversion to "AHCI".
I reinstalled Windows, hoping it was a driver issue that was so grave that it was not detected by currently/previously installed Windows. When trying to install from within the booted Windows (autorun of Windows install disk) the Dialog to chose the installation's target partion came up. As usually I (since it was just a fresh install I did not worry about wiping the system disk (SSD)), I erased both the 100 MB "System Reserved" and the "C:" partition to have Windows recreate those and make sure the previous installation is not going to confilict with the one I am attempting.
Unexpectedly Windows declined to install on any of the partitions with the error: "Windows is unable to install to the selected location. Error: 0x80300001"
Googling showed that this is due to windows being unable to create the 100MB "System Reserved" partition on "disk(0)".
I was surprised to see that my SSD (formerly C: ) was actually designated "disk(1)" whilst it had been "disk(0)" during the initial installation of Windows. Accordingly my HDD (formerly disk(1)) was now designated "disk(0)".
I blamed this on my attempt to install from within a booted Windows. I went to boot from the installation DVD and stumble upon the same problem.
Solution
Swapping both SATA cables actually did the trick. Windows recognized the SSD as "disk(0)" again and the HDD as "disk(1)". Installation of Windows could therefore successfully proceed, a 100mb "System Reserved" partition was created on the SSD as well as drive "C:" is on the SSD as well.
Remarks
I am not sure if Swapping the cables alone would have already fixed the JRAID error, however I am relieved to say that the Reinstallation of Windows and the swap of the SATA cables solved the JRAID error (and the freeze after map load) so far.
It also fixed my PB-B kick problem for now but if it remains this way is uncertain.
Edit: It remained this way
. I also already upgraded to BIOS firmware verison "FE".
Specs:
OS: Win 7 Home Premium x64 EN
Mobo: Gigabyte GA-X58A-UD3R ("GX58AUDR3_FB")
SSD: Kingston SNVP325S264GB (SATA II)
HDD: ST32000641AS (SATA III)
SSD and HDD are both connected to the two SATA III Ports.
Original Mobo Firmware: "GX58AUDR3_FA"
Current Mobo Firmware: "GX58AUDR3_FB"
"Event Viewer" ("Windows Logs/System") reports:
"The driver for device DeviceScsiJRAID1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition."
Error code: 117
The Course:
Short Version:
- Windows Installation
- BIOS update to "FB" (AHCI settings set to "ON")
- PnkbstrB.exe kicks, JRAID error occurrences
- Reinstall attempt of Windows
- SATA Cable Swapping
- successfull Reinstall of Windows (no more JRAID errors, PB-B kicks)
Long Version:
After solving my RAM issue described in this post: https://www.realitymod.com/forum/f358-s ... t-6gb.html
I had been getting Punkbuster's infamous "Pnkbstrb.exe: Heartbeats stopped" kicks on every PB secured BF2 and PR server that I have tried, every time. While I was unable to fix the PB-B kicks I went through a lot of testing to see what might help and noticed a ca. 5 second freeze everytime after the loading of the map finished. At first I related this freeze to be caused by the Punkbuster kick as a common prekick symptom. However when running BF2 in windowed mode I started "Event Viewer" and investigated the events that relate to the punkbuster kick. I soon figured that right after the afore mentioned 5 sec. freeze the "JRAID" error appeared. Googling brought to light that the freez was actually a common Symptom for the "JRAID" error.
At this point I would like to mention that I had been fiddling around with the BIOS in regards of changing around the SATA Controlers' settings from "IDE" to "AHCI".
So far I have not been able to determine whether the JRAID error was caused by the BIOS update or the conversion to "AHCI".
I reinstalled Windows, hoping it was a driver issue that was so grave that it was not detected by currently/previously installed Windows. When trying to install from within the booted Windows (autorun of Windows install disk) the Dialog to chose the installation's target partion came up. As usually I (since it was just a fresh install I did not worry about wiping the system disk (SSD)), I erased both the 100 MB "System Reserved" and the "C:" partition to have Windows recreate those and make sure the previous installation is not going to confilict with the one I am attempting.
Unexpectedly Windows declined to install on any of the partitions with the error: "Windows is unable to install to the selected location. Error: 0x80300001"
Googling showed that this is due to windows being unable to create the 100MB "System Reserved" partition on "disk(0)".
I was surprised to see that my SSD (formerly C: ) was actually designated "disk(1)" whilst it had been "disk(0)" during the initial installation of Windows. Accordingly my HDD (formerly disk(1)) was now designated "disk(0)".
I blamed this on my attempt to install from within a booted Windows. I went to boot from the installation DVD and stumble upon the same problem.
Solution
Swapping both SATA cables actually did the trick. Windows recognized the SSD as "disk(0)" again and the HDD as "disk(1)". Installation of Windows could therefore successfully proceed, a 100mb "System Reserved" partition was created on the SSD as well as drive "C:" is on the SSD as well.
Remarks
I am not sure if Swapping the cables alone would have already fixed the JRAID error, however I am relieved to say that the Reinstallation of Windows and the swap of the SATA cables solved the JRAID error (and the freeze after map load) so far.
It also fixed my PB-B kick problem for now but if it remains this way is uncertain.
Edit: It remained this way
. I also already upgraded to BIOS firmware verison "FE".