BSOD STOP 0x000001E on Start Up only


Joined
Jun 29, 2011
Messages
14
Reaction score
1
Hi guys, I'm experiencing a * STOP 1E* kind of BSOD. Strangely enough this occurs only when I boot my PC. After that, I enter in the recovery menu trying to correct the boot sequence. Doing so, the PC starts correctly in the second time. The problem appears again in the next “fresh” start up of the system in the next day.
I’m attaching the mini dump file, so if anyone can help me, please this is making me crazy!

My PC is relatively new, (less than six months) and its configurations is as follow:
MOBO: Gygabyte 880GM-UD2H
CPU: Phenom II X6 1090T
MEM: 8Gb Kingston (budget ones)
VGA: nVidia GTS 250 1Gb
PSU: 600W Thermaltake (not sure the model)
HD1: 160Gb Samsung (the oldest piece of the config)
HD2: 500Gb Seagate
Optical drives: 2 Samsung writemaster DVD burners
Multi flash memory card reader

Thanks for any help!
 

Attachments

Ad

Advertisements

Elmer BeFuddled

Resident eejit
VIP Member
Joined
Jun 12, 2010
Messages
1,050
Reaction score
251
Hi st230.

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED.
Usual causes:
Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Your latest dump file lists ataport.SYS as the probable cause. This is a Windows System file and for it to be the cause of your crash is highly unlikely.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes. Random stop codes often indicate hardware issues.


As a Priority:

sptd.sys Tue Nov 23 11:47:37 2010 The sptd.sys driver is notorious for causing BSOD's with Windows 7. It's a driver used and installed along with Daemon Tools and Alcohol 120 which you'll also have to uninstall.
Then use the correct (32bit or 64bit) download from Duplex Secure - Downloads to uninstall the SPTD.SYS driver.
Make sure to select the uninstall button! DO NOT SELECT INSTALL!!


Outdated Drivers. Update:

AtiPcie.sys Tue May 05 16:00:22 2009 ATI PCIE Chipset Driver. Go to Mobo Mfr. or AMD


