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: Bosd while loading windows

07 Sep 2011   #1

Windows 7
 
 
Bosd while loading windows

i got this bosd while loading windows 7, 32 bit

i7 920
evga x58 sli le
g-skill ram 3gb
hd5870
seasonic m12 620w
few tb hdd by hitachi and wd


My System SpecsSystem Spec
.

07 Sep 2011   #2

Windows 7 Ultimate x64
 
 

Please run Memtest86 to rule out bad ram. Also please follow both tutorials below:

http://www.sevenforums.com/crashes-d...tructions.html

RAM - Test with Memtest86+

Code:
Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8341e000 PsLoadedModuleList = 0x83566810
Debug session time: Wed Sep  7 07:38:09.714 2011 (UTC - 6:00)
System Uptime: 0 days 0:00:13.776
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 83640441, 8cc4f648, 8cc4f220}

Probably caused by : ntkrpamp.exe ( nt!RtlEqualUnicodeString+2f )

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

6: 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: 83640441, The address that the exception occurred at
Arg3: 8cc4f648, Exception Record Address
Arg4: 8cc4f220, Context Record Address

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


OVERLAPPED_MODULE: Address regions for 'Msfs' and 'cdrom.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!RtlEqualUnicodeString+2f
83640441 3b37            cmp     esi,dword ptr [edi]

EXCEPTION_RECORD:  8cc4f648 -- (.exr 0xffffffff8cc4f648)
ExceptionAddress: 83640441 (nt!RtlEqualUnicodeString+0x0000002f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000ed40
Attempt to read from address 0000ed40

CONTEXT:  8cc4f220 -- (.cxr 0xffffffff8cc4f220)
eax=0000000e ebx=8b9d7a3e ecx=8b9d7a30 edx=00000004 esi=00540041 edi=0000ed40
eip=83640441 esp=8cc4f710 ebp=8cc4f71c iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210206
nt!RtlEqualUnicodeString+0x2f:
83640441 3b37            cmp     esi,dword ptr [edi]  ds:0023:0000ed40=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0000ed40

READ_ADDRESS: GetPointerFromAddress: unable to read from 83586718
Unable to read MiSystemVaType memory at 83566160
 0000ed40 

FOLLOWUP_IP: 
nt!RtlEqualUnicodeString+2f
83640441 3b37            cmp     esi,dword ptr [edi]

BUGCHECK_STR:  0x7E

LOCK_ADDRESS:  83583f60 -- (!locks 83583f60)

Resource @ nt!PiEngineLock (0x83583f60)    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  : 0x83583f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8364029d to 83640441

STACK_TEXT:  
8cc4f71c 8364029d 0000ed40 8b9d7a3e 00000201 nt!RtlEqualUnicodeString+0x2f
8cc4f744 836400e4 0186ebf0 8cc4f790 00000201 nt!ObpLookupDirectoryUsingHash+0xa0
8cc4f768 8363f04e 8b86ebf0 8cc4f790 00000201 nt!ObpLookupDirectoryEntry+0x80
8cc4f7cc 8366524d 00000000 8cc4f820 00000240 nt!ObpLookupObjectName+0x371
8cc4f82c 835c9401 8cc4f858 85a5deb0 00000000 nt!ObOpenObjectByName+0x159
8cc4f878 835c8e06 8ebb148c 00000010 8cc4fa38 nt!IopReferenceDriverObjectByName+0x46
8cc4f918 8360de4e 8ebb14a0 00000001 8ebb148c nt!PipCallDriverAddDeviceQueryRoutine+0x16a
8cc4f950 836160a2 00000001 8cc4fa1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8cc4f9bc 835c6108 40000000 80000198 8cc4fa38 nt!RtlQueryRegistryValues+0x31d
8cc4fa98 835c5876 85a892a8 8cc4fcc8 00000000 nt!PipCallDriverAddDevice+0x383
8cc4fc94 835a9a2a 85a95518 86c39de8 8cc4fcc8 nt!PipProcessDevNodeTree+0x15d
8cc4fcd4 83431f99 86c39de8 83581e80 85a61d48 nt!PiProcessStartSystemDevices+0x6d
8cc4fd00 8348bf2b 00000000 00000000 85a61d48 nt!PnpDeviceActionWorker+0x241
8cc4fd50 8362c66d 00000001 afe2a5bf 00000000 nt!ExpWorkerThread+0x10d
8cc4fd90 834de0d9 8348be1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!RtlEqualUnicodeString+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

STACK_COMMAND:  .cxr 0xffffffff8cc4f220 ; kb

FAILURE_BUCKET_ID:  0x7E_nt!RtlEqualUnicodeString+2f

BUCKET_ID:  0x7E_nt!RtlEqualUnicodeString+2f

Followup: MachineOwner
---------
My System SpecsSystem Spec
07 Sep 2011   #3

Windows 7 Ultimate x64 SP1
 
 

Hello Mano,

In addition to seth500 post, if you didn't find any bad RAM, try bellow suggestion:

1. Uninstall Daemon/Alcohol software and remove its driver with this tools (choose Uninstall)
http://www.duplexsecure.com/download...t-v178-x86.exe

2. Uninstall ATITool (Overclocking utility for ATI/nVidia cards) because unstable overclock can lead crashing.

3. Update Acronis True Image Software to latest version.

Then we'll see how it goes.


Log
Code:
Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8341e000 PsLoadedModuleList = 0x83566810
Debug session time: Wed Sep  7 05:38:09.714 2011 (GMT-8)
System Uptime: 0 days 0:00:13.776
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 83640441, 8cc4f648, 8cc4f220}

