Random BSOD probably due to bad drivers

Studvio · 15 Mar 2013

Hi guys, I'm new around here. I bought this laptop, I uninstalled Windows 8 and installed Windows 7 instead. It took me a while to find the drivers, and occasionally there's a BSOD, which I think is because of some incompatible driver(s). I'm not an expert, so if anyone could have a look at the ZIP file I created with SF_Diagnostic_Tool (thanks again Captain :)) and maybe give me some advice, it would be highly appreciated. I also have the four error messages saved from the "Event viewer" and the MEMORY.DMP file I found after restarting, in case someone need those as well.
Thank you,
Hamilton

Dsprague · 15 Mar 2013

Please post this before we begin: Windows Genuine and Activation Issue Posting Instructions

Studvio · 15 Mar 2013

Code:

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-GJY49-VJBQ7-HYRR2
Windows Product Key Hash: W5/6nm6F2UPXrCkY5xUhXb/+21g=
Windows Product ID: 00426-OEM-8992662-00006
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {9A14DDED-522E-432D-898A-1231C24E1E1F}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000000
Build lab: 7601.win7sp1_gdr.130104-1431
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 114 Blocked VLK 2
Microsoft Office XP Professional with FrontPage - 114 Blocked VLK 2
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Mozilla Firefox\firefox.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{9A14DDED-522E-432D-898A-1231C24E1E1F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-HYRR2</PKey><PID>00426-OEM-8992662-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-4072251998-22306983-348356900</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>Compaq CQ58 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Insyde</Manufacturer><Version>F.13</Version><SMBIOSVersion major="2" minor="7"/><Date>20120907000000.000000+000</Date></BIOS><HWID>A75E3A07018400F2</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90280409-6000-11D3-8CFE-0050048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office XP Professional with FrontPage</Name><Ver>10</Ver><Val>39476F84C4B4004</Val><Hash>4iCnywwNW1w4s9ukTIwGMGxyGic=</Hash><Pid>54185-640-0000025-17934</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="10" Result="114"/><App Id="16" Version="10" Result="114"/><App Id="17" Version="10" Result="114"/><App Id="18" Version="10" Result="114"/><App Id="1A" Version="10" Result="114"/><App Id="1B" Version="10" Result="114"/></Applications></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: 7cfd4696-69a9-4af7-af36-ff3d12b6b6c8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00178-926-600006-02-1033-7600.0000-0502013
Installation ID: 010393592901891743225015869895321530339763813076562064
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: HYRR2
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 15/03/2013 22:50:46

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 2:20:2013 03:44
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MAAAAAEAAQABAAEAAAADAAAAAgABAAEAJJSOb/QvqIRO5g6ZYj0C2EuHIIR8/FBe

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name    OEMID Value    OEMTableID Value
  APIC            HPQOEM        1885    
  FACP            HPQOEM        SLIC-MPC
  HPET            HPQOEM        1885    
  BOOT            HPQOEM        1885    
  MCFG            HPQOEM        1885    
  UEFI            HPQOEM        1885    
  ASF!            HPQOEM        1885    
  SPCR            HPQOEM        1885    
  FPDT            HPQOEM        1885    
  MSDM            HPQOEM        SLIC-MPC
  SSDT            HPQOEM        1885    
  SSDT            HPQOEM        1885    
  SLIC            HPQOEM        SLIC-MPC

Dsprague · 18 Mar 2013

Everything looks ok there, so Looking through your files I noted that most of them were rather quiet about the cause except for one which was a 0x7A:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c0416c48, c00000c0, 45d16860, 82d89da5}

GetPointerFromAddress: unable to read from 82d78830
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Code:

Normal causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

So With that information in hand please do the following:

Run memtest86+ for at least 8 passes: RAM - Test with Memtest86+ Tip: do this overnight it can take quite some time.

run the two following commands from an elevated command prompt:

Code:

sfc /scannow

And

Code:

chkdsk /f /r

the second command will ask you to reboot please do it will then run a chack disk prior to booting fully.

once those two are completed please do some hard drive diagnostics to insure that your hard disk is not having hardware problems: Hard Drive Diagnostic Procedure

And the last test I will have you do before we delve any deeper is check for viruses with these to specialized tools:

WDO
Tdsskiller

Let us know your results when you are done.

Studvio · 19 Mar 2013

Thank you for the answer, I will try that and let you know. Kind regards.
PS. It just happened again this morning :-(

Dsprague · 19 Mar 2013

Let us know your results when you get through all the things I asked you to do

Studvio · 19 Mar 2013

I will run that test tonight, in the meantime it just happened again, and I managed to take a photo with the phone, and after restart there was an windows with some error message:

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    2057

Additional information about the problem:
  BCCode:    50
  BCP1:    98A87000
  BCP2:    00000000
  BCP3:    82C3E573
  BCP4:    00000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\031913-53523-01.dmp
  C:\Users\Laptop\AppData\Local\Temp\WER-76487-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Obviously I did not install any hardware, and the laptop was brand new when I bought it about a month ago. Anyhow, hopefully I will have more information soon, after running those tests. Thanks.

Studvio · 26 Mar 2013

Hey guys, after running those tests nothing unusual was reported - as I said, it is a new laptop, only a couple of months old, and I would have been surprised if a memory or HD error was to be found. After running the Tdsskiller however I've noticed some strange programme (.EXE) that (Google-ing for it) I found it was related to Samsung Kies, for my mobile phone. I disabled it, and since then I did not have any problems. Finger crossed - problem solved!

So thanks Dsprague for the help, much appreciated.

PS. I can even access the content of my mobile phone now, which until disabling that file was not possible. Unfortunatelly I don't remember its name, as at that time it did not seem very important to me, and I did not think that it could cause the problems

After all, it was a driver problem as I thought.