BSOD error

#1
Hi,


I am running a HP G62 laptop withWindows 7 Home Premium. It is a 64 bit operating system with 4GB ofRAM running at 2.27GHz wit i3 processor.


Yesterday, I got a BSOD error. This is the first time I've evernoticed one of these so was a little alarmed. Unfortunately, Ididn't manage to get any of the STOP codes off the blue screen. Iattempted to find Minidump files but the folder was empty. I havealso installed Windows Debugging Tool but I couldn't find anything. Anyway, I looked in the reports section and found that I haveactually suffered four BSOD errors since July. But I don't rememberseeing a blue screen on any of the other occasions although I doremember the computer freezing up 100% and having to do a forcedreboot. Below I have copied and pasted the four BSOD errors asfeatured in my report section. Any advice on what is going wrongwould be appreciated:-
Source
Windows


Summary
Shutdown unexpectedly


Date
05/07/201102:21


Status
Reportsent


Problemsignature
ProblemEvent Name: BlueScreen
OSVersion: 6.1.7600.2.0.0.768.3
LocaleID: 2057


Extrainformation about the problem
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8007498060
BCP3: FFFFF800041F5518
BCP4: FFFFFA80094A6600
OSVersion: 6_1_7600
ServicePack: 0_0
Product: 768_1
BucketID: X64_0x9F_3_ASYNC_ADV_usbhub!Usbh_SSH_HubPendingSuspend+e1
Serverinformation: 2657fe7f-36c2-4452-8cd8-e9d14c10caeb
Source
Windows


Summary
Shutdown unexpectedly


Date
27/10/201111:18


Status
Reportsent


Problemsignature
ProblemEvent Name: BlueScreen
OSVersion: 6.1.7601.2.1.0.768.3
LocaleID: 2057


Extrainformation about the problem
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF880010C55BE
BCP3: FFFFF8800352B948
BCP4: FFFFF8800352B1A0
OSVersion: 6_1_7601
ServicePack: 1_0
Product: 768_1
BucketID: X64_0x7E_iaStor+725be
Serverinformation: fea7918d-cd04-444b-a6f4-49c7c353b2a9


Source
Windows


Summary
Shutdown unexpectedly


Date
28/10/201110:04


Status
Reportsent


Problemsignature
ProblemEvent Name: BlueScreen
OSVersion: 6.1.7601.2.1.0.768.3
LocaleID: 2057


Extrainformation about the problem
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8007472060
BCP3: FFFFF80000B9C518
BCP4: FFFFFA80044FD010
OSVersion: 6_1_7601
ServicePack: 1_0
Product: 768_1
BucketID: X64_0x9F_3_ASYNC_ADV_usbhub!Usbh_SSH_HubPendingSuspend+e1
Serverinformation: 23fa9ace-4ddf-4987-9381-2feba0a82d63


Source
Windows


Summary
Shutdown unexpectedly


Date
20/11/201111:19


Status
Reportsent


Problemsignature
ProblemEvent Name: BlueScreen
OSVersion: 6.1.7601.2.1.0.768.3
LocaleID: 2057


Extrainformation about the problem
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002CE6E60
OSVersion: 6_1_7601
ServicePack: 1_0
Product: 768_1
BucketID: X64_0xA_nt!PfTTraceListAdd+142
Serverinformation: d7d954b3-4935-4e9a-b75d-4c544b91e6d1


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


Trouble

Noob Whisperer
#2
Hello and welcome to the forum.
First, double check and make sure your system is setup correctly to accumulate minidumps.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
There is some discussion as to whether or not the actual location of your swapfile / pagefile can impact the system's ability to write .dmp files. So you might want to insure that the swapfile is located on your system drive.
Additionally
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Good luck
Randy
 


#3
Hi Randy,

Many thanks for your reply. I have followed instructions although I got a bit stuck with, 'RAMMon' request. Memory Tab - CPUI-Z.JPG SPD - CPU-Z.JPG

I hope the attached file contains everything needed. Please let me know if I need to do anything else.

Best Wishes,

Craig Mollekin
 


Attachments

Trouble

Noob Whisperer
#4
Craig:
Without an actual .dmp file to go on, it's difficult at best to suggest an approach to resolving your issue, except to perhaps ask some questions and see if we can sort through some evident issues. Not in any particular order but FYI and consideration.
First you have a product called IObits Advanced System Care in stalled along with a SunBelt Software product, perhaps Vipre or something similar. I might suggest you at least temporarily uninstall both products and consider replacing for the time being with MS Security Essentials You can always reinstall either or both products later if they prove not to be at issue.
Second you seem to have an unusual amount of legacy driver software;
SystemDrivers pre-dating Windows 7 RTM
Code:
SrvHsfHDA    16/10/2008
SrvHsfV92     16/10/2008
SrvHsfWinac 16/10/2008
Normally associated with some type of software modem
Code:
netw5v64    Intel(R) Wireless WiFi      26/03/2009
RimUsb        BlackBerry Smartphone    14/05/2007
yukonw7     Marvell Yukon Ethernet Card    23/02/2009
Code:
nfrd960      IBM ServeRAID Controller Driver                06/06/2006        
ql2300       QLogic Fibre Channel Stor Miniport Driver    22/01/2009        
ql40xx       QLogic iSCSI Storport Miniport Driver         19/05/2009        
stexstor    Promise SuperTrak EX Series Driver            17/02/2009        
vsmraid    VIA RAID DRIVER FOR X86-32                    31/01/2009
My suggestion would be to update these drivers (if possible) if needed, uninstall if not needed, or possibly renaming if uninstalling proves difficult or impossible.
Also additionally double check and confirm that your system is configured properly to write .dmp files to the C:\Windows\minidump folder as outlined in my original post. Make sure you have a pagefile and it is located on your system drive/partition.
Going to ask for some additional help from another member regarding your memory settings, they look a little askew to me but you only uploaded a single slot from the SPD tab and there is no RAMMon report in either text or html format to determine what the other slot might contain but it looks like you are running 1333 memory as 1066 not that that is a bad thing but sometimes memory timings are critical with these types of issues.
Regards
Randy
 


#5
Thanks, Randy. I will attempt to update those drivers and see what options I have with the security software. The Iobit generally is kept inactive except when I have problems such as this and then I attempt to clean up junk files etc.

The Vipre software was installed on the day of the first BSOD and coincidentally, the BSOD yesterday occurred straight after I disabled Vipre. So perhaps there is something suspicious with Vipre. I think the other BSODs may have occurred after my machine woke up from being asleep. Although as stated before, yesterday was the first time I've actually seen a blue screen.

I have now deactivated the automatic restart should another BSOD strike and I have changed the location of the .dmp file to the minidump location. Previously it was configured to save to a location ending in MEMORY.DMP (I think). I have also installed Windows Debugging Tool. So hopefully I will be better equipped to get the correct details if another BSOD occurs.

Upon restart, the machine works perfectly, so I'm not overly concerned. But I am a little alarmed and slightly worried it may become a regular occurrence.

Thanks again.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top