Solved BSOD - Most likely RAM issue

Sabrac · Jan 28, 2012

Hiya everyone,

I've been having BSOD issues since I've had this computer. RAM has always seems to hate me with a passion.
A few months ago, I took lower end RAM from an old computer and put it in my system.
Sadly, that didn't do any better. BSODs all day long.
I also put the original RAM that was in my computer into the other older computer which my family uses.
In their computer, both sets of RAM work completely fine.
Since it was lower end RAM and still getting BSODs, I decided to put my 4GB of Hynix back into my system.
From some miracle, it was working with NO BSODs for like 3 months.
Only a few days ago when my Nvidia drivers started crashing did I realize my RAM is fighting me again.
I did a Memtest and got errors right off the bat.
I'm almost certain its my RAM, but I'll throw in the regular BSOD info and computer things just to be sure.

If it is my RAM, I've been browsing the internet trying to find cheap DDR2 RAM that will work in my Asus M4A785-M, but all the DDR2 is more expensive than the DDR3 and its looking like I need to spend $40 on 2GB of RAM(when I have 4GB installed of Hynix) for a computer that I've already put $1200+ into fixing EACH and EVERY part, whether it be from upgrade or it breaking.
Should the problem show itself to be my RAM, can anyone suggest my cheapest, but most reliable alternative.

I'll also add that I play World of Warcraft extensively on certain days of the week.
Usually I'll have World of Warcraft, Skype, and Winamp open and sometimes I'll have Google Chrome open with those with Facebook open, so it would just have to support doing those.

Thank you.

Sabrac · Jan 28, 2012

Including this picture of the stats of the 2 pieces of RAM that are currently in my system.

Sabrac · Jan 29, 2012

Throwing in a few more dump files from the last 2 days.

linnemeyerhere · Jan 29, 2012

Sabrac,
If I hadn't just sent all my DDR2 ram to another friend with an older mobo I would have happily sent you them. I understand your frustrations with these BSOD's. Have you checked if the mobo has the most recent bios version? It's a mystery why DDR2 is so much more than DDR3 other than when it was manufactured prices/cost were higher. It's a bummer because prices for DDR3 has never been lower as you are aware of. Many here are stellar with BSOD issues but I believe you're on the right path and if it leads to new ram sticks then make sure you check ASUS's site and get approved ram modules that they recommend to be extra safe.

Sabrac · Jan 29, 2012

Thanks for the input.
I went on Asus' website and looked at the QVL.
Found 2GB of some G.Skill RAM for within my budget.
The only thing I'd liek to know is if this is definitely a RAM issue.
I've had 3 BSODs today and when I run Memtest, I get no errors now.

Sabrac · Jan 30, 2012

Bumping this up.
I ran Memtest for another 2 hours because I don't have the time to be able to run it overnight right now and got no errors.
My video driver started failing again just before I started the test and I got a BSOD during my initial start up this morning, so I only have this one minidump.

linnemeyerhere · Jan 30, 2012

Sabrac,
I can understand your concerns in wanting to have some greater assurance that this is in fact a ram issue. The truth is there are much more qualified people here that can delve into the BSOD issue. It does sound like a ram issue but I'm not willing to wager money on it! Let me see if we can get some others input.

writhziden · Jan 30, 2012

Code:

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\013012-32011-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c14000 PsLoadedModuleList = 0xfffff800`02e59670
Debug session time: Mon Jan 30 07:38:51.879 2012 (GMT-7)
System Uptime: 0 days 0:07:35.846
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff80000b9ca18 -- (.exr 0xfffff80000b9ca18)
ExceptionAddress: fffff8000322d4f9 (hal!HalpKInterruptHeap+0x00000000000004f9)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9cac0 -- (.trap 0xfffff80000b9cac0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000001df00 rbx=0000000000000000 rcx=fffffa8003a51f20
rdx=fffffa8003a4d5a8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000322d4f9 rsp=fffff80000b9cc58 rbp=fffff8000321d460
 r8=0000000000000000  r9=000000003a4bcf49 r10=000000000001cbbe
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
hal!HalpKInterruptHeap+0x4f9:
fffff800`0322d4f9 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c885fe to fffff80002c90c10

