Educad
asked on
BSOD Windows Server 2008 R2 0x0000007a
Hi,
We have one backup server which has been rebooted due to BSOD a few times since last year.
This is output of mini dump file:
Is this something to do with cabling?
How can I resolve this issue? I am not sure what exact causes of the error.
We have one backup server which has been rebooted due to BSOD a few times since last year.
D= 1001; Src= BugCheck; User= ; Catg= ; D/T= 10/06/2014 11:56:12; EventDesc= The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0xfffff6fc4002a838, 0xffffffffc0000185, 0x000000005f471be0
This is output of mini dump file:
MODULE_NAME: nt
FAULTING_MODULE: fffff80001649000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c0000185
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001731752 to fffff800016bebc0
Is this something to do with cabling?
0xC0000185 SCSI devices with improper termination, bad cabling, or devices are not configured properly causing two devices to use the same IRQ (Interrupt Request).
How can I resolve this issue? I am not sure what exact causes of the error.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you find it in windoows \minidumps
and no you did NOT post it, only a short txt file, which maybe -or not- correct
and no you did NOT post it, only a short txt file, which maybe -or not- correct
ASKER