Random BSOD

I used Win 7 HP upgrade to replace Vista Business. So I did a clean install, eventually deleted Windows.old, used CCleaner and defragged my OS partition.

Except for annoying BSODs (about 1-2 per day), it works fine. I would appreciate it if someone could look at the attached minidumps and point out what has to be done.

My PC system specs are Intel Core2 6600@2.4 Ghz, 4 GB RAM
After upgrading I had an additional 2 GB RAM installed

1) Mem86+ ran for 6 passes and showed no errors.
2) No overclocking or under-cooling, and no reason I know of to flash BIOS.

Thank you,
Daniel

dadio said:

I used Win 7 HP upgrade to replace Vista Business. So I did a clean install, eventually deleted Windows.old, used CCleaner and defragged my OS partition.

Except for annoying BSODs (about 1-2 per day), it works fine. I would appreciate it if someone could look at the attached minidumps and point out what has to be done.

My PC system specs are Intel Core2 6600@2.4 Ghz, 4 GB RAM
After upgrading I had an additional 2 GB RAM installed

1) Mem86+ ran for 6 passes and showed no errors.
2) No overclocking or under-cooling, and no reason I know of to flash BIOS.

Thank you,
Daniel

Daniel, this one was caused by SRTSP64.SYS part of your NORTON 2009. either remove it or uninstall it to see if it fixes the problem.

Since your already ran Memtest the only other thing I would do is run a system file check
type cmd in search>right click and run as admin>sfc /scannow

let us know the results

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\021810-23687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01c1e000 PsLoadedModuleList = 0xfffff800`01e5be50
Debug session time: Thu Feb 18 02:19:55.302 2010 (GMT-5)
System Uptime: 0 days 0:32:25.818
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 0, fffff8a010b96004}

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

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a010b96004, Address of the block of pool being deallocated

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


BUGCHECK_STR:  0xc2_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  TrustedInstall

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001dc160e to fffff80001c8ff00

STACK_TEXT:  
fffff880`15bdad68 fffff800`01dc160e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt!KeBugCheckEx
fffff880`15bdad70 fffff880`15757fe1 : fffff8a0`0bc431a8 fffff880`15e7e313 ffffffff`ffffffff 00000000`00000000 : nt!ExFreePool+0xccb
fffff880`15bdae20 fffff8a0`0bc431a8 : fffff880`15e7e313 ffffffff`ffffffff 00000000`00000000 fffff8a0`0bc431a8 : SRTSP64+0x4efe1
fffff880`15bdae28 fffff880`15e7e313 : ffffffff`ffffffff 00000000`00000000 fffff8a0`0bc431a8 fffff880`15e7a38e : 0xfffff8a0`0bc431a8
fffff880`15bdae30 ffffffff`ffffffff : 00000000`00000000 fffff8a0`0bc431a8 fffff880`15e7a38e fffff8a0`10b96004 : EX64+0x7e313
fffff880`15bdae38 00000000`00000000 : fffff8a0`0bc431a8 fffff880`15e7a38e fffff8a0`10b96004 fffff8a0`0bc43190 : 0xffffffff`ffffffff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SRTSP64+4efe1
fffff880`15757fe1 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  SRTSP64+4efe1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SRTSP64

IMAGE_NAME:  c
DEBUG_FLR_IMAGE_TIMESTAMP:  4b160164

FAILURE_BUCKET_ID:  X64_0xc2_7_SRTSP64+4efe1

BUCKET_ID:  X64_0xc2_7_SRTSP64+4efe1

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

Hi Captain and Ken,

Thanks for helping out.

Running sfc /scannow found and repaired corrupt files. I uploaded the relevant part of CBS.log

I also ran DriverEasy and used all the suggested updates, so drivers should be in better shape now.

Included in the upload are screen shots of HIDCLASS.SYS and PELUBLF.SYS, taken after updating with DriverEasy. I think HIDCLASS.SYS looks good, but the date on PELUBLF.SYS is still 2008. Right-clicking it in Win 7 doesn't offer updating. Perhaps this is not an issue after the DriverEasy update, which included mouse drivers.

I temporarily stopped Norton, but have let it restart when I restarted my PC. So far today there have been no BSODs. If this holds through evening, I'll mark this item SOLVED.

Daniel

This is hopefully a wrap-up to this thread.

I decided to completely uninstall Norton AV and replaced it with WSE. There have been no BSODs for two days.

I hope this helps others.

Daniel