Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD on startup

09 Oct 2010   #1
Ahad

Windows 7 Home Premium 32 bit
 
 
BSOD on startup

Hi i get BSOD during my WIN 7 32bit HP startup.. the PC restarts and if i select start up normally it works as if nothing has happened.. I am attaching the dmp files.. please give some advice..


My System SpecsSystem Spec
.
09 Oct 2010   #2
lorddenis

 

please folow this posting instructions:

https://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
09 Oct 2010   #3
cybercore

Windows 7 x64
 
 

100810-20545-01.dmp
BugCheck 1000007E, {c0000005, ...
0x7E_nt!ObpLookupDirectoryEntry

092910-23072-01.dmp
BugCheck 1000007E, {c0000005, ...
0x7E_nt!ObpLookupDirectoryEntry

100910-20077-01.dmp
BugCheck 1000007E, {c0000005, ...
nt!ObpLookupDirectoryEntry



Update:

ATITool.sys Fri Nov 10 15:08:51 2006
ATI Tray Tools
ATI Tray Tools download from Guru3D.com

iaStor.sys Fri Oct 02 22:38:45 2009
Intel Matrix Storage
http://downloadcenter.intel.com/
Intel® Driver Update Utility



Visit Toshiba support for updates:

TVALZ_O.SYS Tue Jul 14 05:19:21 2009
tos_sps32.sys Wed Jun 24 08:36:21 2009
Toshiba Support - Homepage



Uninstall Symantec and install MSE to replace:

ftp://ftp.symantec.com/public/englis...moval_Tool.exe

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



If crashes persist, attach the latest .dmp files and run memtest overnght:

Memtest86+ - Advanced Memory Diagnostic Tool

RAM - Test with Memtest86+



Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\100810-20545-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83215000 PsLoadedModuleList = 0x8335d810
Debug session time: Fri Oct  8 08:36:43.139 2010 (GMT-5)
System Uptime: 0 days 0:00:11.715
Loading Kernel Symbols
...............................................................
................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 83437123, 80786890, 80786470}

Probably caused by : ntkrpamp.exe ( nt!ObpLookupDirectoryEntry+2b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 83437123, The address that the exception occurred at
Arg3: 80786890, Exception Record Address
Arg4: 80786470, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
nt!ObpLookupDirectoryEntry+2b
83437123 0fb702          movzx   eax,word ptr [edx]

EXCEPTION_RECORD:  80786890 -- (.exr 0xffffffff80786890)
ExceptionAddress: 83437123 (nt!ObpLookupDirectoryEntry+0x0000002b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000cbc0
Attempt to read from address 0000cbc0

CONTEXT:  80786470 -- (.cxr 0xffffffff80786470)
eax=80786900 ebx=00000000 ecx=880f1724 edx=0000cbc0 esi=80786990 edi=00000007
eip=83437123 esp=80786958 ebp=80786968 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!ObpLookupDirectoryEntry+0x2b:
83437123 0fb702          movzx   eax,word ptr [edx]       ds:0023:0000cbc0=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0000cbc0

READ_ADDRESS: GetPointerFromAddress: unable to read from 8337d718
Unable to read MiSystemVaType memory at 8335d160
 0000cbc0 

FOLLOWUP_IP: 
nt!ObpLookupDirectoryEntry+2b
83437123 0fb702          movzx   eax,word ptr [edx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 83437001 to 83437123

STACK_TEXT:  
80786968 83437001 8a469dd8 880f1724 00000000 nt!ObpLookupDirectoryEntry+0x2b
807869a4 8341e052 880f1738 880f9000 880f1748 nt!ObpDeleteNameCheck+0xfb
807869bc 833b8874 880f1748 00000000 87fbb1c4 nt!ObMakeTemporaryObject+0x93
80786b9c 835c6853 00000001 00000000 80786bd4 nt!IopLoadDriver+0x921
80786be8 835c287b 80811248 8080a8f8 00000000 nt!IopInitializeSystemDrivers+0x163
80786c6c 835c7e78 0080a8f8 853bfda0 853bfa30 nt!IoInitSystem+0x6de
80786d48 833a0494 80786d90 834236d3 8080a8f8 nt!Phase1InitializationDiscard+0xced
80786d50 834236d3 8080a8f8 9fcb41e7 00000000 nt!Phase1Initialization+0xd
80786d90 832d50f9 833a0487 8080a8f8 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpLookupDirectoryEntry+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

STACK_COMMAND:  .cxr 0xffffffff80786470 ; kb

FAILURE_BUCKET_ID:  0x7E_nt!ObpLookupDirectoryEntry+2b

BUCKET_ID:  0x7E_nt!ObpLookupDirectoryEntry+2b

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














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


Loading Dump File [F:\a\Minidump\D M P\092910-23072-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83245000 PsLoadedModuleList = 0x8338d810
Debug session time: Wed Sep 29 11:42:13.496 2010 (GMT-5)
System Uptime: 0 days 0:00:13.682
Loading Kernel Symbols
...............................................................
................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 83467123, 80786890, 80786470}

Probably caused by : ntkrpamp.exe ( nt!ObpLookupDirectoryEntry+2b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 83467123, The address that the exception occurred at
Arg3: 80786890, Exception Record Address
Arg4: 80786470, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
nt!ObpLookupDirectoryEntry+2b
83467123 0fb702          movzx   eax,word ptr [edx]

EXCEPTION_RECORD:  80786890 -- (.exr 0xffffffff80786890)
ExceptionAddress: 83467123 (nt!ObpLookupDirectoryEntry+0x0000002b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000e5d8
Attempt to read from address 0000e5d8

CONTEXT:  80786470 -- (.cxr 0xffffffff80786470)
eax=80786900 ebx=00000000 ecx=88367b8c edx=0000e5d8 esi=80786990 edi=00000007
eip=83467123 esp=80786958 ebp=80786968 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210202
nt!ObpLookupDirectoryEntry+0x2b:
83467123 0fb702          movzx   eax,word ptr [edx]       ds:0023:0000e5d8=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0000e5d8

READ_ADDRESS: GetPointerFromAddress: unable to read from 833ad718
Unable to read MiSystemVaType memory at 8338d160
 0000e5d8 

FOLLOWUP_IP: 
nt!ObpLookupDirectoryEntry+2b
83467123 0fb702          movzx   eax,word ptr [edx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 83467001 to 83467123

STACK_TEXT:  
80786968 83467001 8a467550 88367b8c 00000000 nt!ObpLookupDirectoryEntry+0x2b
807869a4 8344e052 88367ba0 8835a000 88367bb0 nt!ObpDeleteNameCheck+0xfb
807869bc 833e8874 88367bb0 00000000 881e09b4 nt!ObMakeTemporaryObject+0x93
80786b9c 835f6853 00000001 00000000 80786bd4 nt!IopLoadDriver+0x921
80786be8 835f287b 8080fc28 8080a890 00000000 nt!IopInitializeSystemDrivers+0x163
80786c6c 835f7e78 0080a890 853bfda0 853bfa30 nt!IoInitSystem+0x6de
80786d48 833d0494 80786d90 834536d3 8080a890 nt!Phase1InitializationDiscard+0xced
80786d50 834536d3 8080a890 9fe19cb0 00000000 nt!Phase1Initialization+0xd
80786d90 833050f9 833d0487 8080a890 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpLookupDirectoryEntry+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

STACK_COMMAND:  .cxr 0xffffffff80786470 ; kb

FAILURE_BUCKET_ID:  0x7E_nt!ObpLookupDirectoryEntry+2b

BUCKET_ID:  0x7E_nt!ObpLookupDirectoryEntry+2b

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













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


Loading Dump File [F:\a\Minidump\D M P\100910-20077-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8320b000 PsLoadedModuleList = 0x83353810
Debug session time: Sat Oct  9 14:40:32.674 2010 (GMT-5)
System Uptime: 0 days 0:00:09.250
Loading Kernel Symbols
...............................................................
................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8342d123, 80786890, 80786470}

Probably caused by : ntkrpamp.exe ( nt!ObpLookupDirectoryEntry+2b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8342d123, The address that the exception occurred at
Arg3: 80786890, Exception Record Address
Arg4: 80786470, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
nt!ObpLookupDirectoryEntry+2b
8342d123 0fb702          movzx   eax,word ptr [edx]

EXCEPTION_RECORD:  80786890 -- (.exr 0xffffffff80786890)
ExceptionAddress: 8342d123 (nt!ObpLookupDirectoryEntry+0x0000002b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 000026e8
Attempt to read from address 000026e8

CONTEXT:  80786470 -- (.cxr 0xffffffff80786470)
eax=80786900 ebx=00000000 ecx=880bd084 edx=000026e8 esi=80786990 edi=00000007
eip=8342d123 esp=80786958 ebp=80786968 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!ObpLookupDirectoryEntry+0x2b:
8342d123 0fb702          movzx   eax,word ptr [edx]       ds:0023:000026e8=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  000026e8

READ_ADDRESS: GetPointerFromAddress: unable to read from 83373718
Unable to read MiSystemVaType memory at 83353160
 000026e8 

FOLLOWUP_IP: 
nt!ObpLookupDirectoryEntry+2b
8342d123 0fb702          movzx   eax,word ptr [edx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 8342d001 to 8342d123

STACK_TEXT:  
80786968 8342d001 8a45b6c0 880bd084 00000000 nt!ObpLookupDirectoryEntry+0x2b
807869a4 83414052 880bd098 88106000 880bd0a8 nt!ObpDeleteNameCheck+0xfb
807869bc 833ae874 880bd0a8 00000000 87fa98cc nt!ObMakeTemporaryObject+0x93
80786b9c 835bc853 00000001 00000000 80786bd4 nt!IopLoadDriver+0x921
80786be8 835b887b 80811248 8080a928 00000000 nt!IopInitializeSystemDrivers+0x163
80786c6c 835bde78 0080a928 853bfda0 853bfa30 nt!IoInitSystem+0x6de
80786d48 83396494 80786d90 834196d3 8080a928 nt!Phase1InitializationDiscard+0xced
80786d50 834196d3 8080a928 9ffd02e7 00000000 nt!Phase1Initialization+0xd
80786d90 832cb0f9 83396487 8080a928 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpLookupDirectoryEntry+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

STACK_COMMAND:  .cxr 0xffffffff80786470 ; kb

FAILURE_BUCKET_ID:  0x7E_nt!ObpLookupDirectoryEntry+2b

BUCKET_ID:  0x7E_nt!ObpLookupDirectoryEntry+2b

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




start    end        module name
80bb8000 80bc0000   kdcom    kdcom.dll    Tue Jul 14 04:08:58 2009 (4A5BDAAA)
8320b000 8361b000   nt       ntkrpamp.exe Sat Jun 19 06:55:24 2010 (4C1C3FAC)
8361b000 83652000   hal      halmacpi.dll Tue Jul 14 02:11:03 2009 (4A5BBF07)
88e08000 88e80000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:06:41 2009 (4A5BDA21)
88e80000 88e91000   PSHED    PSHED.dll    Tue Jul 14 04:09:36 2009 (4A5BDAD0)
88e91000 88e99000   BOOTVID  BOOTVID.dll  Tue Jul 14 04:04:34 2009 (4A5BD9A2)
88e99000 88edb000   CLFS     CLFS.SYS     Tue Jul 14 02:11:10 2009 (4A5BBF0E)
88edb000 88f86000   CI       CI.dll       Tue Jul 14 04:09:28 2009 (4A5BDAC8)
88f86000 88ff7000   Wdf01000 Wdf01000.sys Tue Jul 14 02:11:36 2009 (4A5BBF28)
89004000 89012000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
89012000 8905a000   ACPI     ACPI.sys     Tue Jul 14 02:11:11 2009 (4A5BBF0F)
8905a000 89063000   WMILIB   WMILIB.SYS   Tue Jul 14 02:11:22 2009 (4A5BBF1A)
89063000 8906b000   msisadrv msisadrv.sys Tue Jul 14 02:11:09 2009 (4A5BBF0D)
8906b000 89095000   pci      pci.sys      Tue Jul 14 02:11:16 2009 (4A5BBF14)
89095000 890a0000   vdrvroot vdrvroot.sys Tue Jul 14 02:46:19 2009 (4A5BC74B)
890a0000 890b1000   partmgr  partmgr.sys  Tue Jul 14 02:11:35 2009 (4A5BBF27)
890b1000 890b9000   compbatt compbatt.sys Tue Jul 14 02:19:18 2009 (4A5BC0F6)
890b9000 890c4000   BATTC    BATTC.SYS    Tue Jul 14 02:19:15 2009 (4A5BC0F3)
890c4000 890d4000   volmgr   volmgr.sys   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
890d4000 8911f000   volmgrx  volmgrx.sys  Tue Jul 14 02:11:41 2009 (4A5BBF2D)
8911f000 89135000   mountmgr mountmgr.sys Tue Jul 14 02:11:27 2009 (4A5BBF1F)
89135000 8913c000   pciide   pciide.sys   Tue Jul 14 02:11:19 2009 (4A5BBF17)
8913c000 8914a000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:11:15 2009 (4A5BBF13)
8914a000 8917e000   fltmgr   fltmgr.sys   Tue Jul 14 02:11:13 2009 (4A5BBF11)
8917e000 891d5000   SYMDS    SYMDS.SYS    Tue May 18 04:12:04 2010 (4BF1E964)
891d5000 891e6000   fileinfo fileinfo.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
89200000 89223000   ataport  ataport.SYS  Tue Jul 14 02:11:18 2009 (4A5BBF16)
89223000 8922d000   msahci   msahci.sys   Tue Jul 14 02:45:50 2009 (4A5BC72E)
8922d000 893e0000   iaStor   iaStor.sys   Fri Oct 02 22:38:45 2009 (4AC656C5)
893e0000 893e9000   atapi    atapi.sys    Tue Jul 14 02:11:15 2009 (4A5BBF13)
893e9000 893f2000   amdxata  amdxata.sys  Tue May 19 20:57:35 2009 (4A12F30F)
89438000 894e1000   SYMEFA   SYMEFA.SYS   Fri Jul 23 05:19:19 2010 (4C48FC27)
894e1000 89598000   ndis     ndis.sys     Tue Jul 14 02:12:24 2009 (4A5BBF58)
89598000 895d6000   NETIO    NETIO.SYS    Tue Jul 14 02:12:35 2009 (4A5BBF63)
895d6000 895fb000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:04:22 2009 (4B21C4C6)
89600000 8960e000   pcw      pcw.sys      Tue Jul 14 02:11:10 2009 (4A5BBF0E)
8960e000 89617000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:11:14 2009 (4A5BBF12)
89631000 89760000   Ntfs     Ntfs.sys     Tue Jul 14 02:12:05 2009 (4A5BBF45)
89760000 8978b000   msrpc    msrpc.sys    Tue Jul 14 02:11:59 2009 (4A5BBF3F)
8978b000 8979e000   ksecdd   ksecdd.sys   Tue Jul 14 02:11:56 2009 (4A5BBF3C)
8979e000 897fb000   cng      cng.sys      Tue Jul 14 02:32:55 2009 (4A5BC427)
89801000 8994a000   tcpip    tcpip.sys    Mon Jun 14 06:36:59 2010 (4C15A3DB)
8994a000 8997b000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:12:03 2009 (4A5BBF43)
8997b000 89983000   wd       wd.sys       Tue Jul 14 02:11:31 2009 (4A5BBF23)
89983000 899c2000   volsnap  volsnap.sys  Tue Jul 14 02:11:34 2009 (4A5BBF26)
899c2000 899c6100   TVALZ_O  TVALZ_O.SYS  Tue Jul 14 05:19:21 2009 (4A5BEB29)
89a2a000 89a71000   tos_sps32 tos_sps32.sys Wed Jun 24 08:36:21 2009 (4A41BB55)
89a71000 89a79000   spldr    spldr.sys    Mon May 11 19:13:47 2009 (4A084EBB)
89a79000 89aa6000   rdyboost rdyboost.sys Tue Jul 14 02:22:02 2009 (4A5BC19A)
89aa6000 89ab6000   mup      mup.sys      Tue Jul 14 02:14:14 2009 (4A5BBFC6)
89ab6000 89abe000   hwpolicy hwpolicy.sys Tue Jul 14 02:11:01 2009 (4A5BBF05)
89abe000 89af0000   fvevol   fvevol.sys   Sat Sep 26 05:24:21 2009 (4ABD7B55)
89af0000 89b01000   disk     disk.sys     Tue Jul 14 02:11:28 2009 (4A5BBF20)
89b01000 89b26000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:11:20 2009 (4A5BBF18)
89b26000 89b33000   crashdmp crashdmp.sys Tue Jul 14 02:45:50 2009 (4A5BC72E)
89b33000 89b3f000   vga      vga.sys      Tue Jul 14 02:25:50 2009 (4A5BC27E)
89b3f000 89b60000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:25:49 2009 (4A5BC27D)
89b60000 89b6d000   watchdog watchdog.sys Tue Jul 14 02:24:10 2009 (4A5BC21A)
89b6d000 89b75000   rdpencdd rdpencdd.sys Tue Jul 14 03:01:39 2009 (4A5BCAE3)
89b75000 89b7d000   rdprefmp rdprefmp.sys Tue Jul 14 03:01:41 2009 (4A5BCAE5)
89b7d000 89b88000   Msfs     Msfs.SYS     Tue Jul 14 02:11:26 2009 (4A5BBF1E)
89b88000 89b96000   Npfs     Npfs.SYS     Tue Jul 14 02:11:31 2009 (4A5BBF23)
89b96000 89bad000   tdx      tdx.sys      Tue Jul 14 02:12:10 2009 (4A5BBF4A)
89bad000 89bb8000   TDI      TDI.SYS      Tue Jul 14 02:12:12 2009 (4A5BBF4C)
89bb8000 89bf9000   rdbss    rdbss.sys    Tue Jul 14 02:14:26 2009 (4A5BBFD2)
8ee07000 8efba000   dump_iaStor dump_iaStor.sys Fri Oct 02 22:38:45 2009 (4AC656C5)
8efba000 8efcb000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:12:47 2009 (4A5BBF6F)
8efcb000 8efea000   cdrom    cdrom.sys    Tue Jul 14 02:11:24 2009 (4A5BBF1C)
8efea000 8eff1000   Null     Null.SYS     Tue Jul 14 02:11:12 2009 (4A5BBF10)
8eff1000 8eff8000   Beep     Beep.SYS     Tue Jul 14 02:45:00 2009 (4A5BC6FC)
8eff8000 8f000000   RDPCDD   RDPCDD.sys   Tue Jul 14 03:01:40 2009 (4A5BCAE4)
8fe18000 8fe72000   afd      afd.sys      Tue Jul 14 02:12:34 2009 (4A5BBF62)
8fe72000 8fea4000   netbt    netbt.sys    Tue Jul 14 02:12:18 2009 (4A5BBF52)
8fea4000 8fead000   ws2ifsl  ws2ifsl.sys  Tue Jul 14 02:55:01 2009 (4A5BC955)
8fead000 8feb4000   wfplwf   wfplwf.sys   Tue Jul 14 02:53:51 2009 (4A5BC90F)
8feb4000 8fed3000   pacer    pacer.sys    Tue Jul 14 02:53:58 2009 (4A5BC916)
8fed3000 8fee4000   vwififlt vwififlt.sys Tue Jul 14 02:52:03 2009 (4A5BC8A3)
8fee4000 8fef0000   SymIMv   SymIMv.sys   Wed Jul 07 06:08:55 2010 (4C33EFC7)
8fef0000 8fefe000   netbios  netbios.sys  Tue Jul 14 02:53:54 2009 (4A5BC912)
8fefe000 8ff0da00   tosrfcom tosrfcom.sys Tue Jul 28 13:18:06 2009 (4A6ED05E)
8ff0e000 8ff21000   wanarp   wanarp.sys   Tue Jul 14 02:55:02 2009 (4A5BC956)
8ff21000 8ff31000   termdd   termdd.sys   Tue Jul 14 03:01:35 2009 (4A5BCADF)
8ff31000 8ff80000   SYMNETS  SYMNETS.SYS  Wed Jul 07 06:11:18 2010 (4C33F056)
8ff80000 8ffa6000   SYMEVENT SYMEVENT.SYS Sat Jul 31 02:05:03 2010 (4C535A9F)
8ffa6000 8ffc9000   Ironx86  Ironx86.SYS  Thu Jun 24 03:27:03 2010 (4C22A657)
8ffc9000 8ffd3980   SRTSPX   SRTSPX.SYS   Wed Jul 28 01:15:42 2010 (4C4F5A8E)
8ffd4000 8ffde000   nsiproxy nsiproxy.sys Tue Jul 14 02:12:08 2009 (4A5BBF48)
8ffde000 8ffe8000   mssmbios mssmbios.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD)
9040d000 90468000   IDSvix86 IDSvix86.sys Sat Sep 11 00:53:26 2010 (4C8AA8D6)
90468000 904c6000   eeCtrl   eeCtrl.sys   Sat May 22 00:44:53 2010 (4BF6FED5)
904c6000 904e3000   EraserUtilRebootDrv EraserUtilRebootDrv.sys Sat May 22 00:44:53 2010 (4BF6FED5)
904e3000 904ef000   discache discache.sys Tue Jul 14 02:24:04 2009 (4A5BC214)
904ef000 90507000   dfsc     dfsc.sys     Tue Jul 14 02:14:16 2009 (4A5BBFC8)
90507000 90515000   blbdrive blbdrive.sys Tue Jul 14 02:23:04 2009 (4A5BC1D8)
90515000 905c1000   BHDrvx86 BHDrvx86.sys Sat Aug 28 00:42:32 2010 (4C783148)
905c1000 905cd000   ATITool  ATITool.sys  Fri Nov 10 15:08:51 2006 (455479E3)
My System SpecsSystem Spec
.

Reply

 BSOD on startup




Thread Tools




Similar help and support threads
Thread Forum
BSOD during windows startup; can't safe mode; startup repair can't fix
Consistent BSOD during Windows startup for both normal mode and safe mode. BSOD problem started shortly after buggy installations of Microsoft Visual C++ 2005 x64, Microsoft .Net Framework 1.1, and AMD Catalyst Drivers 13.9; and turning off Microsoft .Net Framework 3.5.1. Startup Repair is...
BSOD Help and Support
Brief BSOD on Startup, Startup Recovery Hangs
I have Win 7 Home and in the last couple of days I have been trying to do a backup onto an external drive. The problem comes in when I attempt to start my laptop so that I can begin the backup process, the screen flickers a BSOD, says startup failed and do I want to run Startup Recovery. If I say...
BSOD Help and Support
BSOD on startup, unknown error, startup repair running too long
As the title suggests, my Acer Aspire has been running startup repair for over 20 hours following a BSOD yesterday. I'm not sure if it's worth the wait so maybe you all can shed some light. Yesterday I was stressfully trying to search for something (using Chrome) and the website I was on froze;...
BSOD Help and Support
BSOD on Startup - Startup Reapir not working
On Startup, after POST, I get this BSOD: STOP: c000021a {Fatal System Error} The verification of a knownDLL failed. system process terminated unexpectedly with a status of 0xc000012f (0x00360bf0 0x00000000). The system has shut down. Upon Reboot, I am advised to go to the startup repair....
BSOD Help and Support
BSOD at startup, cant repair startup
i had a bsod 3 days ago with no reason when its at Welcome screen and my startup items are not loaded at all(all drivers programs etc.). i tried to reboot and my pc gone wild. it cant even see welcome screen cuz of bsods. also i am having black screens when booting up. sometimes its just freezes...
BSOD Help and Support
BSOD on startup , error 0x000000f4 . startup takes half an hour
so everything was fine when my laptop started to become very slow and i used to get the BSOD very often so i decided to recover the system to the initial state . i did that and everything was fine , then i updated the windows 7 service pack 1 and finished the installation and rebooted my computer ,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:45.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App