A lot of BSODs

Shbitzik · 08 Jun 2011

Hi,
I'm having a lot of problems with my computer lately.

Started having blue screen, all involving ntoskrnl.dll with diffrent bug strings. thought it was because of my hard drive (ran mem check and it turned ok), replaced it, installed new windows 7, blue screens stoped for a while, then came back.
I've extracted 2 of my 2gb sticks. tried to work only with the remaining two. blue screens continue.

I've attached my Dump files.
Any help you can give is appreciated.

my system specs:
-Windows 7 Ultimate 64bit
-Intel Core 2 Duo E8400
-Gigabyte EP43-DS3L
-2gb *4 Dimm DDR2 800Mhz
-Nvidia GeForce 9800GT 1G
-Seagate Barracuda 1TB 7200 RPM 32MB Cache

tnx,
Shbitzik

yowanvista · 08 Jun 2011

Your Eset Antivirus is the cause, remove it and use MSE

Information

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.

Code:

sptd.sys        fffff880`0108a000    fffff880`011ec000    0x00162000    0x4ceba9d9    23/11/2010 15:47:37

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

POOL_CORRUPTION_IN_FILE_AREA (de)
A driver corrupted pool memory used for holding pages destined for disk.
This was discovered by the memory manager when dereferencing the file.
Arguments:
Arg1: 0000000000000002
Arg2: fffff8a00ccd7b90
Arg3: bffff8a00ccd7b91
Arg4: 000000005bc6a8c0

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xDE

PROCESS_NAME:  ekrn.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c7f49d to fffff80002cc8d00

STACK_TEXT:  
fffff880`0a94b4f8 fffff800`02c7f49d : 00000000`000000de 00000000`00000002 fffff8a0`0ccd7b90 bffff8a0`0ccd7b91 : nt!KeBugCheckEx
fffff880`0a94b500 fffff800`02c97542 : 00000000`00000000 fffffa80`04677a00 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2d8a1
fffff880`0a94b5f0 fffff880`014d451b : fffffa80`046e5f68 00000000`00000000 fffff8a0`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`0a94b660 fffff880`014f5033 : fffff880`07d506f0 fffff8a0`0c5f74a0 fffff8a0`042aabc0 fffff880`0a94b968 : Ntfs!NtfsDeleteFile+0x57b
fffff880`0a94b8e0 fffff880`01463cc9 : fffffa80`067abe40 fffffa80`085a06c0 fffff880`07d50650 fffffa80`06af2060 : Ntfs!NtfsCommonCleanup+0x1653
fffff880`0a94bcf0 fffff800`02cc0817 : fffff880`07d50650 00000000`003c2500 00000000`77a745c0 00000000`00000000 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`0a94bd20 fffff800`02cc07d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`07d50520 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2d8a1
fffff800`02c7f49d cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2d8a1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d8a1

BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d8a1

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

Shbitzik · 08 Jun 2011

tnx for the reply,

I've uninstalled my NOD and installed MSE instead, and downloaded an update for my daemon tools which stated:

Issues addressed:
- Fixed BSODs during file copy on some systems.

do you think it will help? or should i remove daemon tools entirely?

and, i have been using nod for quite some time (almost 2 years). why all of the sudden it began causing blue screens? should i get a fresh install, or a diffrent version? will it fix the problem?

again, thank you very much.
i'm putting my additional RAM back in.

yowanvista · 08 Jun 2011

Shbitzik said:

tnx for the reply,

I've uninstalled my NOD and installed MSE instead, and downloaded an update for my daemon tools which stated:

Issues addressed:
- Fixed BSODs during file copy on some systems.

do you think it will help? or should i remove daemon tools entirely?

and, i have been using nod for quite some time (almost 2 years). why all of the sudden it began causing blue screens? should i get a fresh install, or a diffrent version? will it fix the problem?

again, thank you very much.
i'm putting my additional RAM back in.

That Tool will remove sptd.sys which is used by Deamon tools
Any antivirus can cause BSODs at any time regardless of it being good or not

Shbitzik · 14 Jun 2011

no more blue screens
problem solved

thank you very much

Shbitzik · 14 Jun 2011

i guess i've talked to soon,
this morning the flash player prompt for an update, installed it and the screen went black, now computer starts, nothing on the screen, then after 1 min or so, restart itself and hence forth.

i've again extracted 2 of my ram sticks, and turned on pc again. it went on normally and after some casual browsing it froze, (with a loud noise from my speakers, instead of the song), and it went back to on and off.

what should i do?

yowanvista · 15 Jun 2011

Shbitzik said:

i guess i've talked to soon,
this morning the flash player prompt for an update, installed it and the screen went black, now computer starts, nothing on the screen, then after 1 min or so, restart itself and hence forth.

i've again extracted 2 of my ram sticks, and turned on pc again. it went on normally and after some casual browsing it froze, (with a loud noise from my speakers, instead of the song), and it went back to on and off.

what should i do?

Can you boot in safemode with networking? If so run a scan of Malwarebytes

Shbitzik · 15 Jun 2011

everything is clean.

are you certain it's not hardware related?

Shbitzik · 17 Jun 2011

a new blue screen regarding dxgmms1.sys.

dump file attached

yowanvista · 18 Jun 2011

Your Nvidia driver needs to be reinstalled
Uninstall current version then use Driver Sweeper to remove leftover Nvidia driver files
Then reboot and install latest Nvidia driver(275.33)

NVIDIA DRIVERS 275.33 WHQL

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff88003b974cd, The address that the exception occurred at
Arg3: fffff880086b2618, Exception Record Address
Arg4: fffff880086b1e70, 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: 
dxgmms1!memmove+bd
fffff880`03b974cd 488941e0        mov     qword ptr [rcx-20h],rax