Bugcheck Analysis:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : ataport.SYS ( ataport!PortListRemoveRequest+22 )

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

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 
+3161373564613636
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880032cc708 -- (.exr 0xfffff880032cc708)
ExceptionAddress: fffff880011e2eb6 (ataport!PortListRemoveRequest+0x0000000000000022)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880032cc7b0 -- (.trap 0xfffff880032cc7b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007c9a290 rbx=0000000000000000 rcx=fffffa8007a53440
rdx=fffffa800802c040 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011e2eb6 rsp=fffff880032cc948 rbp=fffffa8007a533d0
 r8=fff7fa800802cbb0  r9=fffffa8008028bb0 r10=fffffa8007a3d620
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ataport!PortListRemoveRequest+0x22:
fffff880`011e2eb6 49894008        mov     qword ptr [r8+8],rax ds:fb02:fff7fa80`0802cbb8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c825fe to fffff80002c8ac10

STACK_TEXT:  
fffff880`032cb7e8 fffff800`02c825fe : 00000000`00000000 00000000`00000000 fffff880`032cbf60 fffff800`02cb6830 : nt!KeBugCheck
fffff880`032cb7f0 fffff800`02cb64fd : fffff800`02e9471c fffff800`02dd1c30 fffff800`02c0e000 fffff880`032cc708 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`032cb820 fffff800`02cb52d5 : fffff800`02dd50fc fffff880`032cb898 fffff880`032cc708 fffff800`02c0e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`032cb850 fffff800`02cc6361 : fffff880`032cc708 fffff880`032cbf60 fffff880`00000000 fffffa80`07a53440 : nt!RtlDispatchException+0x415
fffff880`032cbf30 fffff800`02c8a2c2 : fffff880`032cc708 00000000`0000000b fffff880`032cc7b0 00000000`00000014 : nt!KiDispatchException+0x135
fffff880`032cc5d0 fffff800`02c88bca : 00000000`000049d1 fffff800`02ca6237 00000000`00000011 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`032cc7b0 fffff880`011e2eb6 : fffff880`011e395c 00000000`0000000a 00000000`00000014 fffffa80`07a53440 : nt!KiGeneralProtectionFault+0x10a
fffff880`032cc948 fffff880`011e395c : 00000000`0000000a 00000000`00000014 fffffa80`07a53440 00000000`00000000 : ataport!PortListRemoveRequest+0x22
fffff880`032cc950 fffff880`011e3755 : 00000000`00000014 00000000`00000002 00000000`00000000 fffff8a0`02540000 : ataport!TransferRequestsToQueue+0x34
fffff880`032cc980 fffff880`011db20e : 00000000`00000001 fffffa80`07a531b0 fffffa80`07a533d0 fffffa80`08028010 : ataport!PortAvioSchedulerTransferBatch+0x171
fffff880`032cc9c0 fffff880`011dd59a : 00000000`00000000 00000000`00000000 fffffa80`07a531b0 fffffa80`08028010 : ataport!IdeStartNextDeviceRequest+0x66
fffff880`032cca60 fffff880`011dd104 : fffffa80`07a3c1a0 00000000`00000000 fffffa80`07a3c1a0 fffffa80`08028010 : ataport!IdeProcessCompletedRequests+0x26a
fffff880`032ccb90 fffff880`00e5b0cc : fffffa80`069df000 00000000`00000000 fffffa80`07a3c118 fffffa80`07a3c100 : ataport!IdePortCompletionDpc+0x1a8
fffff880`032ccc50 fffffa80`069df000 : 00000000`00000000 fffffa80`07a3c118 fffffa80`07a3c100 00000000`00000010 : sptd+0x460cc
fffff880`032ccc58 00000000`00000000 : fffffa80`07a3c118 fffffa80`07a3c100 00000000`00000010 00000000`00000246 : 0xfffffa80`069df000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!PortListRemoveRequest+22
fffff880`011e2eb6 49894008        mov     qword ptr [r8+8],rax

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  ataport!PortListRemoveRequest+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79293

FAILURE_BUCKET_ID:  X64_0x1E_0_ataport!PortListRemoveRequest+22

BUCKET_ID:  X64_0x1E_0_ataport!PortListRemoveRequest+22

Followup: MachineOwner
Drivers:
Code:
fffff880`01079000 fffff880`010d0000   ACPI     ACPI.sys     Sat Nov 20 09:19:16 2010 (4CE79294)
fffff880`01400000 fffff880`01489000   afd      afd.sys      Mon Apr 25 03:33:58 2011 (4DB4DD96)
fffff880`045e6000 fffff880`045fb000   amdppm   amdppm.sys   Tue Jul 14 00:19:25 2009 (4A5BC0FD)
fffff880`01059000 fffff880`01064000   amdxata  amdxata.sys  Fri Mar 19 16:18:18 2010 (4BA3A3CA)
fffff880`04494000 fffff880`0449c000   AppleCharger AppleCharger.sys Tue Apr 27 04:54:05 2010 (4BD65FDD)
fffff880`01050000 fffff880`01059000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`011d1000 fffff880`011fb000   ataport  ataport.SYS  Sat Nov 20 09:19:15 2010 (4CE79293)
fffff880`01889000 fffff880`01891000   AtiPcie  AtiPcie.sys  Tue May 05 16:00:22 2009 (4A005486)
fffff880`0165c000 fffff880`01663000   Beep     Beep.SYS     Tue Jul 14 01:00:13 2009 (4A5BCA8D)
fffff880`04483000 fffff880`04494000   blbdrive blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF)
fffff880`018c7000 fffff880`018f1000   cdrom    cdrom.sys    Sat Nov 20 09:19:20 2010 (4CE79298)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Sat Nov 20 13:12:36 2010 (4CE7C944)
fffff880`01859000 fffff880`01889000   CLASSPNP CLASSPNP.SYS Sat Nov 20 09:19:23 2010 (4CE7929B)
fffff880`00cea000 fffff880`00d48000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01508000 fffff880`0157a000   cng      cng.sys      Sat Nov 20 10:08:45 2010 (4CE79E2D)
fffff880`01891000 fffff880`0189f000   crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
fffff880`04400000 fffff880`04483000   csc      csc.sys      Sat Nov 20 09:27:12 2010 (4CE79470)
fffff880`013d1000 fffff880`013ef000   dfsc     dfsc.sys     Sat Nov 20 09:26:31 2010 (4CE79447)
fffff880`045d7000 fffff880`045e6000   discache discache.sys Tue Jul 14 00:37:18 2009 (4A5BC52E)
fffff880`01843000 fffff880`01859000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`018ab000 fffff880`018b4000   dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`0189f000 fffff880`018ab000   dump_dumpata dump_dumpata.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`018b4000 fffff880`018c7000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
fffff880`01064000 fffff880`01078000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
fffff880`00faf000 fffff880`00ffb000   fltmgr   fltmgr.sys   Sat Nov 20 09:19:24 2010 (4CE7929C)
fffff880`0158b000 fffff880`01595000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
fffff880`01809000 fffff880`01843000   fvevol   fvevol.sys   Sat Nov 20 09:24:06 2010 (4CE793B6)
fffff880`01b00000 fffff880`01b4a000   fwpkclnt fwpkclnt.sys Sat Nov 20 09:21:37 2010 (4CE79321)
fffff800`031f7000 fffff800`03240000   hal      hal.dll      Sat Nov 20 13:00:25 2010 (4CE7C669)
fffff880`01800000 fffff880`01809000   hwpolicy hwpolicy.sys Sat Nov 20 09:18:54 2010 (4CE7927E)
fffff800`00bd2000 fffff800`00bdc000   kdcom    kdcom.dll    Sat Feb 05 16:52:49 2011 (4D4D8061)
fffff880`014ed000 fffff880`01508000   ksecdd   ksecdd.sys   Sat Nov 20 09:21:15 2010 (4CE7930B)
fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Sat Nov 20 10:10:34 2010 (4CE79E9A)
fffff880`00cc9000 fffff880`00cd6000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Jul 14 02:29:09 2009 (4A5BDF65)
fffff880`011b7000 fffff880`011d1000   mountmgr mountmgr.sys Sat Nov 20 09:19:21 2010 (4CE79299)
fffff880`0162b000 fffff880`0165c000   MpFilter MpFilter.sys Wed Apr 06 21:07:29 2011 (4D9CC801)
fffff880`017ef000 fffff880`017fa000   Msfs     Msfs.SYS     Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`010d0000 fffff880`010da000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
fffff880`0148f000 fffff880`014ed000   msrpc    msrpc.sys    Sat Nov 20 09:21:56 2010 (4CE79334)
fffff880`045cc000 fffff880`045d7000   mssmbios mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE)
fffff880`01be8000 fffff880`01bfa000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
fffff880`01693000 fffff880`01786000   ndis     ndis.sys     Sat Nov 20 09:23:30 2010 (4CE79392)
fffff880`04514000 fffff880`04523000   netbios  netbios.sys  Tue Jul 14 01:09:26 2009 (4A5BCCB6)
fffff880`044a0000 fffff880`044e5000   netbt    netbt.sys    Sat Nov 20 09:23:18 2010 (4CE79386)
fffff880`01786000 fffff880`017e6000   NETIO    NETIO.SYS    Sat Nov 20 09:23:13 2010 (4CE79381)
fffff880`015ba000 fffff880`015cb000   Npfs     Npfs.SYS     Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`045c0000 fffff880`045cc000   nsiproxy nsiproxy.sys Tue Jul 14 00:21:02 2009 (4A5BC15E)
fffff800`02c0e000 fffff800`031f7000   nt       ntkrnlmp.exe Thu Jun 23 03:53:23 2011 (4E02AAA3)
fffff880`0122e000 fffff880`013d1000   Ntfs     Ntfs.sys     Fri Mar 11 03:39:39 2011 (4D79997B)
fffff880`018f1000 fffff880`018fa000   Null     Null.SYS     Tue Jul 14 00:19:37 2009 (4A5BC109)
fffff880`044ee000 fffff880`04514000   pacer    pacer.sys    Sat Nov 20 10:52:18 2010 (4CE7A862)
fffff880`0111a000 fffff880`0112f000   partmgr  partmgr.sys  Sat Nov 20 09:20:00 2010 (4CE792C0)
fffff880`010e7000 fffff880`0111a000   pci      pci.sys      Sat Nov 20 09:19:11 2010 (4CE7928F)
fffff880`011a0000 fffff880`011a7000   pciide   pciide.sys   Tue Jul 14 00:19:49 2009 (4A5BC115)
fffff880`011a7000 fffff880`011b7000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`0157a000 fffff880`0158b000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
fffff880`00cd6000 fffff880`00cea000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
fffff880`0456f000 fffff880`045c0000   rdbss    rdbss.sys    Sat Nov 20 09:27:51 2010 (4CE79497)
fffff880`01681000 fffff880`0168a000   RDPCDD   RDPCDD.sys   Tue Jul 14 01:16:34 2009 (4A5BCE62)
fffff880`0168a000 fffff880`01693000   rdpencdd rdpencdd.sys Tue Jul 14 01:16:34 2009 (4A5BCE62)
fffff880`017e6000 fffff880`017ef000   rdprefmp rdprefmp.sys Tue Jul 14 01:16:35 2009 (4A5BCE63)
fffff880`01bae000 fffff880`01be8000   rdyboost rdyboost.sys Sat Nov 20 09:43:10 2010 (4CE7982E)
fffff880`00f80000 fffff880`00faf000   SCSIPORT SCSIPORT.SYS Sat Nov 20 10:34:01 2010 (4CE7A419)
fffff880`04523000 fffff880`04540000   serial   serial.sys   Tue Jul 14 01:00:40 2009 (4A5BCAA8)
fffff880`01ba6000 fffff880`01bae000   spldr    spldr.sys    Mon May 11 17:56:27 2009 (4A0858BB)
fffff880`00e15000 fffff880`00f77000   sptd     sptd.sys     Tue Nov 23 11:47:37 2010 (4CEBA9D9)
fffff880`018fc000 fffff880`01b00000   tcpip    tcpip.sys    Tue Jun 21 04:33:55 2011 (4E001123)
fffff880`015ed000 fffff880`015fa000   TDI      TDI.SYS      Sat Nov 20 09:22:06 2010 (4CE7933E)
fffff880`015cb000 fffff880`015ed000   tdx      tdx.sys      Sat Nov 20 09:21:54 2010 (4CE79332)
fffff880`0455b000 fffff880`0456f000   termdd   termdd.sys   Sat Nov 20 11:03:40 2010 (4CE7AB0C)
fffff880`01200000 fffff880`01226000   tunnel   tunnel.sys   Sat Nov 20 10:51:50 2010 (4CE7A846)
fffff880`010da000 fffff880`010e7000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
fffff880`01663000 fffff880`01671000   vga      vga.sys      Tue Jul 14 00:38:47 2009 (4A5BC587)
fffff880`01595000 fffff880`015ba000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B)
fffff880`01000000 fffff880`0103c000   vmbus    vmbus.sys    Sat Nov 20 09:57:29 2010 (4CE79B89)
fffff880`01b4a000 fffff880`01b5a000   vmstorfl vmstorfl.sys Sat Nov 20 09:57:30 2010 (4CE79B8A)
fffff880`0112f000 fffff880`01144000   volmgr   volmgr.sys   Sat Nov 20 09:19:28 2010 (4CE792A0)
fffff880`01144000 fffff880`011a0000   volmgrx  volmgrx.sys  Sat Nov 20 09:20:43 2010 (4CE792EB)
fffff880`01b5a000 fffff880`01ba6000   volsnap  volsnap.sys  Sat Nov 20 09:20:08 2010 (4CE792C8)
fffff880`04540000 fffff880`0455b000   wanarp   wanarp.sys   Sat Nov 20 10:52:36 2010 (4CE7A874)
fffff880`01671000 fffff880`01681000   watchdog watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F)
fffff880`00d48000 fffff880`00dec000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
fffff880`00dec000 fffff880`00dfb000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`044e5000 fffff880`044ee000   wfplwf   wfplwf.sys   Tue Jul 14 01:09:26 2009 (4A5BCCB6)
fffff880`0103c000 fffff880`01050000   winhv    winhv.sys    Sat Nov 20 09:20:02 2010 (4CE792C2)
fffff880`013ef000 fffff880`013f8000   wmiacpi  wmiacpi.sys  Tue Jul 14 00:31:02 2009 (4A5BC3B6)
fffff880`00f77000 fffff880`00f80000   WMILIB   WMILIB.SYS   Tue Jul 14 00:19:51 2009 (4A5BC117)
Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.


