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 - Most likely RAM issue

05 Feb 2012   #11
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\Kingston\BSODDmpFiles\Sabrac\02052012dumps\020512-19047-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 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e8e670 Debug session time: Sun Feb 5 10:35:10.571 2012 (GMT-7) System Uptime: 0 days 0:01:07.210 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002cfafe8, fffff8800945dc70, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 3: 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: fffff80002cfafe8, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800945dc70, 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!MiInsertPageInLockedList+d8 fffff800`02cfafe8 48892cc2 mov qword ptr [rdx+rax*8],rbp CONTEXT: fffff8800945dc70 -- (.cxr 0xfffff8800945dc70) rax=0017ffff4017ffdc rbx=fffffa8000c69b10 rcx=0003ffffe003fffa rdx=fffffa8000000000 rsi=0000000000000003 rdi=fffff80002e37bb0 rip=fffff80002cfafe8 rsp=fffff8800945e650 rbp=00000000000008fb r8=0000000046f81963 r9=0000000000000004 r10=0000007c40018050 r11=0000007ffffffff8 r12=00000000000abf47 r13=0000000000000000 r14=fffffa8000bbe7e0 r15=fffff80002efb2a0 iopl=0 nv up ei pl nz ac pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010212 nt!MiInsertPageInLockedList+0xd8: fffff800`02cfafe8 48892cc2 mov qword ptr [rdx+rax*8],rbp ds:002b:00bffa7a`00bffee0=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x3B PROCESS_NAME: WerFault.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002cf88c7 to fffff80002cfafe8 STACK_TEXT: fffff880`0945e650 fffff800`02cf88c7 : fffffa80`00c69b10 00000000`00004718 fffff880`0945e760 00000000`00000000 : nt!MiInsertPageInLockedList+0xd8 fffff880`0945e680 fffff800`02cf7bb7 : fffff700`01080000 fffff680`00004718 fffffa80`074cfb30 fffffa80`04fb4410 : nt!MiDeletePteRun+0x44d fffff880`0945e830 fffff800`02cf9569 : 00000000`00000000 00000000`00cdffff fffff880`00000000 fffff880`00000000 : nt!MiDeleteVirtualAddresses+0x41f fffff880`0945e9f0 fffff800`02fdd221 : fffffa80`074de4b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`0945eb10 fffff800`02fdd623 : 00000000`00000000 00000000`008d0000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1 fffff880`0945ebd0 fffff800`02cc4ed3 : fffffa80`074d14b0 fffff880`0945eca0 fffffa80`074cfb30 00000000`008d0000 : nt!NtUnmapViewOfSection+0x5f fffff880`0945ec20 00000000`771115ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0029d918 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771115ba CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 2 errors : !nt (fffff80002cfaf4f-fffff80002cfaf77) fffff80002cfaf40 10 48 b8 ab aa aa aa aa aa aa 2a 48 f7 e9 48 *8a .H........*H..H. ... fffff80002cfaf70 48 83 05 c8 d0 17 00 *00 f0 48 83 05 ff 02 20 00 H........H.... . MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE STACK_COMMAND: .cxr 0xfffff8800945dc70 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption ---------
  2. Loading Dump File [F:\Kingston\BSODDmpFiles\Sabrac\02052012dumps\020512-21933-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 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e99670 Debug session time: Sun Feb 5 10:33:08.553 2012 (GMT-7) System Uptime: 0 days 1:48:50.566 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {5, fffffa800528f1a0, 10024396, fffffa8006561c48} Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver. Arg2: fffffa800528f1a0, Device extension pointer of the host controller Arg3: 0000000010024396, PCI Vendor,Product id for the controller Arg4: fffffa8006561c48, Pointer to Endpoint data structure Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff88003f8ef7e to fffff80002cd0c40 STACK_TEXT: fffff880`02ffda58 fffff880`03f8ef7e : 00000000`000000fe 00000000`00000005 fffffa80`0528f1a0 00000000`10024396 : nt!KeBugCheckEx fffff880`02ffda60 fffff880`11de6fac : 00000000`ced43180 fffffa80`052906a0 00000000`00000000 fffffa80`06561dc0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a fffff880`02ffdaa0 fffff880`11de6b73 : fffffa80`06561c48 fffffa80`05410100 fffffa80`06561dc0 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c fffff880`02ffdb30 fffff880`11debd91 : fffffa80`06561c48 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53 fffff880`02ffdb70 fffff880`03f62e8b : 00000000`00000002 fffffa80`0528f1a0 00000000`00000000 00000000`00000050 : usbehci!EHCI_PollEndpoint+0x41 fffff880`02ffdbb0 fffff880`03f679d1 : 00000000`00000050 00000000`00000004 fffffa80`06561a00 fffffa80`0528f050 : USBPORT!MPf_PollEndpoint+0x9b fffff880`02ffdbe0 fffff880`03f73077 : fffffa80`0528f1a0 00000000`00000050 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1 fffff880`02ffdc40 fffff880`03f63f89 : fffffa80`0528f050 00000000`00000000 fffffa80`0528fa02 fffffa80`0528fa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3 fffff880`02ffdca0 fffff800`02cdc0ac : fffff880`02fd5180 fffffa80`0528fa18 fffffa80`0528fa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9 fffff880`02ffdcd0 fffff800`02cc896a : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`03f63db0 : nt!KiRetireDpcList+0x1bc fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: usbehci!EHCI_sMode_PollEndpointSlot+6c fffff880`11de6fac 4533c9 xor r9d,r9d SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbehci IMAGE_NAME: usbehci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c00 FAILURE_BUCKET_ID: X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+6c BUCKET_ID: X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+6c Followup: MachineOwner ---------
  3. Loading Dump File [F:\Kingston\BSODDmpFiles\Sabrac\02052012dumps\020412-21262-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 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e9c670 Debug session time: Sat Feb 4 19:17:55.100 2012 (GMT-7) System Uptime: 0 days 10:57:29.113 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5100, fffff6fc500191c0, 2, df70000129cb7943} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+af37 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005100, The subtype of the bugcheck. Arg2: fffff6fc500191c0 Arg3: 0000000000000002 Arg4: df70000129cb7943 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5100 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WerFault.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d2d957 to fffff80002cd3c40 STACK_TEXT: fffff880`09047ea8 fffff800`02d2d957 : 00000000`0000001a 00000000`00005100 fffff6fc`500191c0 00000000`00000002 : nt!KeBugCheckEx fffff880`09047eb0 fffff800`02cf6a4c : 00000000`00000005 fffff880`09048000 fffff8a0`03235000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0xaf37 fffff880`09047fc0 fffff800`02dfff86 : 00000000`00005000 fffffa80`03960000 00000000`80000001 00000000`00000000 : nt!MiAllocatePagedPoolPages+0x4cc fffff880`090480e0 fffff800`02cf4760 : 00000000`00005000 fffffa80`03960000 00000000`80000001 00000000`00000000 : nt!MiAllocatePoolPages+0x906 fffff880`09048220 fffff800`02e0290e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00005000 : nt!ExpAllocateBigPool+0xb0 fffff880`09048310 fffff800`02ceb124 : 00000000`00000000 fffffa80`06b548f0 fffffa80`0aa44b60 00000000`000007ff : nt!ExAllocatePoolWithTag+0x82e fffff880`09048400 fffff800`02cb7f1c : 00000000`00000000 00000000`000009fc 00000000`00000000 fffff880`09048500 : nt!MiAddViewsForSection+0x1d4 fffff880`09048490 fffff800`02f2db21 : fffffa80`00000001 00000000`00000000 00000000`00000000 00000000`000007ff : nt!MiAddViewsForSectionWithPfn+0x98 fffff880`09048500 fffff800`02f2ddac : 00000000`00000000 fffffa80`04691720 00000000`00000000 00000000`00000004 : nt!MiPfPrepareReadList+0xe1 fffff880`090485c0 fffff800`0312fbfc : 00000000`00000002 00000000`0000002c fffffa80`04691610 00000000`0000002c : nt!MmPrefetchPages+0x6c fffff880`09048620 fffff800`0312fe1d : fffff880`09048740 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x43c fffff880`09048710 fffff800`0313025f : 000000a3`c5027f0d fffffa80`046b9060 fffff8a0`038c1000 00000000`00000000 : nt!PfSnPrefetchScenario+0x16d fffff880`09048980 fffff800`0302f2df : 00000000`00000000 00000000`37549b7e fffffa80`042766c0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f fffff880`09048a50 fffff800`02fc1fb8 : fffffa80`0aa44b60 fffffa80`042766c0 00000000`16050800 00000000`7efde000 : nt! ?? ::NNGAKEGL::`string'+0x513d0 fffff880`09048a80 fffff800`02cc5715 : fffff880`02f63180 00000000`00000000 fffff800`02fc1e70 fffffa80`0aa44b60 : nt!PspUserThreadStartup+0x148 fffff880`09048ae0 fffff800`02cc5697 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16 fffff880`09048c20 00000000`76f1c500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn 00000000`0027f5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f1c500 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+af37 fffff800`02d2d957 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+af37 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+af37 BUCKET_ID: X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+af37 Followup: MachineOwner ---------
  4. Loading Dump File [F:\Kingston\BSODDmpFiles\Sabrac\02052012dumps\020312-18798-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 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02ea4670 Debug session time: Fri Feb 3 18:42:41.530 2012 (GMT-7) System Uptime: 0 days 0:04:25.544 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c000001d, fffff80002cdee66, fffff8800b1e3f20, 0} Probably caused by : Npfs.SYS ( Npfs!NpFsdRead+9d ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c000001d, Exception code that caused the bugcheck Arg2: fffff80002cdee66, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800b1e3f20, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: nt!IopfCompleteRequest+186 fffff800`02cdee66 0fbae00b bt eax,0Bh CONTEXT: fffff8800b1e3f20 -- (.cxr 0xfffff8800b1e3f20) rax=0000000000062900 rbx=0000000000000000 rcx=fffffa8003ce2060 rdx=fffff8800b1e4a02 rsi=0000000000000000 rdi=fffffa80067adee0 rip=fffff80002cdee66 rsp=fffff8800b1e4900 rbp=00000000a000000c r8=0000000000000001 r9=fffff8a00b0f8940 r10=0000000000001000 r11=fffff8800b1e49e8 r12=00000000a0000003 r13=0000000000000000 r14=0000000000000000 r15=0000000000000002 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!IopfCompleteRequest+0x186: fffff800`02cdee66 0fbae00b bt eax,0Bh Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff880011e6b01 to fffff80002cdee66 STACK_TEXT: fffff880`0b1e4900 fffff880`011e6b01 : fffffa80`067adfb0 fffffa80`03c37502 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x186 fffff880`0b1e49f0 fffff800`02fe421b : 00000000`00000000 fffff800`02ceda61 00000000`05ad7364 fffffa80`03c37620 : Npfs!NpFsdRead+0x9d fffff880`0b1e4a50 fffff800`02fc5b63 : fffffa80`03c375d0 fffffa80`03c375d0 fffffa80`03c375d0 fffff880`009ea180 : nt!IopSynchronousServiceTail+0xfb fffff880`0b1e4ac0 fffff800`02cdaed3 : 00000000`00000401 00000000`00000000 00000000`00000001 00000000`05ad7304 : nt!NtReadFile+0x631 fffff880`0b1e4bb0 00000000`74e72e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0342ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74e72e09 FOLLOWUP_IP: Npfs!NpFsdRead+9d fffff880`011e6b01 8bc3 mov eax,ebx SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: Npfs!NpFsdRead+9d FOLLOWUP_NAME: MachineOwner MODULE_NAME: Npfs IMAGE_NAME: Npfs.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc114 STACK_COMMAND: .cxr 0xfffff8800b1e3f20 ; kb FAILURE_BUCKET_ID: X64_0x3B_Npfs!NpFsdRead+9d BUCKET_ID: X64_0x3B_Npfs!NpFsdRead+9d Followup: MachineOwner ---------
  1. Possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers... Hardware... (possibly your USB wireless device?)
  2. Since cleaning the USB drivers did not resolve the problem, this is likely due to a device you are using through your USB ports. I do notice a wireless USB device, and these are known to be finicky; usasma has a number of posts speaking of this problem and his recommendations. He recommends installing a wireless PCI card instead of a USB wireless adapter to provide better power and stability for a wireless adapter. Also, make sure the wireless device is supported for Windows 7.
  3. Possible causes are Memory problems... Drivers... Windows error reporting accesses the internet, so the driver causing this fault may be your wireless adapter driver.
  4. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver...



Do the following steps to diagnose possible problems.
  • 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).


  • Replace your wireless device or update/re-install to the latest drivers. Your current drivers may be corrupt and need a re-install or you may not be running with the best drivers.

