bsod about every 15 mins............

#1
hi,
i'm really pissed with my comp showing bsod every 15 mins. earlier i used to get bsod only while gaming but now even if i do NOTHING it still shows up.i'm attaching the files i found in c:\windows\minidump directory. pls help as soon as possible. tell me whether any other info is needed.......:)
 


Attachments

#2
0x24_Ntfs!NtfsFcbTableCompare
0x8E_win32k!XDCOBJ::bCleanDC


Command Prompt --> sfc /scannow


Update (or uninstall and disable):


Analog Devices
giveio.sys Wed Apr 03 22:33:25 1996


Realtek LAN
Rt86win7.sys Thu Feb 26 04:04:22 2009



If crashes reoccur after you have updated the drivers, uninstall Kaspersky and install MSE:
http://www.microsoft.com/security_essentials/


http://windows7forums.com/blue-scre...mportant-every-thread-starter-please-see.html


CRASH DUMPS

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\032111-12906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c17000 PsLoadedModuleList = 0x82d56570
Debug session time: Mon Mar 21 02:37:45.713 2011 (UTC - 4:00)
System Uptime: 0 days 0:27:51.557
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82d2ef03, 926f7b54, 0}

Probably caused by : win32k.sys ( win32k!XDCOBJ::bCleanDC+24d )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 82d2ef03, The address that the exception occurred at
Arg3: 926f7b54, Trap Frame
Arg4: 00000000

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!ExFreePoolWithTag+466
82d2ef03 0fb74ffa        movzx   ecx,word ptr [edi-6]

TRAP_FRAME:  926f7b54 -- (.trap 0xffffffff926f7b54)
ErrCode = 00000000
eax=00000000 ebx=926f7cfc ecx=00008400 edx=00000001 esi=00008400 edi=00008400
eip=82d2ef03 esp=926f7bc8 ebp=926f7c24 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!ExFreePoolWithTag+0x466:
82d2ef03 0fb74ffa        movzx   ecx,word ptr [edi-6]     ds:0023:000083fa=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9711e637 to 82d2ef03

STACK_TEXT:  
926f7c24 9711e637 00008400 00000000 054a0d6e nt!ExFreePoolWithTag+0x466
926f7ca0 9711e1e8 00000000 054a0d12 00000000 win32k!XDCOBJ::bCleanDC+0x24d
926f7cdc 9711df62 926f7cfc 00000000 00000000 win32k!bDeleteDCInternalWorker+0x1b
926f7d08 970ffc29 0301082c 00000000 00000000 win32k!bDeleteDCInternal+0x30
926f7d28 82c4c79a 0301082c 0022e658 77cc64f4 win32k!NtGdiDeleteObjectApp+0xa0
926f7d28 77cc64f4 0301082c 0022e658 77cc64f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0022e658 00000000 00000000 00000000 00000000 0x77cc64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!XDCOBJ::bCleanDC+24d
9711e637 8b03            mov     eax,dword ptr [ebx]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  win32k!XDCOBJ::bCleanDC+24d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7dbbb5

FAILURE_BUCKET_ID:  0x8E_win32k!XDCOBJ::bCleanDC+24d

BUCKET_ID:  0x8E_win32k!XDCOBJ::bCleanDC+24d

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























Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\032111-12359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c03000 PsLoadedModuleList = 0x82d42570
Debug session time: Sun Mar 20 11:36:25.262 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:47.090
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 001904fb
Arg2: a127e7d0
Arg3: a127e3b0
Arg4: 8bcd2629

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


EXCEPTION_RECORD:  a127e7d0 -- (.exr 0xffffffffa127e7d0)
ExceptionAddress: 8bcd2629 (Ntfs!NtfsFcbTableCompare+0x00000015)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000210
Attempt to read from address 00000210

