Windows 7 Forums Search
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows 7. The Windows 7 forum also covers news and updates and has an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7 - Ext HDD on eSATA freeze: \Device\Scsi\JRAID detected a port timeout

 
06-28-2011   #1


Windows 7 Professional 64bit
 
 

Ext HDD on eSATA freeze: \Device\Scsi\JRAID1 detected a port timeout

I had this problem described in another thread, but I figured it deserved its own thread.

Ever since I reformatted and installed Windows 7 I've been having problems with my eSATA external HDD randomly shutting off from the PC. Not sure if related or not, but Windows 7 had placed boot files into it and made it Active, which wouldn't let me boot and forced me to do a reinstall without the HDD connected.

After the new install I deleted those files and the Active flag, but the problems persisted, so I did a complete clean all with WD Diagnostics tool with a full Write-Zeros via USB, which gave a "Failed to update disk property!" message at the end, but still said it had completed successfully.

HDD SMART info (anything wrong?)

I did a full chkdsk and no errors were detected either...

The Jmicron WHQL R1.17.47 Windows 7 drivers had always worked without problems in the past 2 years with Vista. I also tried drivers and R1.17.49 and R1.17.63. Found here.

The problem I'm having is that after successfully booting and using the external HDD via eSATA after some time it'll disconnect itself or stop answering, freezing Windows Explorer and spamming JRAID error events in the Event Log:

\Device\Scsi\JRAID1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition.

Code:
+System
-Provider[ Name] JRAID
-EventID117[ Qualifiers] 49156
Level2Task0Keywords0x80000000000000-
TimeCreated[ SystemTime] 2011-06-29T04:26:19.920Z
EventRecordID45377
ChannelSystem
ComputerStudy-PC
Security-EventData
\Device\Scsi\JRAID1000000000100000000000000750004C0000100000000000000000000000000000000000000000000
Binary data:
Words
0000: 00000000 00000001 00000000 C0040075 
0008: 00000100 00000000 00000000 00000000 
0010: 00000000 00000000 
 
Bytes
0000: 00 00 00 00 01 00 00 00 ........
0008: 00 00 00 00 75 00 04 C0 ....u..À
0010: 00 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
I even went back to Vista to see if it was some compatibility problem with Windows 7, but it's still happening after all...

After the freeze/disconnect has happened if I try to shut down or reboot it'll stay there stuck at "Shutting down...". If I wait 10-15 minutes a BSOD appears with DRIVER_POWER_STATE_FAILURE. Minidump:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
 subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80060ddbb0, The thread currently holding on to the Pnp lock.
Arg4: 0000000000000000
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  4
FAULTING_THREAD:  fffffa80060ddbb0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LOCK_ADDRESS:  fffff80002a58c40 -- (!locks fffff80002a58c40)
Resource @ nt!PiEngineLock (0xfffff80002a58c40)    Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
 
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE: 
 Lock address  : 0xfffff80002a58c40
 Thread Count  : 0
 Thread address: 0x0000000000000000
 Thread wait   : 0x0
LAST_CONTROL_TRANSFER:  from fffff800028ba6fa to fffff800028bac7f
STACK_TEXT:  
fffffa60`023af710 fffff800`028ba6fa : fffff800`02a58a20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7f
fffffa60`023af850 fffff800`028af38b : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`35706e50 : nt!KiSwapThread+0x13a
fffffa60`023af8c0 fffff800`02945100 : fffffa80`00000000 fffff800`00000000 fffffa80`0714d700 fffffa80`0714d700 : nt!KeWaitForSingleObject+0x2cb
fffffa60`023af950 fffff800`02bdd3a5 : fffffa60`023afa14 00000000`00000001 00000000`00000000 fffff800`02a56500 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x20
fffffa60`023af990 fffff800`02c93c3e : fffffa80`0714d730 fffffa80`0714d730 00000000`00000001 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x65
fffffa60`023af9c0 fffff800`02c9408a : 00000000`00000000 fffff800`028bdb94 00000000`00000000 fffff800`02ab2ee9 : nt!PipProcessDevNodeTree+0x36e
fffffa60`023afc30 fffff800`0298be5d : fffff801`00000003 fffffa80`086135e0 00000000`00000000 fffffa60`0508f790 : nt!PiProcessReenumeration+0x8a
fffffa60`023afc80 fffff800`028bf8c3 : fffff800`0298bc30 fffffa80`060ddb01 fffff800`029ef8f8 00000000`00000000 : nt!PnpDeviceActionWorker+0x22d
fffffa60`023afcf0 fffff800`02ac2f77 : fffff800`02a565c0 00000000`00000000 fffffa80`060ddbb0 00000000`00000080 : nt!ExpWorkerThread+0xfb
fffffa60`023afd50 fffff800`028f5636 : fffffa60`02199180 fffffa80`060ddbb0 fffffa60`021a2d40 fffffa80`060dd138 : nt!PspSystemThreadStartup+0x57
fffffa60`023afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
STACK_COMMAND:  .thread 0xfffffa80060ddbb0 ; kb
FOLLOWUP_IP: 
nt!KiSwapContext+7f
fffff800`028bac7f 488d8c2400010000 lea     rcx,[rsp+100h]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KiSwapContext+7f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4cb7275f
FAILURE_BUCKET_ID:  X64_0x9F_nt!KiSwapContext+7f
BUCKET_ID:  X64_0x9F_nt!KiSwapContext+7f
Followup: MachineOwner
---------
Could this be a problem with the HDD itself or my motherboard somehow? My motherboard's BIOS is the latest (BIOS 82 for EVGA X58 SLI) Any way to tell without having to buy new HDD/mobo?

Thanks


Last edited by Kusuri; 06-29-2011 at 02:53 PM..
My System SpecsSystem Spec
Reply

 Ext HDD on eSATA freeze: \Device\Scsi\JRAID detected a port timeout problems?



Thread Tools



Similar Threads for: Ext HDD on eSATA freeze: \Device\Scsi\JRAID detected a port timeout
Thread Forum
Can I connect a SATA drive to an ESATA port? Hardware & Devices
BSOD SCSI Port.sys file error? Crashes and Debugging
External eSata drive stopped being detected Hardware & Devices
ESATA hard drive not detected Hardware & Devices
Here are my computer specs. Why is my eSATA port slow Drivers


All times are GMT -5. The time now is 10:05 AM.



Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30