STACK_TEXT:  
fffff800`00b9baf8 fffff800`02c885fe : 00000000`00000000 00000000`00000000 fffff800`00b9c270 fffff800`02cbc830 : nt!KeBugCheck
fffff800`00b9bb00 fffff800`02cbc4fd : fffff800`02e9a488 fffff800`02dd8c8c fffff800`02c14000 fffff800`00b9ca18 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9bb30 fffff800`02cbb2d5 : fffff800`02ddb0fc fffff800`00b9bba8 fffff800`00b9ca18 fffff800`02c14000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9bb60 fffff800`02ccc361 : fffff800`00b9ca18 fffff800`00b9c270 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff800`00b9c240 fffff800`02c902c2 : fffff800`00b9ca18 00000000`00000000 fffff800`00b9cac0 fffff800`02e06e80 : nt!KiDispatchException+0x135
fffff800`00b9c8e0 fffff800`02c8ebca : 00000000`00000001 fffff800`03207895 fffff800`0322d460 fffff800`00b9cb80 : nt!KiExceptionDispatch+0xc2
fffff800`00b9cac0 fffff800`0322d4f9 : 00000000`00000000 00000000`0001df00 fffff880`043667f2 00000000`00000010 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9cc58 00000000`00000000 : 00000000`0001df00 fffff880`043667f2 00000000`00000010 00000000`00000246 : hal!HalpKInterruptHeap+0x4f9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02c885fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------
[*]
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012812-21325-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c65000 PsLoadedModuleList = 0xfffff800`02eaa670
Debug session time: Sat Jan 28 21:39:43.249 2012 (GMT-7)
System Uptime: 0 days 1:17:47.825
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa80051f61a0, 10024397, fffffa80040e7e68}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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: fffffa80051f61a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: fffffa80040e7e68, Pointer to Endpoint data structure

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ce1c40

STACK_TEXT:  
fffff880`009b0d18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  ZEROED_STACK

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

[*]
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012812-20186-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c15000 PsLoadedModuleList = 0xfffff800`02e5a670
Debug session time: Sat Jan 28 09:57:48.984 2012 (GMT-7)
System Uptime: 0 days 0:16:09.950
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88004b00000, 8, fffff88004b00000, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4611f )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88004b00000, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff88004b00000, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec4100
 fffff88004b00000 

FAULTING_IP: 
+0
fffff880`04b00000 ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002e14520 -- (.trap 0xfffff88002e14520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800579b000 rbx=0000000000000000 rcx=000000000001467d
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b00000 rsp=fffff88002e146b0 rbp=0000000000000080
 r8=fffff78000000000  r9=0000000000000000 r10=fffffa8003a12400
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff880`04b00000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c3d9fc to fffff80002c91c40