Probably caused by : ntkrpamp.exe ( nt!RtlEqualUnicodeString+2f )

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

6: 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: 83640441, The address that the exception occurred at
Arg3: 8cc4f648, Exception Record Address
Arg4: 8cc4f220, Context Record Address

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


OVERLAPPED_MODULE: Address regions for 'Msfs' and 'cdrom.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!RtlEqualUnicodeString+2f
83640441 3b37            cmp     esi,dword ptr [edi]

EXCEPTION_RECORD:  8cc4f648 -- (.exr 0xffffffff8cc4f648)
ExceptionAddress: 83640441 (nt!RtlEqualUnicodeString+0x0000002f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000ed40
Attempt to read from address 0000ed40

CONTEXT:  8cc4f220 -- (.cxr 0xffffffff8cc4f220)
eax=0000000e ebx=8b9d7a3e ecx=8b9d7a30 edx=00000004 esi=00540041 edi=0000ed40
eip=83640441 esp=8cc4f710 ebp=8cc4f71c iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210206
nt!RtlEqualUnicodeString+0x2f:
83640441 3b37            cmp     esi,dword ptr [edi]  ds:0023:0000ed40=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0000ed40

READ_ADDRESS: GetPointerFromAddress: unable to read from 83586718
Unable to read MiSystemVaType memory at 83566160
 0000ed40 

FOLLOWUP_IP: 
nt!RtlEqualUnicodeString+2f
83640441 3b37            cmp     esi,dword ptr [edi]

BUGCHECK_STR:  0x7E

LOCK_ADDRESS:  83583f60 -- (!locks 83583f60)

Resource @ nt!PiEngineLock (0x83583f60)    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  : 0x83583f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8364029d to 83640441

STACK_TEXT:  
8cc4f71c 8364029d 0000ed40 8b9d7a3e 00000201 nt!RtlEqualUnicodeString+0x2f
8cc4f744 836400e4 0186ebf0 8cc4f790 00000201 nt!ObpLookupDirectoryUsingHash+0xa0
8cc4f768 8363f04e 8b86ebf0 8cc4f790 00000201 nt!ObpLookupDirectoryEntry+0x80
8cc4f7cc 8366524d 00000000 8cc4f820 00000240 nt!ObpLookupObjectName+0x371
8cc4f82c 835c9401 8cc4f858 85a5deb0 00000000 nt!ObOpenObjectByName+0x159
8cc4f878 835c8e06 8ebb148c 00000010 8cc4fa38 nt!IopReferenceDriverObjectByName+0x46
8cc4f918 8360de4e 8ebb14a0 00000001 8ebb148c nt!PipCallDriverAddDeviceQueryRoutine+0x16a
8cc4f950 836160a2 00000001 8cc4fa1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8cc4f9bc 835c6108 40000000 80000198 8cc4fa38 nt!RtlQueryRegistryValues+0x31d
8cc4fa98 835c5876 85a892a8 8cc4fcc8 00000000 nt!PipCallDriverAddDevice+0x383
8cc4fc94 835a9a2a 85a95518 86c39de8 8cc4fcc8 nt!PipProcessDevNodeTree+0x15d
8cc4fcd4 83431f99 86c39de8 83581e80 85a61d48 nt!PiProcessStartSystemDevices+0x6d
8cc4fd00 8348bf2b 00000000 00000000 85a61d48 nt!PnpDeviceActionWorker+0x241
8cc4fd50 8362c66d 00000001 afe2a5bf 00000000 nt!ExpWorkerThread+0x10d
8cc4fd90 834de0d9 8348be1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!RtlEqualUnicodeString+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

STACK_COMMAND:  .cxr 0xffffffff8cc4f220 ; kb

FAILURE_BUCKET_ID:  0x7E_nt!RtlEqualUnicodeString+2f

BUCKET_ID:  0x7E_nt!RtlEqualUnicodeString+2f

Followup: MachineOwner
---------
kd> lmtsmn
start    end        module name
83b9e000 83be6000   ACPI     ACPI.sys     Mon Jul 13 15:11:11 2009 (4A5BBF0F)
9064c000 906a6000   afd      afd.sys      Mon Jul 13 15:12:34 2009 (4A5BBF62)
8a8d7000 8a8e0000   amdxata  amdxata.sys  Tue May 19 09:57:35 2009 (4A12F30F)
908a7000 908bb480   archlp   archlp.sys   Tue Jan 12 00:07:05 2010 (4B4C2DA9)
8a8ab000 8a8b4000   atapi    atapi.sys    Mon Jul 13 15:11:15 2009 (4A5BBF13)
8a8b4000 8a8d7000   ataport  ataport.SYS  Mon Jul 13 15:11:18 2009 (4A5BBF16)
9089b000 908a7000   ATITool  ATITool.sys  Fri Nov 10 05:08:51 2006 (455479E3)
8aa17000 8aa1e000   Beep     Beep.SYS     Mon Jul 13 15:45:00 2009 (4A5BC6FC)
9088d000 9089b000   blbdrive blbdrive.sys Mon Jul 13 15:23:04 2009 (4A5BC1D8)
83aa9000 83ab1000   BOOTVID  BOOTVID.dll  Mon Jul 13 17:04:34 2009 (4A5BD9A2)
83af3000 83b9e000   CI       CI.dll       Mon Jul 13 17:09:28 2009 (4A5BDAC8)
8afcb000 8aff0000   CLASSPNP CLASSPNP.SYS Mon Jul 13 15:11:20 2009 (4A5BBF18)
83ab1000 83af3000   CLFS     CLFS.SYS     Mon Jul 13 15:11:10 2009 (4A5BBF0E)
8ab97000 8abf4000   cng      cng.sys      Mon Jul 13 15:32:55 2009 (4A5BC427)
8aff0000 8affd000   crashdmp crashdmp.sys Mon Jul 13 15:45:50 2009 (4A5BC72E)
90811000 90875000   csc      csc.sys      Mon Jul 13 15:15:08 2009 (4A5BBFFC)
90875000 9088d000   dfsc     dfsc.sys     Mon Jul 13 15:14:16 2009 (4A5BBFC8)
907e4000 907f0000   discache discache.sys Mon Jul 13 15:24:04 2009 (4A5BC214)
8afba000 8afcb000   disk     disk.sys     Mon Jul 13 15:11:28 2009 (4A5BBF20)
8adf5000 8adfe000   dump_atapi dump_atapi.sys Mon Jul 13 15:11:15 2009 (4A5BBF13)
8ae00000 8ae0b000   dump_ataport dump_ataport.sys Mon Jul 13 15:11:16 2009 (4A5BBF14)
8ac00000 8ac11000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 15:12:47 2009 (4A5BBF6F)
8a914000 8a925000   fileinfo fileinfo.sys Mon Jul 13 15:21:51 2009 (4A5BC18F)
8a8e0000 8a914000   fltmgr   fltmgr.sys   Mon Jul 13 15:11:13 2009 (4A5BBF11)
8aa0e000 8aa17000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 15:11:14 2009 (4A5BBF12)
8af88000 8afba000   fvevol   fvevol.sys   Mon Jul 13 15:13:01 2009 (4A5BBF7D)
8adc4000 8adf5000   fwpkclnt fwpkclnt.sys Mon Jul 13 15:12:03 2009 (4A5BBF43)
8382e000 83865000   hal      halmacpi.dll Mon Jul 13 15:11:03 2009 (4A5BBF07)
8af80000 8af88000   hwpolicy hwpolicy.sys Mon Jul 13 15:11:01 2009 (4A5BBF05)
80bc8000 80bd0000   kdcom    kdcom.dll    Mon Jul 13 17:08:58 2009 (4A5BDAAA)
8ab84000 8ab97000   ksecdd   ksecdd.sys   Mon Jul 13 15:11:56 2009 (4A5BBF3C)
8ac56000 8ac7b000   ksecpkg  ksecpkg.sys  Mon Jul 13 15:34:00 2009 (4A5BC468)
83a20000 83a98000   mcupdate mcupdate.dll Mon Jul 13 17:06:41 2009 (4A5BDA21)
8a895000 8a8ab000   mountmgr mountmgr.sys Mon Jul 13 15:11:27 2009 (4A5BBF1F)
8a9ec000 8a9f7000   Msfs     Msfs.SYS     Mon Jul 13 15:11:26 2009 (4A5BBF1E)
8a7e5000 8a7ed000   msisadrv msisadrv.sys Mon Jul 13 15:11:09 2009 (4A5BBF0D)
8ab59000 8ab84000   msrpc    msrpc.sys    Mon Jul 13 15:11:59 2009 (4A5BBF3F)
907da000 907e4000   mssmbios mssmbios.sys Mon Jul 13 15:19:25 2009 (4A5BC0FD)
8af70000 8af80000   mup      mup.sys      Mon Jul 13 15:14:14 2009 (4A5BBFC6)
8a925000 8a9dc000   ndis     ndis.sys     Mon Jul 13 15:12:24 2009 (4A5BBF58)
90717000 90725000   netbios  netbios.sys  Mon Jul 13 15:53:54 2009 (4A5BC912)
906a6000 906d8000   netbt    netbt.sys    Mon Jul 13 15:12:18 2009 (4A5BBF52)
8ac18000 8ac56000   NETIO    NETIO.SYS    Mon Jul 13 15:12:35 2009 (4A5BBF63)
83a10000 83a1e000   Npfs     Npfs.SYS     Mon Jul 13 15:11:31 2009 (4A5BBF23)
907d0000 907da000   nsiproxy nsiproxy.sys Mon Jul 13 15:12:08 2009 (4A5BBF48)
8341e000 8382e000   nt       ntkrpamp.exe Mon Jul 13 15:15:19 2009 (4A5BC007)
8aa2a000 8ab59000   Ntfs     Ntfs.sys     Mon Jul 13 15:12:05 2009 (4A5BBF45)
8ac11000 8ac18000   Null     Null.SYS     Mon Jul 13 15:11:12 2009 (4A5BBF10)
906e8000 90707000   pacer    pacer.sys    Mon Jul 13 15:53:58 2009 (4A5BC916)
83be6000 83bf7000   partmgr  partmgr.sys  Mon Jul 13 15:11:35 2009 (4A5BBF27)
8a600000 8a62a000   pci      pci.sys      Mon Jul 13 15:11:16 2009 (4A5BBF14)
8a880000 8a887000   pciide   pciide.sys   Mon Jul 13 15:11:19 2009 (4A5BBF17)
8a887000 8a895000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 15:11:15 2009 (4A5BBF13)
8aa00000 8aa0e000   pcw      pcw.sys      Mon Jul 13 15:11:10 2009 (4A5BBF0E)
83a98000 83aa9000   PSHED    PSHED.dll    Mon Jul 13 17:09:36 2009 (4A5BDAD0)
9078f000 907d0000   rdbss    rdbss.sys    Mon Jul 13 15:14:26 2009 (4A5BBFD2)
8abf4000 8abfc000   RDPCDD   RDPCDD.sys   Mon Jul 13 16:01:40 2009 (4A5BCAE4)
8a9dc000 8a9e4000   rdpencdd rdpencdd.sys Mon Jul 13 16:01:39 2009 (4A5BCAE3)
8a9e4000 8a9ec000   rdprefmp rdprefmp.sys Mon Jul 13 16:01:41 2009 (4A5BCAE5)
8af43000 8af70000   rdyboost rdyboost.sys Mon Jul 13 15:22:02 2009 (4A5BC19A)
8a7bf000 8a7e5000   SCSIPORT SCSIPORT.SYS Mon Jul 13 15:45:55 2009 (4A5BC733)
8af24000 8af42b60   snapman  snapman.sys  Wed Jun 10 00:47:50 2009 (4A2F7336)
8af1c000 8af24000   spldr    spldr.sys    Mon May 11 08:13:47 2009 (4A084EBB)
8a6b5000 8a7b6000   spya     spya.sys     Sun Mar 22 22:38:33 2009 (49C72E69)
8ac7b000 8adc4000   tcpip    tcpip.sys    Mon Jul 13 15:13:18 2009 (4A5BBF8E)
90641000 9064c000   TDI      TDI.SYS      Mon Jul 13 15:12:12 2009 (4A5BBF4C)
8aec3000 8af1b540   tdrpman  tdrpman.sys  Mon Nov 12 05:35:28 2007 (473856A0)
9062a000 90641000   tdx      tdx.sys      Mon Jul 13 15:12:10 2009 (4A5BBF4A)
9077f000 9078f000   termdd   termdd.sys   Mon Jul 13 16:01:35 2009 (4A5BCADF)
8ae10000 8ae7a380   timntr   timntr.sys   Wed Aug 29 04:13:12 2007 (46D562D8)
908bc000 908dd000   tunnel   tunnel.sys   Mon Jul 13 15:54:03 2009 (4A5BC91B)
8a7ed000 8a7f8000   vdrvroot vdrvroot.sys Mon Jul 13 15:46:19 2009 (4A5BC74B)
8aa1e000 8aa2a000   vga      vga.sys      Mon Jul 13 15:25:50 2009 (4A5BC27E)
8a800000 8a821000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 15:25:49 2009 (4A5BC27D)
8ae7b000 8ae83380   vmstorfl vmstorfl.sys Mon Jul 13 15:28:44 2009 (4A5BC32C)
83a00000 83a10000   volmgr   volmgr.sys   Mon Jul 13 15:11:25 2009 (4A5BBF1D)
8a835000 8a880000   volmgrx  volmgrx.sys  Mon Jul 13 15:11:41 2009 (4A5BBF2D)
8ae84000 8aec3000   volsnap  volsnap.sys  Mon Jul 13 15:11:34 2009 (4A5BBF26)
90707000 90717000   vpcnfltr vpcnfltr.sys Wed Jul 22 13:53:18 2009 (4A678A4E)
90738000 9077e100   vpcvmm   vpcvmm.sys   Wed Jul 22 13:53:21 2009 (4A678A51)
90725000 90738000   wanarp   wanarp.sys   Mon Jul 13 15:55:02 2009 (4A5BC956)
8a821000 8a82e000   watchdog watchdog.sys Mon Jul 13 15:24:10 2009 (4A5BC21A)
8a636000 8a6a7000   Wdf01000 Wdf01000.sys Mon Jul 13 15:11:36 2009 (4A5BBF28)
8a6a7000 8a6b5000   WDFLDR   WDFLDR.SYS   Mon Jul 13 15:11:25 2009 (4A5BBF1D)
906e1000 906e8000   wfplwf   wfplwf.sys   Mon Jul 13 15:53:51 2009 (4A5BC90F)
8a7b6000 8a7bf000   WMILIB   WMILIB.SYS   Mon Jul 13 15:11:22 2009 (4A5BBF1A)
906d8000 906e1000   ws2ifsl  ws2ifsl.sys  Mon Jul 13 15:55:01 2009 (4A5BC955)

Unloaded modules:
8a9dc000 8a9fb000   cdrom.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
My System SpecsSystem Spec
.


07 Sep 2011   #4

Windows 7
 
 

hi, i attached windows_NT6_BSOD_jcgriff2 folder & the PERFMON HTML below


My System SpecsSystem Spec
07 Sep 2011   #5

Windows 7
 
 

hi, is there a way to keep my alcohol software? Because something i need to mount disk image for ahem stuffs
My System SpecsSystem Spec
07 Sep 2011   #6

Windows 7 Ultimate x64
 
 

My System SpecsSystem Spec
Reply

 Bosd while loading windows




Thread Tools



Similar help and support threads for2: Bosd while loading windows
Thread Forum
Solved BOSD Win 7 x64 . Random While Gaming , or right on Windows Startup . BSOD Help and Support
Windows not Loading after update, hangs on "Loading operating system." General Discussion
Bosd while loading windows BSOD Help and Support
BOSD Installing Windows Media Center Media Center
Solved Windows 7 BOSD twice. Please help BSOD Help and Support
hal.dll BOSD on new windows 7 BSOD Help and Support
Clean Windows 7 Install BOSD 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 08:15 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33