CONTEXT:  a127e3b0 -- (.cxr 0xffffffffa127e3b0)
eax=000a0000 ebx=99ec6600 ecx=00000210 edx=0000d975 esi=00000200 edi=860ea3e8
eip=8bcd2629 esp=a127e898 ebp=a127e8b0 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
Ntfs!NtfsFcbTableCompare+0x15:
8bcd2629 8b31            mov     esi,dword ptr [ecx]  ds:0023:00000210=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000210

READ_ADDRESS: GetPointerFromAddress: unable to read from 82d62700
Unable to read MiSystemVaType memory at 82d420c0
 00000210 

FOLLOWUP_IP: 
Ntfs!NtfsFcbTableCompare+15
8bcd2629 8b31            mov     esi,dword ptr [ecx]

FAULTING_IP: 
Ntfs!NtfsFcbTableCompare+15
8bcd2629 8b31            mov     esi,dword ptr [ecx]

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 82c884e0 to 8bcd2629

STACK_TEXT:  
a127e8b0 82c884e0 860ea3e8 a127e914 00000210 Ntfs!NtfsFcbTableCompare+0x15
a127e8c8 82c8852a a127e914 a127e900 860ea0d8 nt!FindNodeOrParent+0x20
a127e8e0 82c88560 860ea3e8 a127e914 a127e900 nt!RtlLookupElementGenericTableFullAvl+0x16
a127e8f8 8bccda5e 860ea3e8 a127e914 8d58ad08 nt!RtlLookupElementGenericTableAvl+0x18
a127e994 8bcba8cc 8597e798 99ec6600 8d58ad08 Ntfs!NtfsRetrieveOtherFileName+0x131
a127eb98 8bcd8783 8597e798 8739e4b0 860ea0d8 Ntfs!NtfsQueryDirectory+0xc74
a127ebcc 8bcd84fa 8597e798 99ec6600 2ae156a1 Ntfs!NtfsCommonDirectoryControl+0x21d
a127ec34 82c31f44 860ea020 8739e4b0 8739e4b0 Ntfs!NtfsFsdDirectoryControl+0xf7
a127ec4c 8bb6320c 860b2cd0 8739e4b0 00000000 nt!IofCallDriver+0x63
a127ec70 8bb633cb a127ec90 860b2cd0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
a127eca8 82c31f44 860b2cd0 8739e4b0 8739e4b0 fltmgr!FltpDispatch+0xc5
a127ecc0 82e07307 00000140 0019dc20 82e59adf nt!IofCallDriver+0x63
a127ece0 82e59b3a 860b2cd0 874d4e28 00000001 nt!IopSynchronousServiceTail+0x1f8
a127ed00 82c3879a 00000140 00000000 00000000 nt!NtQueryDirectoryFile+0x5b
a127ed00 77d364f4 00000140 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0019dc5c 00000000 00000000 00000000 00000000 0x77d364f4


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsFcbTableCompare+15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45

STACK_COMMAND:  .cxr 0xffffffffa127e3b0 ; kb

FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsFcbTableCompare+15

BUCKET_ID:  0x24_Ntfs!NtfsFcbTableCompare+15

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
























Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\032111-11875-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c08000 PsLoadedModuleList = 0x82d47570
Debug session time: Sun Mar 20 22:45:35.250 2011 (UTC - 4:00)
System Uptime: 0 days 0:57:20.078
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 001904fb
Arg2: 91779a7c
Arg3: 91779660
Arg4: 8bcd0ca1

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


EXCEPTION_RECORD:  91779a7c -- (.exr 0xffffffff91779a7c)
ExceptionAddress: 8bcd0ca1 (Ntfs!NtfsLookupHashEntry+0x00000042)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00008e08
Attempt to read from address 00008e08

CONTEXT:  91779660 -- (.cxr 0xffffffff91779660)
eax=00008e00 ebx=00000703 ecx=9cf0b000 edx=860eab48 esi=22995f03 edi=00000001
eip=8bcd0ca1 esp=91779b44 ebp=91779b4c iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
Ntfs!NtfsLookupHashEntry+0x42:
8bcd0ca1 397008          cmp     dword ptr [eax+8],esi ds:0023:00008e08=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00008e08

