random bsod after power loss

athu · 10 Nov 2010

hi all,

i had a power loss during startup last week and since that my system stops with various random BSODs during startup (minidump attached)
i tried launching the systen via any startup options given by pressing F8, checked the HDD using chkdsk and sfc, tried startup repair multiple times and nothing changes at all.
the most common stop screens are 'REFERENCE_BY_POINTER' (0x18), 'IRQL_NOT_LESS_OR_EQUAL' (0xA), 'cng.sys - Address XXXX base at YYYY, DateStamp ZZZZ' (0x8E) and some others like 0x7B, 0xD3 (pcw.sys)

it would be awesome if anyone has an idea what else i could try to fix the system..

thanks,
-a

zigzag3143 · 11 Nov 2010

athu said:

hi all,

i had a power loss during startup last week and since that my system stops with various random BSODs during startup (minidump attached)
i tried launching the systen via any startup options given by pressing F8, checked the HDD using chkdsk and sfc, tried startup repair multiple times and nothing changes at all.
the most common stop screens are 'REFERENCE_BY_POINTER' (0x18), 'IRQL_NOT_LESS_OR_EQUAL' (0xA), 'cng.sys - Address XXXX base at YYYY, DateStamp ZZZZ' (0x8E) and some others like 0x7B, 0xD3 (pcw.sys)

it would be awesome if anyone has an idea what else i could try to fix the system..

thanks,
-a

Ok where to start

Ancient drivers from 2002 till present

Code:

SonyPI.sys        0x826d1100    0x00008100    8/19/2002 21:59:29            0x3d61b091    0x826c9000                
tosrfcom.sys        0x94f39d80    0x0000fd80    8/1/2005 02:45:06            0x42edd302    0x94f2a000                
tosporte.sys        0x983db280    0x0000a280    10/10/2006 05:33:20            0x452b76f0    0x983d1000                
dwvkbd.sys        0x8edba000    0x0000a000    4/11/2007 16:23:28            0x461d51d0    0x8edb0000                
nvlddmkm.sys        0x96cfb140    0x006c9140    5/12/2007 01:39:48            0x46456134    0x96632000                
SFEP.sys        0x826d4480    0x00002480    8/3/2007 00:36:08            0x46b2bec8    0x826d2000                
vnasc.sys        0x98316820    0x0001d820    10/18/2007 01:38:06            0x4716ff4e    0x982f9000                
seehcri.sys    seehcri.sys+493    0x98326f00    0x00005f00    1/9/2008 03:41:37            0x478488c1    0x98321000                
fw.sys        0x98245c60    0x00221c60    1/23/2008 03:17:30            0x4796f81a    0x98024000                
DamewareMini.sys        0x98246e80    0x00000e80    3/16/2008 13:41:51            0x47dd69ef    0x98246000                
PGPwded.sys        0x891a0000    0x00039000    5/21/2008 12:26:29            0x48345b45    0x89167000                
PGPfsfd.sys        0x89167000    0x00024000    5/21/2008 12:29:39            0x48345c03    0x89143000                
yk62x86.sys        0x82699000    0x00050000    2/23/2009 09:44:18            0x49a2b642    0x82649000                
ay79lump.SYS        0x8273f000    0x00038000    3/21/2009 09:47:30            0x49c4fe02    0x82707000                
sptd.sys        0x88f92000    0x00101000    3/23/2009 01:38:33            0x49c72e69    0x88e91000                
netw5v32.sys        0x82649000    0x00413000    3/26/2009 11:10:37            0x49cba8fd    0x82236000                
spldr.sys        0x897d0000    0x00008000    5/11/2009 11:13:47            0x4a084ebb    0x897c8000                
amdxata.sys        0x890fe000    0x00009000    5/19/2009 12:57:35            0x4a12f30f    0x890f5000                
SYMTDI.SYS        0x94e69480    0x0002c480    6/17/2009 16:11:02            0x4a395be6    0x94e3d000                
SYMEVENT.SYS        0x8ed84000    0x00025000    6/24/2009 15:14:58            0x4a428942    0x8ed5f000