STACK_TEXT:  
fffff880`02e143b8 fffff800`02c3d9fc : 00000000`00000050 fffff880`04b00000 00000000`00000008 fffff880`02e14520 : nt!KeBugCheckEx
fffff880`02e143c0 fffff800`02c8fd6e : 00000000`00000008 fffff880`04b00000 fffff880`02e14c00 fffffa80`0606db60 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`02e14520 fffff880`04b00000 : fffffa80`0579b000 01ccdddd`f7161463 fffff880`02e146f8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`02e146b0 fffffa80`0579b000 : 01ccdddd`f7161463 fffff880`02e146f8 00000000`00000000 00000000`00000000 : 0xfffff880`04b00000
fffff880`02e146b8 01ccdddd`f7161463 : fffff880`02e146f8 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0579b000
fffff880`02e146c0 fffff880`02e146f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1ccdddd`f7161463
fffff880`02e146c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`02e146f8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4611f
fffff800`02c3d9fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4611f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+4611f

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+4611f

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

[*]
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012812-21918-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c0b000 PsLoadedModuleList = 0xfffff800`02e50670
Debug session time: Sat Jan 28 09:38:13.043 2012 (GMT-7)
System Uptime: 0 days 0:00:31.009
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002c99640, 0, ffffffffffffffff}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff80002c99640, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, 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!ObFastReferenceObject+10
fffff800`02c99640 4c8b01          mov     r8,qword ptr [rcx]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eba100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  nvvsvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cd3588 to fffff80002c87c40

STACK_TEXT:  
fffff880`03fd9e48 fffff800`02cd3588 : 00000000`0000001e ffffffff`c0000005 fffff800`02c99640 00000000`00000000 : nt!KeBugCheckEx
fffff880`03fd9e50 fffff800`02c872c2 : fffff880`03fda628 00000000`00000564 fffff880`03fda6d0 fffffa80`04587398 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`03fda4f0 fffff800`02c85bca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03fda6d0 fffff800`02c99640 : fffff683`ff7efc00 fffffa80`06223ec8 00000000`79402025 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`03fda860 fffff800`02cf2a98 : 00000000`000007c6 00000000`00000564 fffff700`01080000 00000000`00000000 : nt!ObFastReferenceObject+0x10
fffff880`03fda890 fffff800`02ca653f : 7c600000`79402025 00000000`79402121 fffffa80`00000001 20206553`02c8cf32 : nt! ?? ::FNODOBFM::`string'+0x2a15e
fffff880`03fda920 fffff800`02ca5053 : 00000000`000a39cd 000007fe`fdf8072c fffff683`ff7efc00 fffffa80`06223ec8 : nt!MiResolveProtoPteFault+0x1cf
fffff880`03fda9b0 fffff800`02c94f19 : 00000000`00000000 000007fe`fdf8072c 00000000`000000ff 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`03fdaac0 fffff800`02c85d6e : 00000000`00000008 000007fe`fdf8072c 00000000`0033b701 00000000`00398c98 : nt!MmAccessFault+0x359
fffff880`03fdac20 000007fe`fdf8072c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0119ee50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdf8072c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObFastReferenceObject+10
fffff800`02c99640 4c8b01          mov     r8,qword ptr [rcx]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!ObFastReferenceObject+10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_nt!ObFastReferenceObject+10

BUCKET_ID:  X64_0x1E_nt!ObFastReferenceObject+10

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

[*]
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012712-35864-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c5e000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Fri Jan 27 17:04:30.461 2012 (GMT-7)
System Uptime: 0 days 3:26:47.427
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80010aa900, ffff, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80010aa900
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d4a150 to fffff80002cdac40

STACK_TEXT:  
fffff880`038d5768 fffff800`02d4a150 : 00000000`0000001a 00000000`00041790 fffffa80`010aa900 00000000`0000ffff : nt!KeBugCheckEx
fffff880`038d5770 fffff800`02cc80ff : fffffa80`00000000 00000000`04373fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`038d5930 fffff800`02cd9ed3 : ffffffff`ffffffff fffff8a0`08b08d78 fffff8a0`08b08da0 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`038d5a30 fffff800`02cd6470 : fffff880`11dcf4b2 fffff8a0`0efb2390 fffffa80`06528060 fffffa80`06538db0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`038d5bc8 fffff880`11dcf4b2 : fffff8a0`0efb2390 fffffa80`06528060 fffffa80`06538db0 fffff8a0`08b08d70 : nt!KiServiceLinkage
fffff880`038d5bd0 fffff880`11dbaac3 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000001 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`038d5c00 fffff880`11db5153 : 00000000`00000000 fffff8a0`0efb2390 fffff8a0`0efb2390 00000000`00000006 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x7b
fffff880`038d5cb0 fffff880`11d9baa7 : fffff8a0`098e9820 fffff8a0`01cf65e0 fffff880`038d5e20 00000000`00000020 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x483
fffff880`038d5d90 fffff880`11ce7469 : 00000000`00000000 fffff880`038d6260 00000000`00000000 fffff8a0`0ea060a0 : dxgmms1!VidMmOpenAllocation+0xeb
fffff880`038d5de0 fffff880`11ce0610 : fffff880`038d6048 fffff8a0`02262a40 fffff880`038d6220 fffff880`038d6220 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x291
fffff880`038d5e70 fffff880`11ce22ef : fffff8a0`01cff000 fffff880`038d64d0 00000000`00000000 fffff8a0`01cff000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8
fffff880`038d6470 fffff880`11ce89e0 : 00000000`00009000 fffff900`c00c079c 00000000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateStandardAllocation+0x367
fffff880`038d65d0 fffff960`0063682d : fffff900`c00c0020 00000000`00000000 fffff880`038d6cd0 00000000`00000000 : dxgkrnl!DxgkCddEnable+0x904
fffff880`038d6920 fffff960`00635ce1 : ffffffff`00000004 ffffffff`fffd7476 00000000`00000002 fffffa80`00000000 : cdd!CreateAndEnableDevice+0x1e1
fffff880`038d69b0 fffff800`02f75fee : 00000000`045c2d49 fffffa80`06638b60 00000000`00000080 fffffa80`06528060 : cdd!PresentWorkerThread+0x975
fffff880`038d6d40 fffff800`02ccc5e6 : fffff880`02fd5180 fffffa80`06638b60 fffff880`02fdffc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`038d6d80 00000000`00000000 : fffff880`038d7000 fffff880`038d1000 fffff880`038d5140 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`11dcf4b2 488b0e          mov     rcx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

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