EXCEPTION_RECORD:  fffff880086b2618 -- (.exr 0xfffff880086b2618)
ExceptionAddress: fffff88003b974cd (dxgmms1!memmove+0x00000000000000bd)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880086b1e70 -- (.cxr 0xfffff880086b1e70)
rax=0000000000010287 rbx=fffffa8009053000 rcx=bffff8a0020ce230
rdx=400001e006f85d98 rsi=0000000000000001 rdi=fffffa8009053d94
rip=fffff88003b974cd rsp=fffff880086b2858 rbp=fffffa8009f971c0
 r8=0000000000000030  r9=0000000000000001 r10=0000000000000000
r11=bffff8a0020ce210 r12=fffffa8009053238 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!memmove+0xbd:
fffff880`03b974cd 488941e0        mov     qword ptr [rcx-20h],rax ds:002b:bffff8a0`020ce210=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

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:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f11100
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!memmove+bd
fffff880`03b974cd 488941e0        mov     qword ptr [rcx-20h],rax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88003bad3cb to fffff88003b974cd

STACK_TEXT:  
fffff880`086b2858 fffff880`03bad3cb : fffffa80`0000001a fffffa80`08fe50d0 00000000`00000000 fffff880`009e5180 : dxgmms1!memmove+0xbd
fffff880`086b2860 fffff880`03ba579d : 00000000`00000000 fffffa80`09f99000 00000000`0000001c 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x1a3
fffff880`086b28d0 fffff880`03bbf65d : 00000000`00000000 fffff8a0`0266e620 fffffa80`00000000 fffffa80`09f971c0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd09
fffff880`086b2aa0 fffff880`03bbf398 : fffff800`00b96080 fffff880`03bbed00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`086b2c90 fffff880`03bbee96 : 00000000`00000000 fffffa80`07125170 00000000`00000080 fffffa80`0901e010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`086b2cc0 fffff800`02f7e32e : 00000000`02674cf2 fffffa80`09052060 fffffa80`06a1f040 fffffa80`09052060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`086b2d00 fffff800`02cd3666 : fffff800`02e54e80 fffffa80`09052060 fffff800`02e62cc0 fffff880`01211cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`086b2d40 00000000`00000000 : fffff880`086b3000 fffff880`086ad000 fffff880`086b2640 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!memmove+bd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff880086b1e70 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!memmove+bd

BUCKET_ID:  X64_0x7E_dxgmms1!memmove+bd

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