BSOD with gamingsms.sys errors and other errors.

Hi MrCiv,

There seems to have been a problem when posting your attachments - for some reason they weren't uploaded. My apologies you're having difficulty with the posting instructions - I've asked that we revise the instructions to make them a bit clearer for novice users.

If you've managed to run our collection app, there should have been a folder created in your Documents folder called "Windows7_Vista_jcgriff2". If you right click on this folder, you should have the option to compress the folder. If you don't see it, check the Send To option and select Compressed Folder.

Did you manage to complete Step 3 in the posting instructions?

3. Run System Health Report -
START | type perfmon /report | save as HTML file


If so, you can also compress the file in the same way and attach both to your next reply. Please note, always make sure to come back to the site itself to post your reply. We read emails, but you'll receive a much faster response if your reply is posted through the site itself.

Received via email reply:

To: Patrick and Other Tech Experts at BSOD:

Do you know, you guys have lots of jumping thru hoops here for the novice people not used to using zip files like me?
Question #1: You say in Question #4:"Zip up the output folder (#2) + PERFMON to zip up the files"...Uh, where am I supposed to "zip up" the contents of the "Windows7_Vista_jcgriff2" folder TO? (Assuming I know how to use my zip program called WinZip, which I don't!)
Question #2: Just tell me the exact steps to follow inside WinZip if u would please, to "zip up" the files u want and where u want them..Please?
Question #3. So you want me to attach stuff inside a program that I haven't even seen before or been inside of, i.e. your BSOD instruction sheet ((Where it says ("create a new thread here, and attach the files")), let alone you want to me attach stuff to it?

Comments: So help me out here; Do u want your files or don't you? I want you to have the files. I just want to get this BSOD thingy fixed. Because my PC is crapping out on everything right now, and it's really ticking me off!.....
You guys make these "Posting" instructions too hard for novice users like me.
Would you please make the instructions easier to follow and not so many weird steps.
C'mon, be reasonable and logical for us 'non-experts" out here. You're talking over my head...
Just frustrated, but thanks for your help anyway, Clifford Floyd - Cliff - (MrCiv)
Click to expand...
 
Thanks Clifford, they've uploaded correctly now. A helper will post back shortly.
 
Cool thanks, i hope that u guys can figure it all out to get my PC working back to normal now.
BTW: The system will not recognize my E: drive. It is the 2nd drive listed out of 4 drives. I have C:, E:, F:, and G: drives respectively.
AND it takes quite awhile (5 minutes or longer), for the system to boot up AFTER it says "Loading Windows".
Sometimes (more often than not), it just sits there, and I have to do another hard reset of powering off the PC.
On the 3rd try of hard resetting the PC, it usually reboots into Windows ok, but the PC is very slow in letting me go into different programs. Any thoughts as to why?
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 $?
Also, I am seriously considering installing a new wireless keyboard and wireless mouse and a newer (Video Card, i.e. EVGA 650Ti for about $163).
Do you think once you get the system working again, it would be wise for me to order this stuff for Xmas for upgrading my PC?
Thanks. MrCiv.
 
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:

  1. 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.
  2. 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: [I][B]Could not read device object or _DEVICE_OBJECT not found
    [COLOR=#ff0000]gamingms[/COLOR][/B][/I]

^^ 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
[I][B]    Timestamp:        Fri May 11 04:23:26 [COLOR=#ff0000]2007[/COLOR] (464427FE)[/B][/I]
    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 $?
Click to expand...

There is no SP2 for Windows 7, only 1.

Regards,

Patrick
 
Patrick said:
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:

  1. 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.
  2. 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: [I][B]Could not read device object or _DEVICE_OBJECT not found
    [COLOR=#ff0000]gamingms[/COLOR][/B][/I]

^^ 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
[I][B]    Timestamp:        Fri May 11 04:23:26 [COLOR=#ff0000]2007[/COLOR] (464427FE)[/B][/I]
    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 $?
Click to expand...

There is no SP2 for Windows 7, only 1.

Regards,

Patrick
Click to expand...
 
There doesn't seem to be anything in your post. Care to edit and try again?

Regards,

Patrick
 
The Comments below this line, was my latest posting.

Cool thanks, i hope that u guys can figure it all out to get my PC working back to normal now.
BTW: The system will not recognize my E: drive. It is the 2nd drive listed out of 4 drives. I have C:, E:, F:, and G: drives respectively.
AND it takes quite awhile (5 minutes or longer), for the system to boot up AFTER it says "Loading Windows".
Sometimes (more often than not), it just sits there, and I have to do another hard reset of powering off the PC.
On the 3rd try of hard resetting the PC, it usually reboots into Windows ok, but the PC is very slow in letting me go into different programs. Any thoughts as to why?
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 $?
Also, I am seriously considering installing a new wireless keyboard and wireless mouse and a newer (Video Card, i.e. EVGA 650Ti for about $163).
Do you think once you get the system working again, it would be wise for me to order this stuff for Xmas for upgrading my PC?
Thanks. MrCiv.
 
Right, I saw that in your above post prior to my post. Do you understand what I recommended you to do? Anything you need help understanding?

Regards,

Patrick
 
I think this is the missing post - it came in via email a while ago:

Hey Patrick: I do have an (old roller ball inside the mouse) IBM brand mouse I could use, (of course, first assuming it works tho!).
What is the next course of action that I do?
Do I unplug my newer mouse and uninstall the bad driver or what?
And find an IBM driver for my old mouse?
Tell me what to do and I'll do it.
Thanks, MrCiv
Click to expand...
 
If i understand you correctly, I need to install a different mouse (hardware) to get rid of the bad mouse driver (software), right?
I actually found a micro mouse for my laptop I can plug in, that is better than that old IBM mouse I referred to earlier.
Question #1: Does the driver automatically get looked up via Windows so it can install one?
Question #2: OR do I have to see the brand of the mouse and try to find a driver via the mouse maker?
I just want to do the right thing here.
 
You should just be able to plug it in and Windows will install the generic driver.

Regards,

Patrick
 
I did plug it my laptop mouse and it did install a generic driver.
But the next problem I will have is this: The moment I unplug my (old) mouse, I will have no keyboard to be able to type with. I just unplugged it, and had no typing ability, so i re-plugged it in. So I know that is the case.
It is using a Logitech connect software program to connect my mouse and keyboard together.
If I uninstall the driver for my mouse (Assuming it's the gamingms.sys file, If I can find it?), then no typing ability. I don't know what will happen with the new (laptop) mouse in the PC, if I will have typing ability or not. I'm guessing probably not.
What do you recommend I do?
 
I'm thinking I am going to have to buy a new mouse and a new keyboard, but I told you about that already.
So how do I actually get rid of the gamingms.sys file itself? I located it in the Windows/System32 directory.
That is the culprit is it not?
 
Did that Logitech software come with the mouse CD or the system itself? I've never heard of such a software. Have you tried uninstalling that software, restarting, plugging in new mouse and seeing if you can type? I would create a restore point before doing so just in case - Windows 7 - START | type create | select "Create a Restore Point".

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top