Getting BSOD on Windows 7

[paplu]

Since last couple of weeks I am getting BSOD almost every single day. I have attached the .dmp file. Will you please help me to find out what is going on?

Thanks,

 

[writhziden]

Welcome to SevenForums.

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\paplu\010112-30328-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8281e000 PsLoadedModuleList = 0x8295d570
Debug session time: Sun Jan  1 15:33:14.910 2012 (UTC - 7:00)
System Uptime: 0 days 0:29:22.832
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8287cb00, 8e0d5884, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+b )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 8287cb00, The address that the exception occurred at
Arg3: 8e0d5884, Trap Frame
Arg4: 00000000

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!ObFastReferenceObject+b
8287cb00 8b0f            mov     ecx,dword ptr [edi]

TRAP_FRAME:  8e0d5884 -- (.trap 0xffffffff8e0d5884)
ErrCode = 00000000
eax=00037999 ebx=00037975 ecx=00000000 edx=8410c310 esi=82949c80 edi=00037999
eip=8287cb00 esp=8e0d58f8 ebp=8e0d5904 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!ObFastReferenceObject+0xb:
8287cb00 8b0f            mov     ecx,dword ptr [edi]  ds:0023:00037999=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  vsserv.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8288ee68 to 8287cb00

STACK_TEXT:  
8e0d5904 8288ee68 00037999 a9cf2133 8463ad48 nt!ObFastReferenceObject+0xb
8e0d59a4 828b261c 9ec4a000 2f1f735c 00000000 nt!MmCopyToCachedPage+0x3db
8e0d5a38 828b7483 84628890 2f1f735c 8e0d5a88 nt!CcMapAndCopyInToCache+0x1f0
8e0d5a94 878bdc24 846015c0 8e0d5b9c 0011771c nt!CcCopyWrite+0x1d9
8e0d5bc0 87778fec 846015c0 8e0d5ac0 0011771c Ntfs!NtfsCopyWriteA+0x248
8e0d5bf4 877791bb 00000004 00000000 85a095f4 fltmgr!FltpPerformFastIoCall+0x22e
8e0d5c20 8778bdcf 000d5c44 846015c0 8778bc6c fltmgr!FltpPassThroughFastIo+0x7d
8e0d5c64 82a37b5e 846015c0 8e0d5cac 0011771c fltmgr!FltpFastIoWrite+0x163
8e0d5d08 8285379a 850c7ed8 00000000 00000000 nt!NtWriteFile+0x342
8e0d5d08 776f64f4 850c7ed8 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02435e04 00000000 00000000 00000000 00000000 0x776f64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObFastReferenceObject+b
8287cb00 8b0f            mov     ecx,dword ptr [edi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObFastReferenceObject+b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbffc

FAILURE_BUCKET_ID:  0x8E_nt!ObFastReferenceObject+b

BUCKET_ID:  0x8E_nt!ObFastReferenceObject+b

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

See Post #4 in http://www.sevenforums.com/crashes-debugging/205298-ntoskrnl-exe-0x0000001e-bsod.html#post1721371
Give props to JMH if this helps.

Edit: Also, your BitDefender was the application that caused the fault. Recommend uninstalling using the tool in How to uninstall BitDefender (do not use add/remove programs as the first step suggests) and install Microsoft Security Essentials in its place to run with Windows Firewall.

Edit2: Update to SP1

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
​

Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

The file you provided only contained one dmp file. While I was able to provide a suggestion for it, more information would allow us to better assist you. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to allow us to better assist you.

 

[paplu]

Thanks for your response...I also thught that bitdefender might be the issue so I have reinstalled Windows 7 Ultimate and it crashed again. This time there was no bit defender installed. I have uploaded the dump file.
I am going to run the verifier and see if this makes any difference.

Regards,

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\paplu\010212-18625-01\010212-18625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0x82819000 PsLoadedModuleList = 0x82958570
Debug session time: Mon Jan  2 04:42:45.671 2012 (UTC - 7:00)
System Uptime: 0 days 0:21:56.609
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00000411, The subtype of the bugcheck.
Arg2: c0267764
Arg3: 31a59882
Arg4: c0a67765

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

TRAP_FRAME:  8a46fbc4 -- (.trap 0xffffffff8a46fbc4)
ErrCode = 00000000
eax=8a46fc90 ebx=99dd9000 ecx=00000000 edx=85a64758 esi=00000001 edi=82944f50
eip=82a24de8 esp=8a46fc38 ebp=8a46fc5c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!PfpLogPageAccess+0x23e:
82a24de8 8b03            mov     eax,dword ptr [ebx]  ds:0023:99dd9000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828beac4 to 828ea460

STACK_TEXT:  
8a46fa54 828beac4 0000001a 00000411 c0267764 nt!KeBugCheckEx+0x1e
8a46fa88 82887450 c0267764 8a46fad4 c0267764 nt!MiLockTransitionLeafPage+0xdf
8a46fabc 8287aeb1 00000000 99dd9000 c0267764 nt!MiResolveTransitionFault+0x21
8a46fb34 82878d53 99dd9000 00000000 00000000 nt!MiDispatchFault+0x545
8a46fbac 82851948 00000000 99dd9000 00000000 nt!MmAccessFault+0x128f
8a46fbac 82a24de8 00000000 99dd9000 00000000 nt!KiTrap0E+0xdc
8a46fc5c 82a6f068 85a64758 8a46fc90 000001fe nt!PfpLogPageAccess+0x23e
8a46fcc0 82a3429a 00000000 959b9d48 00000000 nt!PfpFlushBuffers+0x1a1
8a46fd50 82a00ee8 82944f80 a319701d 00000000 nt!PfTLoggingWorker+0xaa
8a46fd90 828a2089 82a341ea 82944f80 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiLockTransitionLeafPage+df
828beac4 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiLockTransitionLeafPage+df

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea76f0d

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_411_VRF_nt!MiLockTransitionLeafPage+df

BUCKET_ID:  0x1a_411_VRF_nt!MiLockTransitionLeafPage+df

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

The blue screen crash (verifier enabled) points to memory corruption. If you are overclocking anything, stop by resetting the BIOS to defaults and disabling overclocking software in Windows 7. Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.

 

[writhziden]

Have you had any Verifier related crashes to determine driver incompatibilities with your system?