Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Persistent BSOD - Driver Verifier

  • Please log in to reply
1 reply to this topic

#1 SoulSnatcher


  • Members
  • 8 posts
  • Local time:01:01 PM

Posted 04 July 2012 - 03:15 PM

I've been having a persistent BSOD in the past few weeks. I decided to run Driver Verifier a couple days ago to find out the problem.

It just blue-screened and I zipped up the memory dump file below. Help?

System Info
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Gigabyte Technology Co., Ltd.
System Model M68MT-S2
System Type x64-based PC
Processor AMD FX™-4100 Quad-Core Processor, 3600 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Award Software International, Inc. FCd, 20/02/2012
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale Canada
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Uranium-PC\Uranium
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 6.33 GB

Edited by SoulSnatcher, 04 July 2012 - 03:16 PM.

BC AdBot (Login to Remove)


#2 AustrAlien



  • Members
  • 6,772 posts
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:04:01 AM

Posted 04 July 2012 - 04:35 PM

Interesting: A VERIFIER_ENABLED crash with a system uptime of 52 hours!

Probably caused by : t_mouse.sys

t_mouse.sys Thu Apr 16 23:45:37 2009

t_mouse.sys ... iBall Advanced Mouse driver http://www.iball.co.in/Download.aspx

It seems the mouse being used is causing the problem: Remove it.

Loading Dump File [C:\CactusIsland\SoulSnatcher_BC\070412-30217-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Thu Jul 5 05:57:26.731 2012 (UTC + 10:00)
System Uptime: 2 days 4:38:07.034
Unable to load image \SystemRoot\system32\DRIVERS\t_mouse.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for t_mouse.sys
*** ERROR: Module load completed but symbols could not be loaded for t_mouse.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : t_mouse.sys ( t_mouse+3310 )

The IO manager has caught a misbehaving driver.
Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
call to IoMarkIrpPending.
Arg2: fffff880069c6310, The address in the driver's code where the error was detected.
Arg3: fffff98048c3ecf0, IRP address.
Arg4: 0000000000000103, Status code.
BUGCHECK_STR: 0xc9_24c
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
FAILURE_BUCKET_ID: X64_0xc9_24c_VRF_t_mouse+3310
Bugcheck code 000000C9
Arguments 00000000`0000024c fffff880`069c6310 fffff980`48c3ecf0 00000000`00000103
BiosVersion = FCd
BiosReleaseDate = 02/20/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = M68MT-S2

Edited by AustrAlien, 04 July 2012 - 04:42 PM.

Google is my friend. Make Google your friend too.

Posted Image

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users