Windows 7 Rare and one time occurance of STOP 24 BSOD

J

Jim Davis

New Member
Joined
Nov 9, 2010
Messages
4
Hi guys. I have a very stable (knock on wood) Win 7 X64 box that runs 15 hours a day. Just had a BSOD, first one in 5 months in the middle of work. My guess is it's a one off random thing but if you could look at the minidump I'd appreciate it. I think I was just clicking on an mp3 file, but not 100% sure. Did a chkdsk and drive came up 100% clean.
 

Attachments

Solution
T
Hi there, welcome.

No, there really is no such thing as a one-time bsod. If one happens, it needs to be fixed.

Uninstall Jetico Security as it caused the crash. If it is for antivirus, replace with MSE.

Code: 
Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88008642578, fffff88008641de0, fffff80002ecd664}

Unable to load image fsh.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fsh.SYS
*** ERROR: Module load completed but symbols could not be loaded for fsh.SYS
Probably caused by : fsh.SYS ( fsh+3c03 )

Followup: MachineOwner
---------
The driver is too old for Windows 7 to work well, even:

Code: 
0: kd> lmvm fsh
start             end                 module name
fffff880`01891000...
Sort by date Sort by votes
Hi there, welcome.

No, there really is no such thing as a one-time bsod. If one happens, it needs to be fixed.

Uninstall Jetico Security as it caused the crash. If it is for antivirus, replace with MSE.

Code: 
Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88008642578, fffff88008641de0, fffff80002ecd664}

Unable to load image fsh.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fsh.SYS
*** ERROR: Module load completed but symbols could not be loaded for fsh.SYS
Probably caused by : fsh.SYS ( fsh+3c03 )

Followup: MachineOwner
---------
The driver is too old for Windows 7 to work well, even:

Code: 
0: kd> lmvm fsh
start             end                 module name
fffff880`01891000 fffff880`0189c000   fsh      T (no symbols)           
    Loaded symbol image file: fsh.SYS
    Image path: fsh.SYS
    Image name: fsh.SYS
    Timestamp:        Tue Mar 24 10:10:26 2009 (49C8E9D2)
    CheckSum:         0000D0A3
    ImageSize:        0000B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
As far as stability, I have system uptimes for months here and use the machines for everything you can think of.

---------

As a side note, you can update your Realtek HD Audio driver. Run the install once, reboot and run it again:

RTKVHD64 RTKVHD64.sys Thu Dec 03 08:42:57 2009

Link Removed

----------

Update Realtek lan driver:

Rt64win7 Rt64win7.sys Sat Dec 19 04:11:30 2009

Link Removed

------------

Update NVIDIA video card driver:

nvlddmkm nvlddmkm.sys Tue Mar 16 20:21:57 2010

Link Removed - Invalid URL

--------------

Naviagte to C:\Windows\System32\driver and delete this old problematic driver then reboot:

lirsgt lirsgt.sys Sat Mar 06 14:53:01 2004

-----------
Definitely uninstall BestCrypt. The driver is too old:

mhk mhk.SYS Mon Aug 18 04:08:54 2008

Install the latest version of the absolute best software for this, Truecrypt, to replace.

------------

AVG is notorious for antivirus and slows down the file system...of which 0x24 crashes involve as well. Uninstall it in safe mode with the tool from the sticky thread in this section of the forum. I spoke above about installing MSE to replace.

-----------


And I would stop by Logitech's site to update all the hardware drivers that you have from them.


Enjoy.
 
Last edited:
Upvote 0 Downvote
Solution
Thanks for the fast reply.

Unless something recent got corrupted (not likely) I doubt if there's an issue with those drivers. At least nothing that is going to be a problem,

My guess is some unrepeatable combination of events caused the issue. If it happens again , I'll have to reconsider.
 
Upvote 0 Downvote
There's not any guessing on my part and none of this has to do with corruption, besides what happens in memory when there is a bsod. Those things need to be done to have a stable machine. Good luck with it.
 
Upvote 0 Downvote
You must log in or register to reply here.