READ_ADDRESS: GetPointerFromAddress: unable to read from 82d67700
Unable to read MiSystemVaType memory at 82d470c0
 00008e08 

FOLLOWUP_IP: 
Ntfs!NtfsLookupHashEntry+42
8bcd0ca1 397008          cmp     dword ptr [eax+8],esi

FAULTING_IP: 
Ntfs!NtfsLookupHashEntry+42
8bcd0ca1 397008          cmp     dword ptr [eax+8],esi

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from 8bcb7af0 to 8bcd0ca1

STACK_TEXT:  
91779b4c 8bcb7af0 860eab48 22995f03 00000000 Ntfs!NtfsLookupHashEntry+0x42
91779ba4 8bcb865b 854323d8 860eab48 8d5056e0 Ntfs!NtfsFindPrefixHashEntry+0x158
91779c00 8bcbac5c 854323d8 853cb008 8d5056e0 Ntfs!NtfsFindStartingNode+0x7b6
91779cdc 8bc41210 854323d8 853cb008 9173d884 Ntfs!NtfsCommonCreate+0x65f
91779d1c 82c65056 9173d81c 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
91779d1c 82c6514d 9173d81c 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
9173d780 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsLookupHashEntry+42

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45

STACK_COMMAND:  .cxr 0xffffffff91779660 ; kb

FAILURE_BUCKET_ID:  0x24_Ntfs!NtfsLookupHashEntry+42

BUCKET_ID:  0x24_Ntfs!NtfsLookupHashEntry+42

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



















Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\032111-21390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c1e000 PsLoadedModuleList = 0x82d5d570
Debug session time: Mon Mar 21 02:49:32.443 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:30.255
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82d35f03, a0b6eb54, 0}

Probably caused by : win32k.sys ( win32k!XDCOBJ::bCleanDC+24d )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 82d35f03, The address that the exception occurred at
Arg3: a0b6eb54, Trap Frame
Arg4: 00000000

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!ExFreePoolWithTag+466
82d35f03 0fb74ffa        movzx   ecx,word ptr [edi-6]

TRAP_FRAME:  a0b6eb54 -- (.trap 0xffffffffa0b6eb54)
ErrCode = 00000000
eax=00000000 ebx=a0b6ecfc ecx=00008a00 edx=00000001 esi=00008a00 edi=00008a00
eip=82d35f03 esp=a0b6ebc8 ebp=a0b6ec24 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!ExFreePoolWithTag+0x466:
82d35f03 0fb74ffa        movzx   ecx,word ptr [edi-6]     ds:0023:000089fa=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 969de637 to 82d35f03

STACK_TEXT:  
a0b6ec24 969de637 00008a00 00000000 36079cd5 nt!ExFreePoolWithTag+0x466
a0b6eca0 969de1e8 00000000 36079ca9 00000000 win32k!XDCOBJ::bCleanDC+0x24d
a0b6ecdc 969ddf62 a0b6ecfc 00000000 00000000 win32k!bDeleteDCInternalWorker+0x1b
a0b6ed08 969bfc29 04010722 00000000 00000000 win32k!bDeleteDCInternal+0x30
a0b6ed28 82c5379a 04010722 044bf4e8 77d164f4 win32k!NtGdiDeleteObjectApp+0xa0
a0b6ed28 77d164f4 04010722 044bf4e8 77d164f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
044bf4e8 00000000 00000000 00000000 00000000 0x77d164f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!XDCOBJ::bCleanDC+24d
969de637 8b03            mov     eax,dword ptr [ebx]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  win32k!XDCOBJ::bCleanDC+24d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7dbbb5

FAILURE_BUCKET_ID:  0x8E_win32k!XDCOBJ::bCleanDC+24d