[*]
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012412-22339-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c66000 PsLoadedModuleList = 0xfffff800`02eab670
Debug session time: Tue Jan 24 20:09:37.095 2012 (GMT-7)
System Uptime: 0 days 4:56:35.061
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa80052af1a0, 10024397, fffffa80041286c8}

Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+5d )

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: fffffa80052af1a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: fffffa80041286c8, 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 fffff8801102df7e to fffff80002ce2c40

STACK_TEXT:  
fffff880`02ffdae8 fffff880`1102df7e : 00000000`000000fe 00000000`00000005 fffffa80`052af1a0 00000000`10024397 : nt!KeBugCheckEx
fffff880`02ffdaf0 fffff880`11da5ed9 : 00000000`cf440700 00000000`00000000 fffffa80`052af1a0 fffffa80`041286c8 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`02ffdb30 fffff880`11da8744 : fffffa80`041286c8 fffffa80`04128480 fffffa80`052af1a0 00000000`ffffff02 : usbohci!OHCI_PollIsoEndpoint+0x5d
fffff880`02ffdb80 fffff880`11001e8b : 00000000`00000002 fffffa80`04128480 fffffa80`052af1a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x4c
fffff880`02ffdbb0 fffff880`110069d1 : 00000000`00000070 00000000`00000004 fffffa80`04128480 fffffa80`052af050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`02ffdbe0 fffff880`11012077 : fffffa80`052af1a0 00000000`00000070 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`02ffdc40 fffff880`11002f89 : fffffa80`052af050 00000000`00000000 fffffa80`052afa02 fffffa80`052afa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`02ffdca0 fffff800`02cee0ac : fffff880`02fd5180 fffffa80`052afa18 fffffa80`052afa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffdcd0 fffff800`02cda96a : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`11002db0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbohci!OHCI_PollIsoEndpoint+5d
fffff880`11da5ed9 8bd3            mov     edx,ebx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbohci!OHCI_PollIsoEndpoint+5d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbohci

IMAGE_NAME:  usbohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0bff

FAILURE_BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollIsoEndpoint+5d

BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollIsoEndpoint+5d

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