Also, make sure when replacing RAM that you practice safe electrostatic discharge (ESD) procedures. You may also find Avoid Static Damage to Your PC | PCWorld interesting further reading as to why RAM problems can occur. It basically says that ~400 Volts of electrostatic discharge (ESD) can ruin RAM, but you will not feel the discharge until it reaches ~1400-3500 Volts (that link says 3500-4000 Volts, but it varies based on the climate and how dry it is). When RAM receives a shock that we cannot feel, it can work for a while, and then slowly fail over time until symptoms become noticeable. That is one of the many reasons why so many users end up on these forums wondering why their systems are suddenly not working.

So for future reference, make sure you practice good electrostatic discharge (ESD) habbits and keep yourself grounded when touching PC components.

For ESD Safety, follow these steps:
  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.


My System SpecsSystem Spec
.
05 Feb 2012   #12
Sabrac

Windows 7 Ultimate 64-Bit
 
 

Removed my Wireless USB device all together.
I have this Xbox 360 "wireless" Ethernet adapter that I used way back when I had no USB one.
Since its not USB and its connected by Ethernet, I hope this should help solve my problem.
I was getting BSODs like crazy tonight and as soon as I removed the USB driver, they stopped, but its only been 30 minutes or so since.
I'll post here again if I should find anything else.
And results of a 7 hour Memtest had zero errors.

