Solved Win 7 BSOD ks.sys BAD_POOL_CALLER

[gforke]

My PC crashes sometimes, already tried to reinstall windows but even moving on a different drive (SSD) didnt solve the Problem.
Pls Help

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 109b, 40b0015, fffffa800bfa1f60}

*** WARNING: Unable to verify timestamp for tbs8922.sys
*** ERROR: Module load completed but symbols could not be loaded for tbs8922.sys
GetPointerFromAddress: unable to read from fffff800032ff100
GetUlongFromAddress: unable to read from fffff800032ff1c0
Probably caused by : ks.sys ( ks!CKsQueue::FreeStreamPointer+6b )

Followup: MachineOwner
---------

0: kd> lmvm tbs8922
start             end                 module name
fffff880`04323000 fffff880`04357080   tbs8922  T (no symbols)           
    Loaded symbol image file: tbs8922.sys
    Image path: \SystemRoot\system32\drivers\tbs8922.sys
    Image name:[B][COLOR="Red"] tbs8922.sys[/COLOR][/B]
    Timestamp:        Wed [COLOR="red"][B]Mar 07[/B][/COLOR] 18:13:53 [COLOR="red"][B]2012[/B][/COLOR] (4F5711B9)
    CheckSum:         000463A5
    ImageSize:        00034080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As far as I can tell the driver belongs to the TBS digital TV tuners.....do you have one installed? If so, see if you can update that driver:
TBS Download Center-Update the Latest Window & Linux Driver

 

[gforke]

Yes i have a TBS-8922 in my PC and i tought i already had the newest installed, used the new downloaded now to be sure. should i attach a second log ?

 

[Golden]

No, first follow this:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[gforke]

I cant boot to desktop with the verifier enabled should i attach the dmp files ?

 

[Golden]

No, there are no new .dmp files since Driver Verifier did not get a chance to work since you could not boot with it.

Just boot as normal and us the PC as normal. If it BSOD's again, then you can upload the new .dmp files.

 

[gforke]

the log collector found a new file... i have 3 instead of 2 now

 

[Golden]

the log collector found a new file... i have 3 instead of 2 now

Ah OK, good. Lets see it then - upload please.

 

[gforke]

here

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff88005a81710, fffff980039eccf0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

Followup: MachineOwner
---------

Please check the following:

1. Windows is fully updated (also check the Optional Upates)
2. All USB-connected device drivers are up-to-date
3. Any BlueTooth drivers are updated
4. Chipset drivers are up-to-date (especially any 3rd party USB drivers such as USB3.0)

Please use this tool to examine all the USB devices - post a screencapture of its view please:
View any installed/connected USB device on your system

Finally, please complete your system specifications using this tutorial (especially Step 5) - my German isn't good enough to translate the MSINFO:
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[gforke]

Here is the screen of usb deview

 

[Golden]

Were there any drivers that required updating?

 

[gforke]

i believe no and i didnt have any blue screens since.