New
#1
Win7 Ultimate Retail, BSOD
Hi all,
I received my copy of Win7 Ultimate on Wednesday after Amazon brought forward the delivery date owing to a postal strike that is currently underway in the UK. I proceeded with a clean install (x64 version), installed all my apps and was surprised to see, on my third day of using the OS, a BSOD. I was only running ITunes (my first song was playing in iTunes on this installation) and Outlook. I don't think anything else notable was running. I also have Norton 360 as my file scanner.
Below are my hardware details and underneath that you will find a WinDbg output. Have submitted the crash info to Microsoft via the 'Action' Centre, no fixes yet as obviously it is early days.
Not expecting a solution but grateful for any comments you might have.
Thanks all,
Martin
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
OS Manufacturer Microsoft Corporation
System Manufacturer Dell Inc
System Model Dimension E521
System Type x64-based PC
Processor AMD Athlon(tm) 64 X2 Dual Core Processor 5600+, 2800 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Dell Inc 1.1.11, 02/08/2007
SMBIOS Version 2.4
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume3
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7600.16385"
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 4.00 GB
Available Physical Memory 1.83 GB
Total Virtual Memory 8.00 GB
Available Virtual Memory 5.55 GB
Page File Space 4.00 GB
Page File C:\pagefile.sys
--
!analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002b9853b, The address that the exception occurred at
Arg3: fffff88003124898, Exception Record Address
Arg4: fffff880031240f0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!IopDeleteFile+24b
fffff800`02b9853b 488b09 mov rcx,qword ptr [rcx]
EXCEPTION_RECORD: fffff88003124898 -- (.exr 0xfffff88003124898)
ExceptionAddress: fffff80002b9853b (nt!IopDeleteFile+0x000000000000024b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000001300000000
Attempt to read from address 0000001300000000
CONTEXT: fffff880031240f0 -- (.cxr 0xfffff880031240f0)
rax=fffff8a00f57ddf0 rbx=fffffa800a0b3070 rcx=0000001300000000
rdx=fffff8a00f57ddf1 rsi=fffffa80039db080 rdi=fffffa8004502030
rip=fffff80002b9853b rsp=fffff88003124ad0 rbp=0000000000000001
r8=fffff8a00f57ddf0 r9=0000000000000110 r10=fffff800029ff900
r11=fffff8a010bfcca0 r12=fffffa80044f5d10 r13=fffff8a010c70600
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!IopDeleteFile+0x24b:
fffff800`02b9853b 488b09 mov rcx,qword ptr [rcx] ds:002b:00000013`00000000=????????????????
Resetting default scope
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: 0000000000000000
EXCEPTION_PARAMETER2: 0000001300000000
READ_ADDRESS: 0000001300000000
FOLLOWUP_IP:
nt!IopDeleteFile+24b
fffff800`02b9853b 488b09 mov rcx,qword ptr [rcx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8000288a0b4 to fffff80002b9853b
STACK_TEXT:
fffff880`03124ad0 fffff800`0288a0b4 : 00000000`00000000 00000000`00000000 fffffa80`039db080 00000000`00000000 : nt!IopDeleteFile+0x24b
fffff880`03124b60 fffff800`02b72f39 : 00000000`00000000 00000000`0008c081 fffffa80`0a0b3210 fffffa80`0008c081 : nt!ObfDereferenceObject+0xd4
fffff880`03124bc0 fffff800`029aaf6b : fffffa80`0a0b3218 00000000`00000001 00000000`00000000 0f4f072f`00000631 : nt!MiSegmentDelete+0xa1
fffff880`03124c00 fffff800`029ab5dd : 00000000`00000000 00000000`00000080 fffffa80`039cd040 0fc71f0f`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`03124cc0 fffff800`02b28166 : f2f0f0fc`b4f0f036 8f0c0f29`0e0f2f1f 70d8f4f2`6050f0f4 8f1b050f`0f0d0f0f : nt!MiDereferenceSegmentThread+0x10d
fffff880`03124d40 fffff800`02863486 : fffff800`029fde80 fffffa80`039e4510 fffff800`02a0bc40 0e6d2e0e`0f0f2d8f : nt!PspSystemThreadStartup+0x5a
fffff880`03124d80 00000000`00000000 : fffff880`03125000 fffff880`0311f000 fffff880`03124550 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IopDeleteFile+24b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
STACK_COMMAND: .cxr 0xfffff880031240f0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!IopDeleteFile+24b
BUCKET_ID: X64_0x7E_nt!IopDeleteFile+24b
Followup: MachineOwner
---------