We have various bug checks from the attached DMP files:
CRITICAL_STRUCTURE_CORRUPTION (109)
This indicates that the kernel has detected critical kernel code or data corruption.
There are generally two causes for this bug check:
- A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
- A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
KERNEL_DATA_INPAGE_ERROR (7a)
This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
ERROR_CODE: (NTSTATUS)
0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR:
There was error with disk hardware
0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ. This can also imply a faulty hard disk. We'll run hard disk diagnostic soon, but there's something else I'd like to tackle first.
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
This is the bug check code for all Driver Verifier I/O Verification violations.
BugCheck C9, {23e, fffff880071fcde0,
fffff98006daaca0, 0}
The 3rd parameter of the bug check is the IRP address of the driver that has marked an IRP pending but didn't return STATUS_PENDING. Let's run an !irp on it:
Code:
2: kd> !irp fffff98006daaca0
Irp is active with 9 stacks 8 is current (= 0xfffff98006daaf68)
No Mdl: No System Buffer: Thread fffffa8004413660: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 10 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ f, 0] 0 10 fffffa8007931050 00000000 00000000-00000000
fffffa8007931050: Could not read device object or _DEVICE_OBJECT not found
Args: 00000000 00000000 00000000 00000000
[ f, 0] 0 10 fffffa80081ca9b0 00000000 fffff880071fb630-fffff880033bd270
fffffa80081ca9b0: Could not read device object or _DEVICE_OBJECT not found
gamingms
^^ FAILURE_BUCKET_ID: X64_0xc9_23e_
VRF_
gamingms+1de0
Unable to load image \SystemRoot\system32\drivers\gamingms.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for gamingms.sys
*** ERROR: Module load completed but symbols could not be loaded for gamingms.sys
Probably caused by : gamingms.sys ( gamingms+1de0 ) <--- matches failure bucket ID
This is the Primax USB Optical Gaming Mouse Driver. If we run an lmvm on it:
Code:
3: kd> lmvm gamingms
start end module name
fffff880`06f78000 fffff880`06f7aa80 gamingms (deferred)
Image path: gamingms.sys
Image name: gamingms.sys
Timestamp: Fri May 11 04:23:26 2007 (464427FE)
CheckSum: 000111D1
ImageSize: 00002A80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
We can see it's fairly old (dated from 2007). As far as I know this is an OEM mouse and there are no drivers available anywhere online. I have solved BSOD's in the past in which the user had to remove this mouse and plug in an alternative. Do you have a different mouse to test?
Also, I forgot to include on my OS, that I am using Service Pack #1. Should I get #2 Service Pack or not? Does it cost $?
There is no SP2 for Windows 7, only 1.
Regards,
Patrick
