figure this one out

#1
im getting bsod on win7
i have done extensive ram testing everything turned up ok
i have collected the dump files, they give some memory error the first time, altho memory test is ok, the other reports
show the dump files reporting several windows drivers
i have collected also system information, diagnostic information everything you need from windows itself
the dump files are included also in the rar i uploaded
please take a look at the files and tell me whats wrong thanks in advance
peter
View attachment win7.rar
 


Captain Jack

Extraordinary Member
#2
Hello and Welcome !

Seems like the the Dumps are pointing to Core Windows Components. I would recommend to try some basic things. I noticed you have mentioned that once you got some errors in Memory well to be honest even 1 error in Memory can mess things up.

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger

Uninstall Comodo Internet Security make use you run the Cleanup Tool Clean-up tool for Comodo Internet Security

Update the Following Driver

Code:
lirsgt.sys   Sun Mar 07 01:23:01 2004 - TAGES copy protection system
nvoclk64.sys Wed Sep 05 07:56:33 2007
atksgt.sys   Mon Oct 20 13:20:38 2008
Rt64win7.sys Thu Feb 26 14:34:13 2009


Bugcheck:

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

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+1e7952f00a1dfdc
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88005e98888 -- (.exr 0xfffff88005e98888)
ExceptionAddress: fffff88001570000 (volsnap!VspWriteApplicationInfo)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000003
Attempt to read from address 0000000000000003

TRAP_FRAME:  fffff88005e98930 -- (.trap 0xfffff88005e98930)
Unable to read trap frame at fffff880`05e98930

LAST_CONTROL_TRANSFER:  from fffff8000328446e to fffff8000328c710

STACK_TEXT:  
fffff880`05e97978 fffff800`0328446e : 00000000`00000000 fffff880`05e98170 00000000`00000000 fffff800`032e0f6b : nt!KeBugCheck
fffff880`05e97980 fffff800`032b240d : fffff800`03498cf8 fffff800`033dbaf0 fffff800`0321c000 fffff880`05e98888 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`05e979b0 fffff800`032b9a90 : fffff800`033dbae8 fffff880`05e97a28 fffff880`05e98888 fffff800`0321c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`05e979e0 fffff800`032c69ef : fffff880`05e98888 fffff880`05e980f0 fffff880`00000000 fffff8a0`00000004 : nt!RtlDispatchException+0x410
fffff880`05e980c0 fffff800`0328bd82 : fffff880`05e98888 fffffa80`03eca650 fffff880`05e98930 fffffa80`054bb390 : nt!KiDispatchException+0x16f
fffff880`05e98750 fffff800`0328a8fa : 00000000`00000000 fffffa80`03eca650 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`05e98930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`0328446e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
Hope this helps,
Captain
 


#3
Uninstall Daemon Tools in the normal method. Then use this installer/uninstaller to carefully remove sptd.sys from the system:

DuplexSecure - Downloads

Reboot when done. Of course, update the old drivers too.

Also uninstall the software which belongs to this driver, to rid it:

hmonitor45 hmonitor45.sys Sat Jul 26 09:29:37 2008
 


#4
thank you for everyone who gave me an answer i have carefully tried every suggestion
and the system seems to be stable again
obviously some sort of driver conflict altho a bad case!!
peter
 


#5
btw really nice that you help each other out cause you bring this to the computer store and they charge you a leg.....
peter
 


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