Also if I were to get a PCI wireless internet card, could you maybe suggest something?
Was looking at this, but I don't know much about these things.
My System SpecsSystem Spec
06 Feb 2012   #13
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Did you run memtest or memtest86+?
They are different programs.

Are the CPU temps posted previously with the system at idle?
If they are, then your CPU temps are high.
Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Post a snip.

If you have any more crashes, post the below info on your RAM.
Post your CPUZ SPD tabs, one for each brand of RAM you have installed.
Mixing RAM brands, frequencies, timings and voltages can cause system instability.
My System SpecsSystem Spec
.

06 Feb 2012   #14
Sabrac

Windows 7 Ultimate 64-Bit
 
 

I'm using Memtest86+ version 4.20, I believe.
I was using one of the my old RAM sticks with the new ones, so that might have been causing some issues last night.
I removed it and the only RAM left in there are the 2 new sticks I just bought.
I downloaded the Coretemp program and ran it about 15 minutes after turning on my computer.
Although after opening WoW, it jumped up to the 45C I was seeing in the other program.
So to clarify, my idle temp is about 35-38 and my load temp is 45-47C.
My System SpecsSystem Spec
06 Feb 2012   #15
Sabrac

Windows 7 Ultimate 64-Bit
 
 

I ran SFC /scannow to maybe fix my Windows files, but I got the "found corrupt files, but unable to fix them".
Posting the CBS.txt file.
My System SpecsSystem Spec
06 Feb 2012   #16
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Your core temps are a little high (depending on ambient temp) but in the acceptable range.