These must be updated

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

2-Symantec Old and causes BSOD's by itself. Remove and replace with Microsoft Security Essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

3- This file is from Sony Ericsson Mobile Communications and belongs to product seehcri Device. Seehcri.sys. Old and causing these BSOD's

Remove or find win 7 compatible version.

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\091110-49904-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83019000 PsLoadedModuleList = 0x83161810
Debug session time: Sat Sep 11 01:19:01.030 2010 (GMT-5)
System Uptime: 0 days 0:00:30.872
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a0f45000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 98321493, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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

Unable to load image \SystemRoot\system32\DRIVERS\seehcri.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for seehcri.sys

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 83181718
Unable to read MiSystemVaType memory at 83161160
 a0f45000 

FAULTING_IP: 
seehcri+493
98321493 663906          cmp     word ptr [esi],ax

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8b3238c4 -- (.trap 0xffffffff8b3238c4)
ErrCode = 00000000
eax=00000000 ebx=8667c320 ecx=7fffffff edx=7ffffffe esi=a0f45000 edi=8b323988
eip=98321493 esp=8b323938 ebp=8b323944 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210202
seehcri+0x493:
98321493 663906          cmp     word ptr [esi],ax        ds:0023:a0f45000=????
Resetting default scope

LOCK_ADDRESS:  8317ef60 -- (!locks 8317ef60)

Resource @ nt!PiEngineLock (0x8317ef60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x8317ef60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8305f638 to 8309e903

STACK_TEXT:  
8b3238ac 8305f638 00000000 a0f45000 00000000 nt!MmAccessFault+0x106
8b3238ac 98321493 00000000 a0f45000 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
8b323944 983247d5 a0f44ffe 7fffffff 8b323988 seehcri+0x493
8b323998 830554bc 8661ac08 00000000 8b323a18 seehcri+0x37d5
8b3239b0 831f5f03 c00000bb 8b323a4c 00000000 nt!IofCallDriver+0x63
8b3239e0 831c4d7e 852dc7f0 8b323a4c 852dc638 nt!IopSynchronousCall+0xc2
8b323a1c 831c4aa4 00000005 852dc638 00000000 nt!PnpIrpQueryID+0x3f
8b323a9c 831c0a17 00000001 00000000 86508d58 nt!PipProcessStartPhase3+0x2f2
8b323c94 831a4a42 852a9548 86508d58 8b323cc8 nt!PipProcessDevNodeTree+0x2e6
8b323cd4 8302cf9c 86508d58 8317ce80 852c0020 nt!PiProcessStartSystemDevices+0x6d
8b323d00 83086f3b 00000000 00000000 852c0020 nt!PnpDeviceActionWorker+0x241
8b323d50 832276d3 00000001 9573c3d0 00000000 nt!ExpWorkerThread+0x10d
8b323d90 830d90f9 83086e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
seehcri+493
98321493 663906          cmp     word ptr [esi],ax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  seehcri+493

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: seehcri

IMAGE_NAME:  seehcri.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  478488c1

FAILURE_BUCKET_ID:  0x50_seehcri+493

BUCKET_ID:  0x50_seehcri+493

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

4-SPTD.SYS used in alcohol120/daemon tools almost always causes BSOD's.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

I also would remove PGP

fix these and we can see what is really causing these.

Ken J

athu · 11 Nov 2010

dear ken,

thanks a lot for your suggestions! i will try to follow your advises, but i'm not sure if i can perform all of the actions due to the fact that i can not access the current windows 7 installation at all.
i hope to be able to fix some things via ubuntu, other than that i am afraid i need to do a fresh system setup...

but first, i'm going to try whatever is possible.

again, thanks a lot!
cheers
-a