HTH.
 

bassfisher6522

VIP Member
Joined
Feb 9, 2010
Messages
748
Reaction score
126
What are your system specs? Do you have an AMD formerly ATI GPU installed? The reason I'm asking, I went through some thing very very similar to what you described in you post. In my case, the offending culprit was indeed hardware and it turned out to be my GPU. I had some old but good hardware in storage and started parts swapping. I started with the CPU, then my memory and finally the GPU. The cause of the GPU failure was an overheating problem, it was so hot that I couldn't remove it right away, I had to let the system cool off for an hour just to handle it. Since then I have taken apart the GPU and thoroughly inspected it and found it clogged with lent and dust on the heat sink which was so bad it was not allowing the unit to vent properly.
 

zigzag3143

Wanikiya
Microsoft MVP
Joined
Sep 22, 2010
Messages
268
Reaction score
110
Hi guys, I'm experiencing a * STOP 1E* kind of BSOD. Strangely enough this occurs only when I boot my PC. After that, I enter in the recovery menu trying to correct the boot sequence. Doing so, the PC starts correctly in the second time. The problem appears again in the next “fresh” start up of the system in the next day.
I’m attaching the mini dump file, so if anyone can help me, please this is making me crazy!

My PC is relatively new, (less than six months) and its configurations is as follow:
MOBO: Gygabyte 880GM-UD2H
CPU: Phenom II X6 1090T
MEM: 8Gb Kingston (budget ones)
VGA: nVidia GTS 250 1Gb
PSU: 600W Thermaltake (not sure the model)
HD1: 160Gb Samsung (the oldest piece of the config)
HD2: 500Gb Seagate
Optical drives: 2 Samsung writemaster DVD burners
Multi flash memory card reader