BUCKET_ID:  0x8E_win32k!XDCOBJ::bCleanDC+24d

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




DRIVERS

Code:
start    end        module name
8b9fe000 8ba46000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8c384000 8c3de000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
93824000 93836000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
8bb4f000 8bb58000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
8bb23000 8bb2c000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
8bb2c000 8bb4f000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
96800000 9684d000   ATMFD    ATMFD.DLL    Wed May 26 23:49:36 2010 (4BFDEBD0)
8c2f0000 8c2f7000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
928b4000 928c2000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
8b88a000 8b892000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
92af0000 92b09000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
96ba0000 96bbe000   cdd      cdd.dll      Wed Jan 26 00:50:45 2011 (4D3FB635)
8b8d4000 8b97f000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
8c292000 8c2b7000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
8b892000 8b8d4000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8bdab000 8be08000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
93817000 93824000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
95775000 95782000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
92838000 9289c000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
9289c000 928b4000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8bfd9000 8bfe5000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
8c281000 8c292000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
95752000 9576b000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
9578d000 95796000   dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
95782000 9578d000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
95796000 957a7000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
9576b000 95775000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
94232000 942e9000   dxgkrnl  dxgkrnl.sys  Tue Jan 25 23:06:46 2011 (4D3F9DD6)
942e9000 94322000   dxgmms1  dxgmms1.sys  Tue Jan 25 23:05:51 2011 (4D3F9D9F)
8bb8c000 8bb9d000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
8bb58000 8bb8c000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
8be16000 8be1f000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
8c24f000 8c281000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
8c186000 8c1b7000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
8c24e000 8c24e680   giveio   giveio.sys   Wed Apr 03 22:33:25 1996 (316334F5)
8301e000 83055000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
94322000 94341000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
957bd000 957d0000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
957d0000 957d6480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
957b2000 957bd000   hidusb   hidusb.sys   Mon Jul 13 19:51:04 2009 (4A5BC868)
92a6b000 92af0000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
8c246000 8c24e000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
943e3000 943fb000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
8baf8000 8baff000   intelide intelide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17)
928e3000 928f5000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
93800000 9380d000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
80bbc000 80bc4000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
be03b000 be55d000   kl1      kl1.sys      Wed Jun 09 09:24:39 2010 (4C0F9617)
be55d000 be563000   kl2      kl2.sys      Wed Jun 09 09:24:35 2010 (4C0F9613)
9d596000 9d619000   klif     klif.sys     Fri Oct 01 03:30:11 2010 (4CA58E03)
9d619000 9d621000   klim6    klim6.sys    Thu Apr 22 11:07:20 2010 (4BD06628)
92997000 929cb000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
8bd98000 8bdab000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
8bf14000 8bf39000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
957d9000 957e0d80   LHidFilt LHidFilt.Sys Thu Mar 18 04:50:19 2010 (4BA1E94B)
92a48000 92a58000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
957ec000 957f3780   LMouFilt LMouFilt.Sys Thu Mar 18 04:50:27 2010 (4BA1E953)
95400000 9541b000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
8b801000 8b879000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
957a7000 957b2000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
9298a000 92997000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
957e1000 957ec000   mouhid   mouhid.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8bb0d000 8bb23000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
92b09000 92b1b000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
92b1b000 92b3e000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
92b3e000 92b79000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
92b79000 92b94000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
8c349000 8c354000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8ba4f000 8ba57000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
8bd6d000 8bd98000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8bfcf000 8bfd9000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
8c236000 8c246000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
8be1f000 8bed6000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
9290d000 92918000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
92918000 9293a000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
92a1d000 92a2e000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8bf39000 8bf47000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8c000000 8c032000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
8bed6000 8bf14000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
8c354000 8c362000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8bfc5000 8bfcf000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82c1e000 8301e000   nt       ntkrnlmp.exe Fri Jun 18 23:55:07 2010 (4C1C3F9B)
8bc3e000 8bd6d000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8c2e9000 8c2f0000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
94230000 94231040   nvBridge nvBridge.kmd Fri Jan 07 20:57:19 2011 (4D27C47F)
93836000 9422fee0   nvlddmkm nvlddmkm.sys Fri Jan 07 21:03:58 2011 (4D27C60E)
8c3de000 8c3fd000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
943cb000 943e3000   parport  parport.sys  Mon Jul 13 19:45:34 2009 (4A5BC71E)
8ba8c000 8ba9d000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
9541b000 95422000   parvdm   parvdm.sys   Mon Jul 13 19:45:29 2009 (4A5BC719)
8ba57000 8ba81000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
8baff000 8bb0d000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
8be08000 8be16000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
9d427000 9d4be000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
95723000 95752000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
8b879000 8b88a000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
928f5000 9290d000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
9293a000 92952000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
92952000 92969000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
92969000 92980000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8bf84000 8bfc5000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
92980000 9298a000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
8c331000 8c339000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8c339000 8c341000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8c341000 8c349000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
8c209000 8c236000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
92a58000 92a6b000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
be588000 be5ad000   Rt86win7 Rt86win7.sys Thu Feb 26 04:04:22 2009 (49A65B16)
95427000 957222c0   RTKVHDA  RTKVHDA.sys  Tue Jul 06 06:02:40 2010 (4C32FF40)
9d4be000 9d4c8000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
9380d000 93817000   serenum  serenum.sys  Mon Jul 13 19:45:27 2009 (4A5BC717)
8bf47000 8bf61000   serial   serial.sys   Mon Jul 13 19:45:33 2009 (4A5BC71D)
8c207000 8c208480   speedfan speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F)
8c1ff000 8c207000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
9d545000 9d596000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
9d4f6000 9d545000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
9d4c8000 9d4e9000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
943fb000 943fc380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
8c03d000 8c186000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
9d4e9000 9d4f6000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8c379000 8c384000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8c362000 8c379000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8bf74000 8bf84000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
96b70000 96b79000   TSDDD    TSDDD.dll    unavailable (00000000)
928c2000 928e3000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
929cb000 929d9000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
957d7000 957d8700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
943bc000 943cb000   usbehci  usbehci.sys  Fri Oct 23 23:58:55 2009 (4AE27B7F)
929d9000 92a1d000   usbhub   usbhub.sys   Sat Oct 24 00:00:05 2009 (4AE27BC5)
94371000 943bc000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
94366000 94371000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
8ba81000 8ba8c000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8c2f7000 8c303000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8c303000 8c324000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
8c1b7000 8c1bf380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8ba9d000 8baad000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8baad000 8baf8000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
8c1c0000 8c1ff000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8bf61000 8bf74000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8c324000 8c331000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8b97f000 8b9f0000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
8b9f0000 8b9fe000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8c032000 8c039000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
96910000 96b5b000   win32k   win32k.sys   Tue Aug 31 22:34:29 2010 (4C7DBBB5)
8ba46000 8ba4f000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
92a2e000 92a48000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)

