bsod for random reasons

[mojodup]

MY BSOD HELL

hi i have been having problems with random but constant bsod, i am running a

nvidia geforce 6100pm-m2 v3 motherboard
amd athlon 2 x 4 620 processor
2gb ddr2 800mhz
with a inno3d nvidia authorised (whatever that means) geforce 9800 gt 1gb graphics card
and a nikkai a38gn rf wireless mouse
580w power supply

my os is a windows 7 home x64 upgrade from win xp home

blue screens have been happening at random times when playing games when booting when watching vids generally whenever it feels like it i have tried several things including running repair installation off of windows installation disc, this hasnt seemed to make any differnce other than now it is bringing up new reason for bsod,
this is really starting to frustrate me as the whole system is less than 6 months old
also aswell as this the res keeps changing itself (well at least the desktop keeps changing from large to small icons and vice-versa.... could this be connected??

could someone please check over my dmp files

thanks

 

[zigzag3143]

hi i have been having problems with random but constant bsod, i am running a

nvidia geforce 6100pm-m2 v3 motherboard
amd athlon 2 x 4 620 processor
2gb ddr2 800mhz
with a inno3d nvidia authorised (whatever that means) geforce 9800 gt 1gb graphics card
and a nikkai a38gn rf wireless mouse
580w power supply

my os is a windows 7 home x64 upgrade from win xp home

blue screens have been happening at random times when playing games when booting when watching vids generally whenever it feels like it i have tried several things including running repair installation off of windows installation disc, this hasnt seemed to make any differnce other than now it is bringing up new reason for bsod,
this is really starting to frustrate me as the whole system is less than 6 months old
also aswell as this the res keeps changing itself (well at least the desktop keeps changing from large to small icons and vice-versa.... could this be connected??

could someone please check over my dmp files

thanks

The most recent one was caused by mpfilter.sys part of MSE. I would re-install MSE to test.

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\031611-13509-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;srv*e:\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 Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0340a000 PsLoadedModuleList = 0xfffff800`0364fe90
Debug session time: Wed Mar 16 08:11:45.249 2011 (GMT-4)
System Uptime: 0 days 0:02:29.153
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880016651b7, fffff8800a3198d8, fffff8800a319130}

Probably caused by : MpFilter.sys ( MpFilter+101b7 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880016651b7, The address that the exception occurred at
Arg3: fffff8800a3198d8, Exception Record Address
Arg4: fffff8800a319130, Context Record Address

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


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

FAULTING_IP: 
MpFilter+101b7
fffff880`016651b7 66833900        cmp     word ptr [rcx],0

EXCEPTION_RECORD:  fffff8800a3198d8 -- (.exr 0xfffff8800a3198d8)
ExceptionAddress: fffff880016651b7 (MpFilter+0x00000000000101b7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT:  fffff8800a319130 -- (.cxr 0xfffff8800a319130)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800a319b90
rdx=000000000000002c rsi=0000000000000001 rdi=0000000000000000
rip=fffff880016651b7 rsp=fffff8800a319b10 rbp=0000000001000100
 r8=0000000000000024  r9=ffffffdffeb92580 r10=fffff8a002ae94f0
r11=0000000000000000 r12=fffffa80049925d0 r13=0000000000000001
r14=fffffa8004992628 r15=0000000000100081
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
MpFilter+0x101b7:
fffff880`016651b7 66833900        cmp     word ptr [rcx],0 ds:002b:fffff880`0a319b90=000c
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036bb0e8
 0000000000000000 

FOLLOWUP_IP: 
MpFilter+101b7
fffff880`016651b7 66833900        cmp     word ptr [rcx],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 000000000010000e to fffff880016651b7

STACK_TEXT:  
fffff880`0a319b10 00000000`0010000e : fffff880`0167ba70 fffffa80`04992628 00000000`00000001 fffffa80`049925d0 : MpFilter+0x101b7
fffff880`0a319b18 fffff880`0167ba70 : fffffa80`04992628 00000000`00000001 fffffa80`049925d0 00000000`00000000 : 0x10000e
fffff880`0a319b20 fffffa80`04992628 : 00000000`00000001 fffffa80`049925d0 00000000`00000000 00000000`00000000 : MpFilter+0x26a70
fffff880`0a319b28 00000000`00000001 : fffffa80`049925d0 00000000`00000000 00000000`00000000 fffff880`016632b9 : 0xfffffa80`04992628
fffff880`0a319b30 fffffa80`049925d0 : 00000000`00000000 00000000`00000000 fffff880`016632b9 fffffa80`02a6b880 : 0x1
fffff880`0a319b38 00000000`00000000 : 00000000`00000000 fffff880`016632b9 fffffa80`02a6b880 fffffa80`01a040c0 : 0xfffffa80`049925d0


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  MpFilter+101b7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MpFilter

IMAGE_NAME:  MpFilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c901110

STACK_COMMAND:  .cxr 0xfffff8800a319130 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_MpFilter+101b7

BUCKET_ID:  X64_0x7E_MpFilter+101b7

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

0: kd> lmvm MpFilter
start             end                 module name
fffff880`01655000 fffff880`01686000   MpFilter T (no symbols)           
    Loaded symbol image file: MpFilter.sys
    Image path: \SystemRoot\system32\DRIVERS\MpFilter.sys
    Image name: MpFilter.sys
    Timestamp:        Tue Sep 14 20:19:28 2010 (4C901110)
    CheckSum:         00036060
    ImageSize:        00031000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[mojodup]

hi thanks for looking i uninstalled mse but it did not seem to make any difference so i went for a reinstall, instead of installing x64 i went to the more compatable x32,but problems havnt stopped, still bsod, freezing, failing to boot properly and constantly trying to run startup repair, only for that to keep giving me error codes of 0x0 and 0x490 system file integrity check :sarc: