Solved BSOD - Reloaded Fresh but Still happening :(

[Jenelia]

Windows 7 Ultimate 64-Bit 16 GB of Ram.

Original OS with the System Windows 7 Ultimate (Yes) I haven't strayed away from the original OS other than reloads.

Fresh Reload of the OS as of 02/18/2012.

This is an OEM from IbuyPower. I re-installed from the Disc they supplied in the packaging.

I bought the system in April of 2010. So it's about 22 months old.


Been having blue screens on the previous oS install which was about 7 months old so I figured I should reload as it started happening I thought with a 2011 version of Webroots Spysweeper. When I reloaded on Saturday I installed the updated version even tho the perfmon report says no antivirus. Secureanywhere 8.0 is running.

I recently installed the windbg and found that it's blaming ntoskernel for alot of the problems. I also noticed that googleupdate was a process involved and have recently disabled those services for the time being. I need your advise to tell me what is really happening

Anyway I hope this enough information for you to troubleshoot my recent BSODs on the fresh install of Windows 7.

Thank you Thank you so very much - In advance

 

[writhziden]

[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\Jenelia\Windows_NT6_BSOD_jcgriff2\021912-30919-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`02c11000 PsLoadedModuleList = 0xfffff800`02e56670
Debug session time: Sun Feb 19 11:20:22.716 2012 (GMT-7)
System Uptime: 0 days 1:01:31.214
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseScbFromLazyWrite+42 )

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: fffff8800152096a, 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: 
Ntfs!NtfsReleaseScbFromLazyWrite+42
fffff880`0152096a 837e0801        cmp     dword ptr [rsi+8],1

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec0100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  rundll32.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cd9588 to fffff80002c8dc40

STACK_TEXT:  
fffff880`07a11da8 fffff800`02cd9588 : 00000000`0000001e ffffffff`c0000005 fffff880`0152096a 00000000`00000000 : nt!KeBugCheckEx
fffff880`07a11db0 fffff800`02c8d2c2 : fffff880`07a12588 00000000`0d5613d0 fffff880`07a12630 db7a8250`2b279202 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`07a12450 fffff800`02c8bbca : 00000000`00000000 00000000`0d561440 fffffa80`0d561300 00000000`0d5613d0 : nt!KiExceptionDispatch+0xc2
fffff880`07a12630 fffff880`0152096a : fffff800`02cd2f97 fffffa80`0d5613d0 fffffa80`0d5614e0 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`07a127c8 00000000`00000001 : 00000000`00000001 00000000`00000001 00000000`000007ff 00000000`00000101 : Ntfs!NtfsReleaseScbFromLazyWrite+0x42
fffff880`07a127f8 00000000`00000001 : 00000000`00000001 00000000`000007ff 00000000`00000101 fffff880`00000001 : 0x1
fffff880`07a12800 00000000`00000001 : 00000000`000007ff 00000000`00000101 fffff880`00000001 00000000`00000000 : 0x1
fffff880`07a12808 00000000`000007ff : 00000000`00000101 fffff880`00000001 00000000`00000000 fffff800`02f87c3a : 0x1
fffff880`07a12810 00000000`00000101 : fffff880`00000001 00000000`00000000 fffff800`02f87c3a 00000000`00000000 : 0x7ff
fffff880`07a12818 fffff880`00000001 : 00000000`00000000 fffff800`02f87c3a 00000000`00000000 fffff8a0`000a0008 : 0x101
fffff880`07a12820 00000000`00000000 : fffff800`02f87c3a 00000000`00000000 fffff8a0`000a0008 00000000`00000000 : 0xfffff880`00000001


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsReleaseScbFromLazyWrite+42
fffff880`0152096a 837e0801        cmp     dword ptr [rsi+8],1

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Ntfs!NtfsReleaseScbFromLazyWrite+42

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

FAILURE_BUCKET_ID:  X64_0x1E_Ntfs!NtfsReleaseScbFromLazyWrite+42

BUCKET_ID:  X64_0x1E_Ntfs!NtfsReleaseScbFromLazyWrite+42

Followup: MachineOwner
---------
[*]
Loading Dump File [F:\Kingston\BSODDmpFiles\Jenelia\Windows_NT6_BSOD_jcgriff2\021912-31012-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e70
Debug session time: Sun Feb 19 10:01:37.958 2012 (GMT-7)
System Uptime: 0 days 1:31:31.643
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff500195287f0, 1, fffff80002de9b2f, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!RtlpGenerateInheritAcl+d3 )

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

3: 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: fffff500195287f0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002de9b2f, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f0e0
 fffff500195287f0 

FAULTING_IP: 
nt!RtlpGenerateInheritAcl+d3
fffff800`02de9b2f 4889442438      mov     qword ptr [rsp+38h],rax

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880080e8c60 -- (.trap 0xfffff880080e8c60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800ca943dc rbx=0000000000000000 rcx=fffff8a00440297c
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002de9b2f rsp=fffff880080e8df0 rbp=fffff8a004402974
 r8=0000000000000001  r9=fffff8a00ae0a2e0 r10=fffff8a004402974
r11=fffff880080e90d9 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!RtlpGenerateInheritAcl+0xd3:
fffff800`02de9b2f 4889442438      mov     qword ptr [rsp+38h],rax ss:0018:fffff880`080e8e28=fffff80002c0c2dd
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b56729 to fffff80002ad75c0

STACK_TEXT:  
fffff880`080e8af8 fffff800`02b56729 : 00000000`00000050 fffff500`195287f0 00000000`00000001 fffff880`080e8c60 : nt!KeBugCheckEx
fffff880`080e8b00 fffff800`02ad56ae : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ccb
fffff880`080e8c60 fffff800`02de9b2f : fffffa80`0d9bdde0 fffffa80`0d5c2010 00000000`00000000 fffffa80`0d15e8e0 : nt!KiPageFault+0x16e
fffff880`080e8df0 fffff800`02de58d5 : 00000000`00000003 00000000`00000001 fffffa80`0f900001 fffff8a0`0ae0a2e0 : nt!RtlpGenerateInheritAcl+0xd3
fffff880`080e8eb0 fffff800`02de5031 : fffff8a0`04402974 fffff880`080e9120 00000000`00000000 00000000`00000701 : nt!RtlpInheritAcl2+0x325
fffff880`080e8f70 fffff800`02de4230 : 00000000`00008000 00000000`00000000 fffff880`000000c8 fffff8a0`0ae0a324 : nt!RtlpInheritAcl+0x17d
fffff880`080e9030 fffff800`02d89e69 : fffff8a0`0af43da0 fffff880`080e92e8 fffffa80`00000058 00000000`00000001 : nt!RtlpNewSecurityObject+0xb20
fffff880`080e92c0 fffff800`02d4827f : fffff8a0`0625142c fffffa80`0cfd5b10 fffff8a0`115d9948 00000000`00000000 : nt!SeAssignSecurity+0x3d
fffff880`080e9320 fffff800`02d48bf4 : fffff8a0`007f1010 fffffa80`0140e020 fffff8a0`04402960 fffffa80`0cfd5b10 : nt!CmpDoCreateChild+0x437
fffff880`080e9430 fffff800`02daedc5 : fffff8a0`063aa024 fffff880`0140e020 fffff880`080e9630 fffff880`080e9630 : nt!CmpDoCreate+0x268
fffff880`080e9570 fffff800`02dcdba4 : fffff800`02dad960 00000000`00000001 fffffa80`0cfd5b10 fffff8a0`e24e4d01 : nt!CmpParseKey+0x1465
fffff880`080e9840 fffff800`02dd2b7d : fffffa80`0cfd5b10 fffff880`080e99a0 fffff8a0`00000040 fffffa80`0ca94390 : nt!ObpLookupObjectName+0x585
fffff880`080e9940 fffff800`02d71b18 : 00000000`00000000 00000000`00000000 ffff94c1`e407f101 00000000`00000000 : nt!ObOpenObjectByName+0x1cd
fffff880`080e99f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmCreateKey+0x2e1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!RtlpGenerateInheritAcl+d3
fffff800`02de9b2f 4889442438      mov     qword ptr [rsp+38h],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!RtlpGenerateInheritAcl+d3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0x50_nt!RtlpGenerateInheritAcl+d3

BUCKET_ID:  X64_0x50_nt!RtlpGenerateInheritAcl+d3

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

[*]
Loading Dump File [F:\Kingston\BSODDmpFiles\Jenelia\Windows_NT6_BSOD_jcgriff2\021812-24991-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Sat Feb 18 13:58:29.397 2012 (GMT-7)
System Uptime: 0 days 0:19:02.708
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1d0, 2, 0, fffff88001681730}

Probably caused by : tcpip.sys ( tcpip!TcpMppQueryTcbKillRate+34 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000000001d0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001681730, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc00e0
 00000000000001d0 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TcpMppQueryTcbKillRate+34
fffff880`01681730 448b1b          mov     r11d,dword ptr [rbx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002d8c260 -- (.trap 0xfffff88002d8c260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001681730 rsp=fffff88002d8c3f0 rbp=0000000000000088
 r8=0000000000000001  r9=0000000000000002 r10=fffff88002d64180
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
tcpip!TcpMppQueryTcbKillRate+0x34:
fffff880`01681730 448b1b          mov     r11d,dword ptr [rbx] ds:0e60:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a89469 to fffff80002a89f00

STACK_TEXT:  
fffff880`02d8c118 fffff800`02a89469 : 00000000`0000000a 00000000`000001d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02d8c120 fffff800`02a880e0 : 00000000`00000000 00000000`000001d0 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02d8c260 fffff880`01681730 : 00000000`000001d0 fffff880`02d64180 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02d8c3f0 fffff880`01681e6b : 00000000`00000e10 00000000`00000002 00000000`00000002 00000000`0001bea4 : tcpip!TcpMppQueryTcbKillRate+0x34
fffff880`02d8c440 fffff880`016705fc : fffffa80`0d91ad30 00000000`00000e10 00000000`00000004 00000000`0001bea4 : tcpip!TcpTimerMppTimeoutHandler+0x63
fffff880`02d8c4f0 fffff800`02a95fa6 : fffff880`02d8c600 fffffa80`00010264 00000000`00000001 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x39e
fffff880`02d8c570 fffff800`02a95326 : fffffa80`0d91ae00 00000000`00011e22 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`02d8c5e0 fffff800`02a95e7e : 00000002`a91b7fba fffff880`02d8cc58 00000000`00011e22 fffff880`02d669c8 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02d8cc30 fffff800`02a95697 : 00000000`e30e5ec1 00000000`00011e22 00000000`e30e5e9a 00000000`00000021 : nt!KiTimerExpiration+0x1be
fffff880`02d8ccd0 fffff800`02a926fa : fffff880`02d64180 fffff880`02d6efc0 00000000`00000000 fffff880`050a7588 : nt!KiRetireDpcList+0x277
fffff880`02d8cd80 00000000`00000000 : fffff880`02d8d000 fffff880`02d87000 fffff880`02d8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TcpMppQueryTcbKillRate+34
fffff880`01681730 448b1b          mov     r11d,dword ptr [rbx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!TcpMppQueryTcbKillRate+34

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc26e

FAILURE_BUCKET_ID:  X64_0xD1_tcpip!TcpMppQueryTcbKillRate+34

BUCKET_ID:  X64_0xD1_tcpip!TcpMppQueryTcbKillRate+34

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


[/list]

1. Points to your hard disk having errors. Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
2. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
3. Points to your network or your antivirus. Likely Webroot related.

Thanks to Dave76 for help understanding possible causes.



One of your devices has not yet had its drivers installed.

Not Available	PCI\VEN_1957&DEV_00B6&SUBSYS_11011A56&REV_12\4&16A7741&0&0028	The drivers for this device are not installed.

Do the following steps. After each step, test if the system is stable, and if it is not, proceed to the next step.

• If you are overclocking any hardware, please stop.
  
  
  
• Install the drivers for your device that is missing drivers. It looks like a gaming adapter device or network adapter device or PCI device... I could not find the exact match through Google, so hopefully you'll have better luck since it is one of your components.
  
  
  
• Uninstall Webroot antivirus using the steps for uninstall outlined in How do I uninstall and reinstall my program? and replace it with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall, at least to test.
  
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
  
• Download Seagate Seatools and run diagnostics on your hard drive that is running Windows.

 

[Jenelia]

Thanks for your reply, the missing driver is a BigFootNetworks Killer Card. I uninstalled that after the TCPIP crash thinking it was related to that. So at the present time I'm running the onboard Realtek 1GB adapter.

There's no overclocking going on but this board does have many options for overclocking but I've never overclocked I never have any need to this machine is plenty fast

I have the seagate tools, I ran a quick test on the Disk with the OS installed and no errors, even a simple Windows scan found nothing wrong either.

Since I turned off the gupdate (google update) services no blue screens for at least 7 hours. I'll run some more extensive tests on the hard-drives and memory and report back .

Thank you for looking at these

 

[writhziden]

You're welcome. Let us know if you have any more crashes (hope not) or if the system is stable (best wishes this is the case).

 

[Jenelia]

Running Seagate tools, i believe it was scanning the OS drive, Seagate tools locked up and there was some really small text at the top of the screen. I couldn't read it as it was super small and the system was just froze solid. My thinking is there is a very bad spot on the drive it was scanning and crashed it. What do you think?

No way to get to the logs cause I had to shut off due to a very loud beeeep coming from the system.

 

[writhziden]

Was it a sustained beep? Beeps signify hardware failure of some kind. See the image for the possible failures. My guess is it was just the last one and it may have easily been due to the hard disk being bad. There is a DOS version of SeaTools you could run instead. You will have to burn the SeaTools ISO to a CD or DVD to use it.

 

[Jenelia]

It was a Solid Long beep (While Seagate dos version tools was running when i moved the cursor after it locked up) and it wouldn't stop until I shut the computer off. This wasn't at post , I haven't turned it back on since being at work :/

 

[Jenelia]

Running scan again on the drive that I think is bad, I'll let you know what happens. It's about 24 months old so I doubt Seagate will issue a RMA for it , or will they?

 

[writhziden]

It depends on the drive. Some still have three year warranties.

 

[Jenelia]

Well good news, I ran through scan fully and there we no errors on any of the drives through seagate DOS tools. I ran a MS memory check too and no errors with memory. After work today I'll boot up Windows to see what happens.

Thanks

 

[Jenelia]

Well today I booted up my computer back to windows for the first time since running scan from Seagate tools and it bluescreen right away, twice. This is the last report from windbg

CODE

Loading Dump File [C:\Windows\Minidump\022112-21075-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*D:\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`02c53000 PsLoadedModuleList = 0xfffff800`02e98670
Debug session time: Tue Feb 21 18:27:34.642 2012 (UTC - 5:00)
System Uptime: 0 days 0:07:30.125
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff80002ced931, 0, fffffa800ceba600}

Probably caused by : memory_corruption ( nt!MiDispatchFault+aa2 )

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

1: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002ced931, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffffa800ceba600, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!MiDispatchFault+aa2
fffff800`02ced931 4c3bea cmp r13,rdx

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: fffffa800ceba600

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

BUGCHECK_STR: 0x1E_c000001d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: MsMpEng.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d1b588 to fffff80002ccfc40

FAILED_INSTRUCTION_ADDRESS:
nt!MiDispatchFault+aa2
fffff800`02ced931 4c3bea cmp r13,rdx

STACK_TEXT:
fffff880`028aaf98 fffff800`02d1b588 : 00000000`0000001e ffffffff`c000001d fffff800`02ced931 00000000`00000000 : nt!KeBugCheckEx
fffff880`028aafa0 fffff800`02ccf2c2 : fffff880`028ab778 fffffa80`0e5cedc0 fffff880`028ab820 0000007f`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`028ab640 fffff800`02ccd41f : fffff880`028ab820 00000000`00000000 00000000`01239f00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`028ab820 fffff800`02ced931 : 00000000`00000001 fffff680`00021680 fffff880`028abc20 fffff6fb`40000108 : nt!KiInvalidOpcodeFault+0x11f
fffff880`028ab9b0 fffff800`02cdcf19 : 00000000`00000000 00000000`01238ff8 fffff700`01080000 00000000`00000000 : nt!MiDispatchFault+0xaa2
fffff880`028abac0 fffff800`02ccdd6e : 00000000`00000000 00000000`01238ff8 00000000`00000b01 00000000`74bb2828 : nt!MmAccessFault+0x359
fffff880`028abc20 000007fe`ff2911fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0249e618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff2911fd


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDispatchFault+aa2
fffff800`02ced931 4c3bea cmp r13,rdx

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!MiDispatchFault+aa2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!MiDispatchFault+aa2

BUCKET_ID: X64_0x1E_c000001d_BAD_IP_nt!MiDispatchFault+aa2

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

 

[Jenelia]

So now I'm going to go do a memory scan. I've already loaded the latest bios for this board. Reloaded defaults in the bios too, I wonder if I need to set voltages for the RAM or CPU. I never had to before and it worked fine up until a week ago.

 

[writhziden]

Have you tried restoring to an earlier point in time with System Restore? Pay close attention to the NOTE: in part 8. to find older restore points and try to restore to before the problem began.

Backup any important files first.

 

[Jenelia]

Yea I thought about restore points but it's really a fresh install, I ran the Windows Memory diagnostics and it reported hardware issues soooo I think for some reason out of the blue a memory chip is bad, the last dump with Driver verifier on turned up nothing driver related so it has to be hardware. UGh... Looks like I'm going to be flipping chips in / out to find the baddies so I think I would say this is resolved... Hardware failure! it Figures! Just my Luck!

Thank you Writh, you've gave me the direction I needed and without it I think I'd be lost. Cheers !

Jen

 

[writhziden]

No problem. 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.



Sorry it wasn't something simple. Best of luck tracking the problem down!

 

[Jenelia]

Thank you for that , I do believe that makes alot of sense, I have the computer on a metal file cabinet to keep it off the floor. (I have two german shepherds) so you can imagine the pet dander that gets around, but I have the computer in the living room gated off but the dander and dust does get in here. Most importantly the computer chair was on top of a plastic Chair mat which was on top of a "18x18" RUG.. and it has been dry but not enough for me to get shocked so that point on ESD really does make sense.

I've gone through Windows 7 Memory Diagnostics so far one memory stick at a time and so far 2 sticks (4g each) have checked out fine. I'm logged on now with one that is working so I'm going through to check the other two.

I know when I had all 4 in WMD did report hardware errors so I hope I find the one thats bad and get an RMA from A-Data but it's been almost 2 years so who knows. I can't really complain this is the most trouble I've had with this since I got it, I bought it for 5k from Ibuypower and I called them about the ram and they gave me all the details I needed.

The Mother board is a M4A79T Deluxe (AMD 64 Phenom II x4 965 CPU Installed) I did flash it to the latest bios so I can buy 1600 memory if needed but I don't think I'm that needy for something that powerful at the moment. I just want it working and I'll live with 8GB of Ram if I have to. Money is kinda tight right now. Ok I'm rambling.. sorry Cheers


Thanks again.

 

[writhziden]

No problem with rambling. You're welcome to provide any updates you want. Glad you're narrowing it down.

You're welcome for the help. Best of luck!

 

[Jenelia]

Thanks I'm going to try the memory diagnostics that comes with Fedora 15 DVD , I have suspicions that the one that comes with Windows isn't thorough enough. I'll report back later

 

[writhziden]

The Windows diagnostic is not the best, but it does find errors from bad modules if they are bad enough.

My usual rant on this is:

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[Jenelia]

I agree Windows Diagnostics suck.. ok I said it. It had me going on a wild goose chase. Thankfully I didn't spend too much time trying to figure *THAT* out so I went directly to MemTest86+ from a bootable Fedora 15 and later downloaded the updated one you linked on it's own bootable CD, Thank you

Having said that I found 2 4gb Chips that actually tested good and have been using them and Windows 7 has been stable for 16 hours and counting, so running on 8GB instead of 16gb. I"ll let this run a week and see what happens

Thanks again for your help