Unloaded modules:
be563000 be588000   Rt86win7.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00025000
9d621000 9d68b000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0006A000
94341000 94366000   Rt86win7.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00025000
8c2b7000 8c2c4000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
8c2c4000 8c2cf000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
8c2cf000 8c2d8000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
8c2d8000 8c2e9000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
 


#3
hey i did everything u said. i updated all drivers and stuff,etc... but i still see BSODs.... now it doesnt show win32k.sys or ntfs.sys but mostly it shows MEMORY_MANAGEMENT error code and sometimes no specific error is shown. also an imp thing, just b4 the bsod shows up, all running applications like google chrome,etc and explorer also crash.....pls help.. i'm posting cpu-z screens as well......
 


Attachments

#4
Something's not right with your RAM. Keep attaching for further analysis:

- RAMMON HTML report
- Latest crash dumps

Run 10 passes of memtest.
 


#6
DDR800 will never work well with DDR667. That's why I always ask to attach the memory info:

me said:
If your RAM sticks are set wrong, or if they are mismatching, or not supported by motherboard, your BSOD thread will grow many pages and yet you'll be having crashes. Sorting software and drivers won't help, and memtest will not necessarily detect errors.
DDR2-800 DDR-667
400.00 333.33
6-6-6-18 5-5-5-15
Maximum Skew Between DQS and DQ Signals (ns) 0.200 0.240