SFC may have failed if you are having RAM problems.

Leave only the new RAM cards installed until we are sure the system is stable.
Better to reduce the variables as much as possible.

Post your CPUZ 'Memory' and 'SPD' tabs, one SPD tab for each brand or card of RAM you have installed.

Run memtest86+ on the new RAM cards, minimum of 7 full passes, best to run overnight.
You can stop the test if you get any errors.

If that passes then run HCI Mem Test, this memory test runs from Windows and will also test the windows settings.
Run it overnight also.
My System SpecsSystem Spec
07 Feb 2012   #17
Sabrac

Windows 7 Ultimate 64-Bit
 
 

I ran Memtest86+ over the weekend for 7 hours. I didn't notice how many passes it went through, but there were no errors at all.
Right now, I only have the new RAM I bought recently in my system.
Ever since I removed my USB wireless device, things seem better, but my computer could stay "fixed" for a month or 2, then another issue will arise.
I ran MSE last night on a full scan and found no viruses, so I'm safe in that regard.
I'll post the CPUZ for the RAM and post if I experience any new problems.
My System SpecsSystem Spec
07 Feb 2012   #18
Sabrac

Windows 7 Ultimate 64-Bit
 
 

Got a BSOD a few minutes after my last post.
And another a few hours later while watching Youtube videos named (Dump 2).
My System SpecsSystem Spec
08 Feb 2012   #19
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Your crashes are pointing to the RAM, to rule this out you will need to run memtest86+ several times, electronics can be fickle and have intermittent faults which are very hard to find, and RAM is no exception.
I have seen RAM tests pass several times and then fail, adjust settings or replace the RAM and problem was solved.
Can you run memtest86+ on your RAM a couple more times, start it before you go to bed and let it run overnight.
Also, you can run HCI Mem Test, while you are using your computer, try not to run any RAM intensive programs like games or videos.

