Blue Screen of Death (BSOD)

[zrizvi]

Hi,
After re-installation of windows 7 home premium 64 bit, on my HP laptop, I am facing Blue Screen of Death (BSOD) problem; I have followed the instructions and uploaded the log file. Appreciate your help.

Thanks
Zrizvi

 

[koolkat77]

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

AVG contributes to BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Remove the Synaptic Touch Pad Driver & Software if you don't really need it as it's causing the BSOD's for you.

   Tip

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\ZIA-PC-Wed_04_02_2014_183158_56\040214-28392-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305d6d0
Debug session time: Wed Apr  2 18:34:07.866 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:45.912
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 5, {fffffa8003cd6040, fffffa800b612060, 0, 1}

*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys ( SynTP+3ba0f )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INVALID_PROCESS_ATTACH_ATTEMPT (5)
Arguments:
Arg1: fffffa8003cd6040
Arg2: fffffa800b612060
Arg3: 0000000000000000
Arg4: 0000000000000001

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x5

PROCESS_NAME:  QLBController.

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

LAST_CONTROL_TRANSFER:  from fffff80002ef456a to fffff80002e8fbc0

STACK_TEXT:  
fffff800`00ba27b8 fffff800`02ef456a : 00000000`00000005 fffffa80`03cd6040 fffffa80`0b612060 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba27c0 fffff800`03186a2d : fffff8a0`00f07750 fffffa80`06b0a5f0 fffff8a0`00f07750 fffff800`00ba27f0 : nt! ?? ::FNODOBFM::`string'+0x2563b
fffff800`00ba2840 fffff800`03186721 : 00000000`00000000 fffffa80`00000000 fffff8a0`00001830 00000000`00000000 : nt!ObpDecrementHandleCount+0x17d
fffff800`00ba28c0 fffff800`03186ce4 : 00000000`00001730 fffffa80`0b612060 fffff8a0`00001830 00000000`00001730 : nt!ObpCloseHandleTableEntry+0xb1
fffff800`00ba2950 fffff800`02e8ee53 : fffffa80`0b60a060 fffff800`00ba2a20 fffff800`00ba2c88 fffffa80`048cf000 : nt!ObpCloseHandle+0x94
fffff800`00ba29a0 fffff800`02e8b410 : fffff800`0314a5ab 00000000`00000000 00000000`00000000 fffff800`00ba2c50 : nt!KiSystemServiceCopyEnd+0x13
fffff800`00ba2b38 fffff800`0314a5ab : 00000000`00000000 00000000`00000000 fffff800`00ba2c50 00000000`00000000 : nt!KiServiceLinkage
fffff800`00ba2b40 fffff880`0463ba0f : 00000000`00000001 fffff800`00ba2d30 00000000`00000000 00000000`00000000 : nt!RtlQueryRegistryValues+0x2ab
fffff800`00ba2c10 00000000`00000001 : fffff800`00ba2d30 00000000`00000000 00000000`00000000 00000000`00000000 : SynTP+0x3ba0f
fffff800`00ba2c18 fffff800`00ba2d30 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0460dd5b : 0x1
fffff800`00ba2c20 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`0460dd5b 00000000`00080006 : 0xfffff800`00ba2d30


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SynTP+3ba0f
fffff880`0463ba0f ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  SynTP+3ba0f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SynTP

IMAGE_NAME:  SynTP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5227915d

FAILURE_BUCKET_ID:  X64_0x5_SynTP+3ba0f

BUCKET_ID:  X64_0x5_SynTP+3ba0f

Followup: MachineOwner
---------

0: kd> lmvm SynTP
start             end                 module name
fffff880`04600000 fffff880`04686000   SynTP    T (no symbols)           
    Loaded symbol image file: SynTP.sys
    Image path: \SystemRoot\system32\DRIVERS\SynTP.sys
    Image name: SynTP.sys
    Timestamp:        Thu Sep 05 02:00:29 2013 (5227915D)
    CheckSum:         000840C1
    ImageSize:        00086000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[zrizvi]

Thank you koolkat77. So Synaptic Touch Pad Driver was the main culprit. :sarc:
Problem resolved. Much appreciated