Thought I'd be able to figure it out but am stuck BSOD

Hi all. After following Adrynalyne's guide I was hoping to be able to work out what was causing my Frequent BSOD. Have had 27 so far since the beginning of March! It only seems to happen when resuming from standby, after I have entered my password to log back on, but sadly not everytime which would probably make it a bit easier to diagnose. It happens more when the power isn't connected and it's running on battery. Also, a strange symptom is, and I dont know if it is linked but happens nonetheless, for some reason, after the BSOD and subsequent reboot when everything is back to normal. I open up IE9 and all my cookies seem to have been reset and I have to log back into websites (ones that I tick to stay logged onto). If I restart as normal this doesn't happen, it's only after crash recovery. The DUMP says fault probably caused by HIDCLASS.SYS but doesn't really give much other info. Am hoping one of you guys can get to the bottom of it. A challenge for some bright spark I hope.
My system is
Toshiba A500-1GL
i3 2.13Ghz
4GB DDR3 RAM
500GB HDD
nVidia GeForce GT330M
Windows 7 Home Premium 64Bit.
System still under warranty but would rather try and fix it myself that send it away for weeks.
Attached is minidump as a text file.

Cheers
J1M

 

I'd prefer to analyse a few dumps, a lot more can be discovered and maybe ruled out that way. HIDCLASS is probably mouse/keyboard related, if they're USB, check the power settings so they don't turn off to save power.

 

Thanks for helping. It is a laptop and I am just using the touchpad and built in keyboard. Do you just require a random selection of the dump files or all 27 of them?
Many Thanks
J1M

 

Here's a few more, although I think they all say the same thing.
Thanks

 

I'd like the original dumps, please - copy the last 5 to your Desktop, zip and attach them.

 

Sorry. Thought I was helping lol. Here you go thanks.
J1M

 

Some more history on the Tosh, please - updated to SP1 when? Date the 0x50 BSOD started? Any hardware updated/added, if so, dates? Can you post a screenshot from Add/Remove Programs, listed by date installed?

 

Hi again. Installed SP1 on the 9th march 2011. Had a lot of problems with it previously to that date so did a factory reset and started again because it made my internet go all screwy. the first dump file I have dated is 11th March 2011 because of that HDD Recovery but it was happening before that date but coincidently now I come to think of it, it might have been since installing SP1. The only hardware I have plugged in that isn't part of the system is a nano bluetooth dongle that has been in for a while now. It's a belkin one but system properties says it is a Broadcom Bluetooth 2.1+EDR USB Device. Drivers are all a up to date. I like to keep up to date. Had too many programs installed to fit on one screen so snipped a bit out from around the date of the first dump. HTH. Cheers
J1M

 

I'd like you to check and update, if possible, the following drivers listed as being loaded during the last dump (file dates/times are affected by time zones so not 100% accurate):

TVALZFL.sys 6/19/2009 11:05:44
pgeffect.sys 6/22/2009 10:00:11
tos_sps64.sys 6/24/2009 06:31:09
thpdrv.sys 6/29/2009 03:02:56
Thpevm.SYS 6/29/2009 09:15:37
LPCFilter.sys 7/28/2009 18:26:44
tdcmdpst.sys 7/30/2009 09:39:35
RTKVHD64.sys 8/31/2009 11:19:33
HECIx64.sys 9/17/2009 20:54:16
jmcr.sys 9/23/2009 03:24:55
iaStor.sys 10/2/2009 20:58:50
dump_iaStor.sys 10/2/2009 20:58:50
SynTP.sys 10/16/2009 03:28:35
Rt64win7.sys 11/5/2009 15:15:41
btusbflt.sys 4/9/2010 02:11:36
rtl8192se.sys 6/28/2010 14:02:00
MpFilter.sys 9/15/2010 01:19:28
MpNWMon.sys 9/15/2010 01:19:30
NisDrvWFP.sys 9/15/2010 01:20:25
nvhda64v.sys 11/12/2010 00:10:36

Running a Find for each driver on this page should help you track down what loads them and where they can be updated from (this page isn't fully updated), anything not listed there, check them with a search engine - but be careful of the scamware sites. Don't update anything unless it's from a legit source - Tosh, MSFT, hardware suppliers, etc.

 

Awesome. thanks dude. will get back to you asap. gonna take a few hours. got stuff to do.

 

No worries, I'll post up a generic list of causes and possible fixes for you to think on regarding this particular BSOD (gleaned from carrona.org), my feeling is that an older driver (possibly an original Tosh driver - look to them for any patches?) may be causing conflicts with something recently installed (SP1?). It might well be power saving related, difficult to say. There's also a slim chance that it's a malware thing, triggered by wininnit.ini, for example.

Code:

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Cause:

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.


Resolving the Problem

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

It'd be worthwhile going through that list carefully and running any suggested tests/checks; make notes as you go, in case you need to prove to Tosh that it's a hardware error so you can get a fast replacement.