Bsod Crashes Also, No known reason

I have no idea why this is happening. I was running W7 RC and Never once had a problem. I installed Pro 7 from scratch and have been having problems since. I am completely lost I have only enough time to read "page fault error" or something like that.

Any Help and direction is going to be awesome, as I have already turned to you guys for so many resources from you guys.

B26ninspot said:

I have no idea why this is happening. I was running W7 RC and Never once had a problem. I installed Pro 7 from scratch and have been having problems since. I am completely lost I have only enough time to read "page fault error" or something like that.

Any Help and direction is going to be awesome, as I have already turned to you guys for so many resources from you guys.

These crashes are being caused by memory corruption. It was caused by either nero (which has problems in win 7) or your comodo firewall.

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

I would
uninstall comodo and nero to see if it fixes the memory corruption
download memtestx86 and run it for 5 passes
run a system file check
type cmd in search>right click and run as admin>sfc /scannow

let us know the results as you may have to re-run it

Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\021510-14445-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*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`02e4a000 PsLoadedModuleList = 0xfffff800`03087e50
Debug session time: Mon Feb 15 19:26:08.024 2010 (GMT-5)
System Uptime: 0 days 0:03:04.068
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffce802e7402b0, 1, fffff88001081840, 7}

Unable to load image \SystemRoot\System32\DRIVERS\cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys

Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: ffffce802e7402b0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88001081840, 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 fffff800030f20e0
 ffffce802e7402b0 

FAULTING_IP: 
fltmgr!FltIsDirectory+0
fffff880`01081840 48895cff10      mov     qword ptr [rdi+rdi*8+10h],rbx

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  NERO-8.1.1.0B_

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800824d0e0 -- (.trap 0xfffff8800824d0e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=9990000033543901 rbx=0000000000000000 rcx=fffffa80052955a0
rdx=fffffa8004a0f010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001081840 rsp=fffff8800824d278 rbp=0000000000000000
 r8=fffff8800824d2f1  r9=0000000000000000 r10=fffffa8004c0dab0
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
fltmgr!FltIsDirectory:
fffff880`01081840 48895cff10      mov     qword ptr [rdi+rdi*8+10h],rbx ds:be00:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f39b19 to fffff80002ebbf00

STACK_TEXT:  
fffff880`0824cf78 fffff800`02f39b19 : 00000000`00000050 ffffce80`2e7402b0 00000000`00000001 fffff880`0824d0e0 : nt!KeBugCheckEx
fffff880`0824cf80 fffff800`02eb9fee : 00000000`00000001 fffff8a0`02801c70 00000000`00000000 fffffa80`00000201 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`0824d0e0 fffff880`01081840 : fffff880`015e6a87 fffffa80`069240c0 fffff880`015ea10a fffffa80`04a0f010 : nt!KiPageFault+0x16e
fffff880`0824d278 fffff880`015e6a87 : fffffa80`069240c0 fffff880`015ea10a fffffa80`04a0f010 00000000`00000000 : fltmgr!FltIsDirectory
fffff880`0824d280 fffffa80`069240c0 : fffff880`015ea10a fffffa80`04a0f010 00000000`00000000 00000000`00000072 : cmdguard+0xfa87
fffff880`0824d288 fffff880`015ea10a : fffffa80`04a0f010 00000000`00000000 00000000`00000072 00000000`10000004 : 0xfffffa80`069240c0
fffff880`0824d290 fffffa80`04a0f010 : 00000000`00000000 00000000`00000072 00000000`10000004 fffffa80`069240c0 : cmdguard+0x1310a
fffff880`0824d298 00000000`00000000 : 00000000`00000072 00000000`10000004 fffffa80`069240c0 fffff880`015e92bb : 0xfffffa80`04a0f010


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !fltmgr
8 errors : !fltmgr (fffff88001081843-fffff8800108187b)
fffff88001081840  48  89  5c *ff  10  48  89  6c  24  18  48 *ff  74  24  20  57 H.\..H.l$.H.t$ W
fffff88001081850  48  83  ec *ff  41  c6  00  00  48  83  79 *ff  00  49  8b  f0 H...A...H.y..I..
fffff88001081860  48  8b  ea *ff  8b  d9  75  0a  b8  ef  00 *ff  c0  e9  b8  00 H.....u.........
fffff88001081870  00  00  ff *ff  f8  17  00  00  85  c0  74 *ff  33  c0  e9  a7 ..........t.3...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption

---------

Wow WOW is all I can say. That was fast as lightning. I haven't been able to even install nero. I can uninstall Comodo. But then am wandering what I am going to do with out those programs. I have ran memtest86 on each module for 24 hours or so with no issues. So is it more likely the OS is the Problem and not the memory. I have some experience with computers but am wondering about my purchase of W7-64. Any suggestions???

I have since had 3 BSODs since your reply. What in the world have I got myself into??? Please help.

dear Captain,

I wish I was as smart as you and the others that offer up advice and answers on here. Then I would not be bothering you on your own time. Is there a way to tell how/what you use and ways you get your BSOD info from. I would really like to take care of my problem without expecting so much from everyone here.

I have run SFC with no errors and now have my drivers up to date. I am still getting errors but am not sure if they are linked to the memory I am cont trying to get to work now after switching to W7 -64bit

I am unsure how to update the other items you listed on the post also

Try swapping your ram with different ones,\
If that works fine try your old ram one at a time, this will help you isolate the defective ram. Once you have done that get a new ram and you should be good to go