What you need to do:

1. Remove the Micron Technology DDR667 stick
2. In the bios, set DRAM 800Mhz 6-6-6-18 1.8v for your DDR2-800 memory module
3. Save the new settings and reboot
 


#7
tried evrything bt nothing seems to work..... attaching new crash dumps.....
 


Attachments

#8
DDR800 will never work well with DDR667. That's why I always ask to attach the memory info:



DDR2-800 DDR-667
400.00 333.33
6-6-6-18 5-5-5-15
Maximum Skew Between DQS and DQ Signals (ns) 0.200 0.240


What you need to do:

1. Remove the Micron Technology DDR667 stick
2. In the bios, set DRAM 800Mhz 6-6-6-18 1.8v for your DDR2-800 memory module
3. Save the new settings and reboot



Have you followed my post?
 


#9
ya i did..... i removed that stick bt bsod stll continued.... i dont know what 2 do now.... pls help.....
 


#10
Well, attach this again so I can see your new setup:

1. CPU-Z memory and CPU tab
2. RAMMON HTML report
 


#11
well it wasnt working so i put the stick back.... its better to use 3gb ram and get bsod rather than..... well...use 1gb ram and get bsod...eh... atleast its not slow:confused:
 


#12
Again, DDR-800 will not work with DDR-667. This is where your blue screens come from. Reinstalling the OS and drivers will NOT help. Remove one of the sticks and enjoy. Or get a new matching pair of RAM and enjoy.


DDR800 will never work well with DDR667. That's why I always ask to attach the memory info:



DDR2-800 DDR-667
400.00 333.33
6-6-6-18 5-5-5-15
Maximum Skew Between DQS and DQ Signals (ns) 0.200 0.240


What you need to do:

1. Remove the Micron Technology DDR667 stick
2. In the bios, set DRAM 800Mhz 6-6-6-18 1.8v for your DDR2-800 memory module
3. Save the new settings and reboot
 


#13
hey i dont think u got it..... i did removed one stick and i sure as hell didnt enjoy..... if the problem was with the compatibility of ram , then removing one stick should hav done the trick... but it didnt.... i dont want to buy a new pair of ram and still be stuck in the same situation........
 


#14
I don't think you're getting me: DDR-800 will not work with DDR-667, alright? It will but with the blue screens as in your case. Why?? Because the sticks cannot work "in unison" side by side as their parameters are different:

DDR2-800 DDR-667
400.00 333.33
6-6-6-18 5-5-5-15
Maximum Skew Between DQS and DQ Signals (ns) 0.200 0.240


----> After removing one of the sticks, you need to adjust the settings for the other remaining stick according to its rated specs:

DDR667 5-5-5-15, if you remove DDR800
DDR800 6-6-6-18, if you remove DDR667

Having done so, you were supposed to attach new CPUZ and Rammon info, you didn't.


Good luck.
 


#15
okay did it again.....how do i change the settings to 6-6-6-18??????
 


#17
hey... i removed the 800mhz 1gig stick and now my comp is running fine and even games are running good..... no bsod since 2 dayz.... thanx for ur help... guess i would hav 2 buy a new 1 gig 667mhz stick.... can u recommend which brand to choose and the approx price range.........
 


#18
At last, sounds good - well done.

If you want more RAM, then make sure the sticks are matching, they should be the same model same brand and from the same batch. Buy a RAM kit and you'll be fine. As for the price range, you might wanna use google.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.