Your RAM should be installed in Slots A1 and B1, the blue slots, is this how you have them?

Can you always upload the complete Blue Screen of Death (BSOD) Posting Instructions files, these have information that will help us to analyze your crashes.
Please attach them to your next post.


Both crashes are STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED, a very common Stop code and doesn't pinpoint anything.
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: fffff800031365bb, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000080000, Parameter 1 of the exception

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!PfSnGetPrefetchInstructions+1db
fffff800`031365bb 49895d00        mov     qword ptr [r13],rbx

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000080000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0e100
 0000000000080000 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006ebe710 -- (.trap 0xfffff88006ebe710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff88006ebe998
rdx=fffff8a00436e184 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031365bb rsp=fffff88006ebe8a0 rbp=fffffa8001f9d610
 r8=0000000000000004  r9=0000000000000000 r10=fffff8a00436a000
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!PfSnGetPrefetchInstructions+0x1db:
fffff800`031365bb 49895d00        mov     qword ptr [r13],rbx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d27588 to fffff80002cdbc40

STACK_TEXT:  
fffff880`06ebde88 fffff800`02d27588 : 00000000`0000001e ffffffff`c0000005 fffff800`031365bb 00000000`00000001 : nt!KeBugCheckEx
fffff880`06ebde90 fffff800`02cdb2c2 : fffff880`06ebe668 fffff8a0`0436a000 fffff880`06ebe710 00000000`000043ac : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`06ebe530 fffff800`02cd9e3a : 00000000`00000001 00000000`00080000 00000000`00000000 fffff8a0`0436a000 : nt!KiExceptionDispatch+0xc2
fffff880`06ebe710 fffff800`031365bb : fffff8a0`0436a000 00000000`00000000 fffff880`06ebe998 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`06ebe8a0 fffff800`031381f9 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!PfSnGetPrefetchInstructions+0x1db
fffff880`06ebe980 fffff800`030372df : 00000000`00000000 00000000`e301a942 fffffa80`05225900 00000000`00000000 : nt!PfSnBeginAppLaunch+0x2f9
fffff880`06ebea50 fffff800`02fc9fb8 : fffffa80`021e0510 fffffa80`05225900 00000000`14050800 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x513d0
fffff880`06ebea80 fffff800`02ccd715 : fffff880`02f63180 00000000`00000000 fffff800`02fc9e70 fffffa80`021e0510 : nt!PspUserThreadStartup+0x148
fffff880`06ebeae0 fffff800`02ccd697 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`06ebec20 00000000`7779c500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0017fdf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7779c500


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PfSnGetPrefetchInstructions+1db
fffff800`031365bb 49895d00        mov     qword ptr [r13],rbx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!PfSnGetPrefetchInstructions+1db

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!PfSnGetPrefetchInstructions+1db

BUCKET_ID:  X64_0x1E_c0000005_nt!PfSnGetPrefetchInstructions+1db

Followup: MachineOwner
---------
I need to look at your Event Logs, can you post the BSOD files requested?

D/L and run Western Digital Lifeguard – Quick Test and Extended Test.

Then run memtest86+ again tonight.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


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

FAULTING_IP: 
+3063386630323032
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efe100
 0000000000000000 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  winamp.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880039da7d0 -- (.trap 0xfffff880039da7d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880039da588
rdx=fffff900c02182b8 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff880039da968 rbp=fffff96000227319
 r8=0000000000000000  r9=000000000000101d r10=0000000000000000
r11=fffff880039da638 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d17588 to fffff80002ccbc40

STACK_TEXT:  
fffff880`039d9f48 fffff800`02d17588 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`039d9f50 fffff800`02ccb2c2 : fffff880`039da728 fffff880`039daca0 fffff880`039da7d0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`039da5f0 fffff800`02cc9e3a : 00000000`00000008 00000000`00000000 fffff900`c1ab2800 fffff880`039daca0 : nt!KiExceptionDispatch+0xc2
fffff880`039da7d0 00000000`00000000 : ffffffff`e9040df3 00000000`00000000 fffff880`039daca0 00000000`00000021 : nt!KiPageFault+0x23a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4977d
fffff800`02d17588 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4977d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4977d

BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4977d

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

Old or problematic drivers:
Code:
AtiPcie.sys  Tue May 05 23:00:22 2009  - ATI PCIE Driver for ATI PCIE chipset
Go to your Motherboard support site and download all updated drivers and install them.


Code:
GEARAspiWDM.sys Mon May 18 20:17:04 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes
Uninstall iTunes for testing purposes, it is known to cause crashes in Windows 7 and the driver is out of date.


Code:
mcdbus.sys   Tue Feb 24 18:34:07 2009 - MagicISO SCSI Host Controller driver
Uninstall MagicISO and D/L a newer version and install.


Code:
Rt64win7.sys Thu Feb 26 17:04:13 2009 - Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
You can find a newer driver on your motherboard support website.


Code:
Unloaded modules: cpuz135_x64
Timestamp: unavailable
Uninstall or delete CPUZ 1.35 64bit and D/L the new version CPUZ 1.59
My System SpecsSystem Spec
12 Feb 2012   #20
Sabrac

Windows 7 Ultimate 64-Bit
 
 

I updated the drivers and ran MemTest86+ overnight.
Since then I haven't had an issue with BSODs and MemTest86 showed zero errors for 8 passes.

But now my computer will freeze(hang) at some points. Either soon after the computer is turned on from being off for a while or when I open World of Warcraft.
It hangs on whatever it was showing before hand and the mouse and keyboard are unresponsive.
The only way to restart it is to manually turn off my system and turn it back on.
Though when I get back in, my MB splash page says that the Date/Time are not set and when I get into Windows, I must sync the Date/Time with the internet time every single time I restart from these hangs.
The reset of the time sounds like my CMOS battery, but I don't know what's causing the hangs since they give no minidump.
My System SpecsSystem Spec
Reply

 BSOD - Most likely RAM issue




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD randomly (no specific trigger) Commonly an IRQL issue on BSOD
Hi, My computer has been unstable for quite some time and after memory tests, changing graphics cards, many driver variations and a couple of fresh OS installs a while ago it is still not stable. The difficulty is that it doesn't seem to be triggered by anything specific so it makes debugging...
BSOD Help and Support
BSOD & Non-BSOD Crashes, Display Driver Issue?
I'm running: Windows 7 Home Premium, 64-bit, OEM, never reinstalled HP model #p6654y, approx. 1 year old, no major problems until now I've attached the BSOD Dump and System File Collection, but Windows refuses to produce a System Health Report because I have to run in safe mode. If you have...
BSOD Help and Support
Need help with a BSOD issue.
I recently built a new pc but I seem to be randomly getting BSOD errors infrequently every day or so. I have a full retail version of Windows 7 Ultimate 64 bit os. All my specs are in my profile. Thanks for any and all help!
BSOD Help and Support
Another BSOD issue... please help.
This is the first pc I ever built, has been BSOD from day one. Any help is greatly appreciated.
BSOD Help and Support
BSOD Issue.. HELP
This pops up when I play a video file. It doesn't happen all the time, so i wouldn't say whenever. Still, it only pops up when i play video files. I am not overclocking, I thought that might be the case so I set it back to factory clocks. Any help?... I hate this BSOD.
BSOD Help and Support
BSOD issue
Hey everybody. I'm having an identical problem as this guy: http://www.sevenforums.com/crashes-debugging/54063-windows-7-bsod-issue-dmp-attached.html. It happens mostly after coming out of standby, just like him. Mine's a Toshiba L355D-S7825. I've been having BSODs since I bought the thing,...
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 15:37.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App