[*]
Loading Dump File [K:\BSODDmpFiles\Sabrac\Windows_NT6_BSOD_jcgriff2\012412-17004-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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`02c04000 PsLoadedModuleList = 0xfffff800`02e49670
Debug session time: Tue Jan 24 15:12:06.192 2012 (GMT-7)
System Uptime: 0 days 0:02:01.174
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff88004c00000, 80000001270f0963, fffff88003e06520, 2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45d8c )

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

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff88004c00000, Virtual address for the attempted execute.
Arg2: 80000001270f0963, PTE contents.
Arg3: fffff88003e06520, (reserved)
Arg4: 0000000000000002, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003e06520 -- (.trap 0xfffff88003e06520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800567b000 rbx=0000000000000000 rcx=0000000000000953
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004c00000 rsp=fffff88003e066b0 rbp=0000000000000080
 r8=fffff78000000000  r9=0000000000000000 r10=fffffa8003a8fb00
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
monitor!WPP_SF_ <PERF> (monitor+0x0):
fffff880`04c00000 4d5a            pop     r10
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c2c6c4 to fffff80002c80c40

STACK_TEXT:  
fffff880`03e063b8 fffff800`02c2c6c4 : 00000000`000000fc fffff880`04c00000 80000001`270f0963 fffff880`03e06520 : nt!KeBugCheckEx
fffff880`03e063c0 fffff800`02c7ed6e : 00000000`00000008 fffff880`04c00000 fffff880`03e06c00 fffffa80`05fbcb60 : nt! ?? ::FNODOBFM::`string'+0x45d8c
fffff880`03e06520 fffff880`04c00000 : fffffa80`0567b000 01ccdae5`35334421 fffff880`03e066f8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03e066b0 fffffa80`0567b000 : 01ccdae5`35334421 fffff880`03e066f8 00000000`00000000 00000000`00000000 : monitor!WPP_SF_ <PERF> (monitor+0x0)
fffff880`03e066b8 01ccdae5`35334421 : fffff880`03e066f8 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0567b000
fffff880`03e066c0 fffff880`03e066f8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1ccdae5`35334421
fffff880`03e066c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`03e066f8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+45d8c
fffff800`02c2c6c4 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+45d8c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+45d8c

BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+45d8c

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


[/list]

Possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.
USB driver related. Possibly due to a USB device plugged in that is conflicting/incompatible with Windows 7 or that has drivers that are conflicting/incompatible with Windows 7.
Possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...
Probably caused by Kaspersky.
This was related to DirectX or your graphics card. Other possible causes are Memory problems... Drivers...
Another USB driver related crash.
This one was likely due to either your monitor or your graphics card.

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the hardware tests you can run concurrently as they will not increase stability, but do not run them with Driver Verifier enabled). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you are overclocking any hardware, please stop.
Proceed with the steps for http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html
Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts
Alternatively:
1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
  - Right click the adapter
  - Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  - Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts
Uninstall your monitor driver using the steps above for opening device manager. Open Monitors, right click on your monitor, click Uninstall (put a check in the box to delete driver software for this device if the box exists), click OK, restart your computer, and let Windows install the appropriate software or install the software yourself from the manufacturer of the monitor.
Download and install HWiNFO64 Download to check hardware temperatures by running in sensor-only mode.
Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
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. Run Driver Verifier

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 http://www.sevenforums.com/tutorials/700-system-restore.html 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.

If the above steps do not resolve the problem, disable Verifier, and uninstall Kaspersky using the Removal tool for Kaspersky Lab products and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.

Dave76 · Jan 31, 2012

Good post writhziden.

After following the excellent suggestions given above, can you post the CPUZ CPU, Mainboard and Memory tabs so we can take a look?

Sabrac · Feb 5, 2012

Did all that and also bought myself 2GB of the G.Skill I mentioned.
Since then I noticed a considerable difference.
But still get BSODs at random points of the day.
Got these 4 since I put the RAM in.
BlueScreenView seems to point at USB, but since I did that USB bug fix thing, shouldn't it not be doing that?

Added CPUZ and temps.
I'm don't know how to look at temp programs, nor do I know what is a good temp or bad, so I'll just post the picture of it.

writhziden · Feb 5, 2012

Code:

[list=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
---------
[*]
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
---------

[*]
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
---------

[*]
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
---------

[/list]

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?)
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.
Possible causes are Memory problems... Drivers... Windows error reporting accesses the internet, so the driver causing this fault may be your wireless adapter driver.
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:

Shut down and turn off your computer.
Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
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.

Sabrac · Feb 5, 2012

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.

Dave76 · Feb 6, 2012

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.

Sabrac · Feb 6, 2012

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.

Sabrac · Feb 6, 2012

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.

Dave76 · Feb 6, 2012

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.

Sabrac · Feb 7, 2012

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.

Sabrac · Feb 7, 2012

Got a BSOD a few minutes after my last post.
And another a few hours later while watching Youtube videos named (Dump 2).

Dave76 · Feb 8, 2012

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

Sabrac · Feb 12, 2012

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.

Solved BSOD - Most likely RAM issue

New member

My Computer

New member

My Computer

New member

My Computer

Limburger Cheese

My Computer

New member

My Computer

New member

My Computer

Limburger Cheese

My Computer

Closed by request.

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Similar threads