Thanks for any help!
Please tell us what sleep states your computer supports by running powercfg -a from a command prompt (start>search>right click and run as admin>powercfg -1

Also what version of GPU driver is installed?
 
Joined
Jun 29, 2011
Messages
14
Reaction score
1
Please tell us what sleep states your computer supports by running powercfg -a from a command prompt (start>search>right click and run as admin>powercfg -1

Also what version of GPU driver is installed?
Hello again guys. Excuse the delay but I've been travelling.

Well, answering all questions:

1 - My GPU is the described before nVidia Geforce GTS 250 1Gb (not AMD bassfisher6522)

2 - I've disabled the hibernate long ago, kepping only the suspension mode.

3 - I've updated the nvidia display drivers yesterday to the new one (280.26), and also the Daemon Tools to the SPTD 1.78 (since Elmer said it is a possible BSOD source)

After that, I had no more BSOD's on start up, but its a little to soon to guarantee.

Anyway, thanks for the help guys! I'll be doing some more testing and if the problem has been gone I'm going to come back here to the final notes.

Thanks!
 
Joined
Jun 29, 2011
Messages
14
Reaction score
1
Well, it seems tha the problem has gone. Apparently it was the SPTD indeed.

Thanks again Elmer! You saved me twice since I bought this PC!

Hello again guys. Excuse the delay but I've been travelling.

Well, answering all questions:

1 - My GPU is the described before nVidia Geforce GTS 250 1Gb (not AMD bassfisher6522)

2 - I've disabled the hibernate long ago, kepping only the suspension mode.

3 - I've updated the nvidia display drivers yesterday to the new one (280.26), and also the Daemon Tools to the SPTD 1.78 (since Elmer said it is a possible BSOD source)

After that, I had no more BSOD's on start up, but its a little to soon to guarantee.

Anyway, thanks for the help guys! I'll be doing some more testing and if the problem has been gone I'm going to come back here to the final notes.

Thanks!
 
Ad

Advertisements

Joined
Jun 29, 2011
Messages
14
Reaction score
1
Hello again!

It seems that the problem returns. Now I had a “STOP 0x0000024”. Again, this happens only on the start up.

The BSOD have not appeared for a while since I have updated the Daemon Tools virtual drive software, but then again it started to happen.

My PC stills the same:
MOBO: Gigabyte 880GM-UD2H
CPU: Phenom II X6 1090T
MEM: 8Gb Kingston (budget ones)
VGA: nVidia GTS 250 1Gb
PSU: 600W Thermaltake (not sure the model)
HD1: 160Gb Samsung (the oldest piece of the config)
HD2: 500Gb Seagate
Optical drives: 2 Samsung writemaster DVD burners
Multi flash memory card reader

Here is the minidump. Do you think that the problem can be Daemon tools related? I’ll disable it the next time I have a BSOD to test.
 

Attachments

Elmer BeFuddled

Resident eejit
VIP Member
Joined
Jun 12, 2010
Messages
1,050
Reaction score
251
STOP 0x00000024: NTFS_FILE_SYSTEM
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

This ones blaming your Ntfs.sys file. But you still have an sptd driver showing, although it's updated. Cannot stress enough that this needs to be removed from your system.

sptd.sys Sun Feb 27 19:29:52 2011 Use the correct (32bit or 64bit) download from Duplex Secure - Downloads to uninstall the SPTD.SYS driver.
Make sure to select the uninstall button! DO NOT SELECT INSTALL!!

After running the above tool to remove the sptd.sys driver, do a search to see if you can find it. If you happen to, rename it sptd.old. That will break it and prevent it from loading.

If you were using DT for drive emulation (virtual drives) I can recommend DVDFab Free, it's compact and resource light and can emulate up to 18 drives, I believe (one's enough for me!).


 
Last edited:

zigzag3143

Wanikiya
Microsoft MVP
Joined
Sep 22, 2010
Messages
268
Reaction score
110
Hardly befuddled, Elmer is right as usual. SPTD.SYS is often a cause of BSOD's

If after removing it you still are experiencing BSOD's please do the following.

Do what ELMER says first

Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org/#downiso

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier


I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
 
Ad

Advertisements

Joined
Jun 29, 2011
Messages
14
Reaction score
1
Thank you guys for all the support!

For now, the BSOD's stopped again after the SPTD removal. If it happens again, then I'll do these tests.

Cheers!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top