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: Why do i keep getting BSOD's!


25 Mar 2012   #1

windows 7 home premium 64bit
 
 
Why do i keep getting BSOD's!

I built a computer a while ago, i keep getting blue screens. Can someone please tell me what is making my computer BSOD, ill add the dmp files.
Attachment 204272


My System SpecsSystem Spec
.

25 Mar 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\gusrawrr\BSOD FILES\032512-29328-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16917.amd64fre.win7_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3de70 Debug session time: Sun Mar 25 17:13:30.679 2012 (UTC - 6:00) System Uptime: 0 days 0:00:43.193 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 1097, 0, fffffa8009428888} GetPointerFromAddress: unable to read from fffff80002ea80e0 Probably caused by : ntkrnlmp.exe ( nt!ObpDeleteSymbolicLink+19 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 0000000000000007, Attempt to free pool which was already freed Arg2: 0000000000001097, (reserved) Arg3: 0000000000000000, Memory contents of the pool block Arg4: fffffa8009428888, Address of the block of pool being deallocated Debugging Details: ------------------ POOL_ADDRESS: fffffa8009428888 FREED_POOL_TAG: Even BUGCHECK_STR: 0xc2_7_Even CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: userinit.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002da360e to fffff80002c71540 STACK_TEXT: fffff880`082e3848 fffff800`02da360e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`00000000 : nt!KeBugCheckEx fffff880`082e3850 fffff800`02f06e4d : fffffa80`09428850 fffff800`02f6922d 00000000`00000000 fffff8a0`020da6a0 : nt!ExDeferredFreePool+0x11eb fffff880`082e3900 fffff800`02c76634 : fffffa80`093f2440 fffff8a0`020da6a0 fffffa80`6e657645 fffff8a0`0211af70 : nt!ObpDeleteSymbolicLink+0x19 fffff880`082e3930 fffff800`02f82ed4 : fffff8a0`020da6a0 00000000`00000000 fffffa80`09446430 00000000`00000000 : nt!ObfDereferenceObject+0xd4 fffff880`082e3990 fffff800`02f2a944 : 00000000`00000070 fffff8a0`020da6a0 fffff8a0`020e01c0 00000000`00000070 : nt!ObpCloseHandleTableEntry+0xc4 fffff880`082e3a20 fffff800`02f2a8c4 : 00000000`00000004 00000000`00000000 fffffa80`09369b30 fffff800`02f13511 : nt!ObpCloseHandleProcedure+0x30 fffff880`082e3a60 fffff800`02f29722 : fffff8a0`020e7701 00000000`00000001 fffffa80`09369b30 fffffa80`09369b30 : nt!ExSweepHandleTable+0x74 fffff880`082e3aa0 fffff800`02f524d8 : fffff8a0`020e77a0 00000000`00000000 00000000`00000000 000007ff`fffde000 : nt!ObKillProcess+0x62 fffff880`082e3ae0 fffff800`02f29e3f : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x878 fffff880`082e3ba0 fffff800`02c70793 : fffffa80`09369b30 fffff880`00000000 00000000`00113d30 fffffa80`09446430 : nt!NtTerminateProcess+0x25b fffff880`082e3c20 00000000`7786f97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0029fe08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7786f97a STACK_COMMAND: kb FOLLOWUP_IP: nt!ObpDeleteSymbolicLink+19 fffff800`02f06e4d 4883631000 and qword ptr [rbx+10h],0 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!ObpDeleteSymbolicLink+19 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec7a284 FAILURE_BUCKET_ID: X64_0xc2_7_Even_nt!ObpDeleteSymbolicLink+19 BUCKET_ID: X64_0xc2_7_Even_nt!ObpDeleteSymbolicLink+19 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\gusrawrr\BSOD FILES\032512-26254-02.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16917.amd64fre.win7_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e3de70 Debug session time: Sun Mar 25 17:12:13.904 2012 (UTC - 6:00) System Uptime: 0 days 0:01:00.418 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffffff8a001b3, 2, 0, fffff80002c614f3} Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+8b ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffffff8a001b3, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002c614f3, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea80e0 fffffffff8a001b3 CURRENT_IRQL: 2 FAULTING_IP: nt!MiResolveMappedFileFault+8b fffff800`02c614f3 4d8b11 mov r10,qword ptr [r9] CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: SearchIndexer. TRAP_FRAME: fffff88009b75610 -- (.trap 0xfffff88009b75610) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff88009b75c20 rbx=0000000000000000 rcx=0000000000000001 rdx=000007fefb280000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002c614f3 rsp=fffff88009b757a0 rbp=fffff88009b75800 r8=fffff8a001b3cec0 r9=fffffffff8a001b3 r10=fffff8a001b3ccc8 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac pe cy nt!MiResolveMappedFileFault+0x8b: fffff800`02c614f3 4d8b11 mov r10,qword ptr [r9] ds:030a:ffffffff`f8a001b3=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c70aa9 to fffff80002c71540 STACK_TEXT: fffff880`09b754c8 fffff800`02c70aa9 : 00000000`0000000a ffffffff`f8a001b3 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`09b754d0 fffff800`02c6f720 : 00000000`00000000 fffff8a0`01b3ccc8 fffffa80`06a53060 fffff880`09b75600 : nt!KiBugCheckDispatch+0x69 fffff880`09b75610 fffff800`02c614f3 : 00000000`00000000 fffffa80`0921e898 fffff880`09b757e0 00000000`00000038 : nt!KiPageFault+0x260 fffff880`09b757a0 fffff800`02c976dd : fffff8a0`01b3ccc8 f8a001b3`cec00400 fffff8a0`01b3cec0 00000000`00000000 : nt!MiResolveMappedFileFault+0x8b fffff880`09b75910 fffff800`02c8d20e : 00000000`00000000 000007fe`fb280000 fffff683`ff7d9400 fffffa80`09a373f8 : nt!MiResolveProtoPteFault+0x48d fffff880`09b759b0 fffff800`02c8b393 : fffff880`09b75c00 000007fe`fb280000 00000000`0001d000 fffff800`00000000 : nt!MiDispatchFault+0x1de fffff880`09b75ac0 fffff800`02c6f62e : 00000000`00000000 00000000`00000000 fffffa80`09aecb01 fffffa80`c0000034 : nt!MmAccessFault+0x343 fffff880`09b75c20 00000000`76ef6358 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`00a6b930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ef6358 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiResolveMappedFileFault+8b fffff800`02c614f3 4d8b11 mov r10,qword ptr [r9] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiResolveMappedFileFault+8b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ec7a284 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveMappedFileFault+8b BUCKET_ID: X64_0xA_nt!MiResolveMappedFileFault+8b Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\gusrawrr\BSOD FILES\032512-26208-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16917.amd64fre.win7_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c61000 PsLoadedModuleList = 0xfffff800`02e9de70 Debug session time: Sun Mar 25 17:10:38.699 2012 (UTC - 6:00) System Uptime: 0 days 0:01:09.603 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8000301b94a, fffff88003bf9070, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+36349 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8000301b94a, Address of the instruction which caused the bugcheck Arg3: fffff88003bf9070, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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! ?? ::NNGAKEGL::`string'+36349 fffff800`0301b94a 48894108 mov qword ptr [rcx+8],rax CONTEXT: fffff88003bf9070 -- (.cxr 0xfffff88003bf9070) rax=fffffa8008bb4a60 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000001 rsi=fffffa8008bb4910 rdi=fffffa8008bb4a18 rip=fffff8000301b94a rsp=fffff88003bf9a40 rbp=fffff88003bf9ca0 r8=0000000000000000 r9=0000000000000000 r10=fffffa8008bb4910 r11=fffff88003bf9b38 r12=0000000000000001 r13=fffffa8008bb5b60 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010296 nt! ?? ::NNGAKEGL::`string'+0x36349: fffff800`0301b94a 48894108 mov qword ptr [rcx+8],rax ds:002b:00000000`00000008=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: lsass.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002fde6c8 to fffff8000301b94a STACK_TEXT: fffff880`03bf9a40 fffff800`02fde6c8 : 00000000`00000000 00000000`00000001 fffff880`03bf9ca0 00000000`0059f770 : nt! ?? ::NNGAKEGL::`string'+0x36349 fffff880`03bf9aa0 fffff800`02fdea87 : fffffa80`08bb4910 00000000`0059f770 00000000`00000000 fffffa80`08abc801 : nt!AlpcpReceiveLegacyMessage+0x127 fffff880`03bf9b40 fffff800`02fdeafb : fffffa80`08bb5b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReplyWaitReceivePortEx+0x106 fffff880`03bf9be0 fffff800`02cd0793 : fffffa80`08bb5b60 fffffa80`08ef1600 fffff880`03bf9ca0 00000000`0026c660 : nt!NtReplyWaitReceivePort+0xf fffff880`03bf9c20 00000000`7782f76a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0059f548 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7782f76a FOLLOWUP_IP: nt! ?? ::NNGAKEGL::`string'+36349 fffff800`0301b94a 48894108 mov qword ptr [rcx+8],rax SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+36349 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec7a284 STACK_COMMAND: .cxr 0xfffff88003bf9070 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!_??_::NNGAKEGL::_string_+36349 BUCKET_ID: X64_0x3B_nt!_??_::NNGAKEGL::_string_+36349 Followup: MachineOwner ---------
  1. Most likely an underlying driver problem...
  2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
  3. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
Thanks to Dave76 for help understanding possible causes.


Code:
AODDriver2	fffff880`06ca9000	fffff880`06cda000	Wed Jun 15 02:38:35 2011 (4df86f8b)	00012df4		AODDriver2.sys
Remove AMD Overdrive, EasyTune6, or AMD Vision Engine Control Centre. These programs are known to overclock systems without the user's knowledge and cause crashes.


Start by checking hardware, RAM, and then drivers:
  • Monitor temperatures during the following tests.
    Use the following programs to monitor the temperatures.
  • 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 (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.

  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. In Windows 7:
    • Click the Start Menu
    • Type verifier in Search programs and files (do not hit enter)
    • Right click verifier and click Run as administrator
    • Put a tick in Create custom settings (for code developers) and click next
    • Put a tick in Select individual settings from a full list and click next
    • Set up the individual settings as in the image and click next
      Attachment 204305
    • Put a tick in Select driver names from a list
    • Put a tick next to all non-Microsoft drivers.
    • Click Finish.
    • Restart your computer.

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
    The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
My System SpecsSystem Spec
27 Mar 2012   #3

windows 7 home premium 64bit
 
 

Turned out to be the RAM. I have ran memtest for nearly 24hrs and has come up with over 13,000 errors. Attachment 204658
My System SpecsSystem Spec
.


27 Mar 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Glad you found the culprit. I actually saw your other thread: http://www.sevenforums.com/crashes-d...e-screens.html Let us know how things go if you RMA the RAM.
My System SpecsSystem Spec
Reply

 Why do i keep getting BSOD's!




Thread Tools



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 12:07 PM.
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