BSOD : ntoskrnl.exe / 0x00000019

[nighty]

Hello.

I've had this blue screen for some time now.

All my drivers are up-to-date.
memory check, no problem.

windows 7 64 reinstalled 2 weeks ago everything was working perfectly but today the blue screen came back while playing.

At first 3 games crash then the blue screen in game.

i've attached everything asked, i really can't pinpoint the problem.

 

[nighty]

No clues ? could it be a GPU problem ? is there any memtest for graphic cards ?

i'm pretty stuck here

 

[wish]

Hi,
Your dmp bugcheck BAD_POOL_HEADER (19) = could be RAM faulty or bad drivers.

Remove Alcohol or Daemon software because they use sptd.sys which is notorious for causing BSOD in windows 7.
Uninstall sptd.sys with this tools --> DuplexSecure - Downloads

Test your RAM with memtest86 for at least 7 passes.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Update these drivers:

iaStor.sys   Thu Jun 04 18:53:40 2009 -> [URL="http://downloadcenter.intel.com/Default.aspx"]Intel Storage driver[/URL]
Rt64win7.sys Fri May 22 07:52:30 2009 ->[URL="http://www.realtek.com.tw/downloads/"] Realtek NIC driver [/URL]
sptd.sys     Sun Oct 11 13:55:14 2009  -> uninstall it

Log

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {22, 1000000000000, 0, 0}

GetPointerFromAddress: unable to read from fffff800030c50e0
GetUlongFromAddress: unable to read from fffff800030331b0
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )

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

 

[nighty]

First of all : thank you.

I've updated : Realtek NIC driver
and : Intel Storage driver from intel matrix storage to intel rapid storage (seems like intel changed the name...)

I'm going to wait to see if I get more blue screen before I uninstall deamon tools (I use it on a daily basis)

 

[nighty]

New blue screen (black screen actually) with : 0x00000124 that usually means an hardware malfunction no ?

GTX 470 issue - NVIDIA Forums - Page 2

 

[zigzag3143]

New blue screen (black screen actually) with : 0x00000124 that usually means an hardware malfunction no ?

GTX 470 issue - NVIDIA Forums - Page 2

Yep it is hardware.

Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks


Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\120210-9562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Thu Dec  2 06:53:57.947 2010 (GMT-5)
System Uptime: 0 days 0:00:04.993
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80086772a8, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80086772a8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`035706f0 fffff800`0310aa89 : fffffa80`08677280 fffffa80`05526680 00000000`00000015 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03570c10 fffff800`02fec667 : fffffa80`08677280 fffff800`030655f8 fffffa80`05526680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03570c40 fffff800`02f54c45 : fffff800`030c7360 fffffa80`08397828 fffffa80`08397820 fffffa80`05526680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03570c80 fffff800`02ecd961 : fffff880`0151ae00 fffff800`02f54c20 fffffa80`05526680 00440042`004b0009 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03570cb0 fffff800`03164c06 : 004c004c`0044002e fffffa80`05526680 00000000`00000080 fffffa80`0550a040 : nt!ExpWorkerThread+0x111
fffff880`03570d40 fffff800`02e9ec26 : fffff880`0336a180 fffffa80`05526680 fffff880`033750c0 00440042`004b000b : nt!PspSystemThreadStartup+0x5a
fffff880`03570d80 00000000`00000000 : fffff880`03571000 fffff880`0356b000 fffff880`0300d690 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

7: kd> lmtsmn
start             end                 module name
fffff880`010c5000 fffff880`0111c000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`014df000 fffff880`014ea000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`01491000 fffff880`0149a000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0149a000 fffff880`014c4000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00d2f000 fffff880`00def000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`0108e000 fffff880`010be000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00cd1000 fffff880`00d2f000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01200000 fffff880`01273000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`019ee000 fffff880`019fc000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0161b000 fffff880`01631000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0440b000 fffff880`0441e000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`04201000 fffff880`0440b000   dump_iaStor dump_iaStor.sys Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff880`01536000 fffff880`0154a000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`014ea000 fffff880`01536000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01611000 fffff880`0161b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01054000 fffff880`0108e000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01800000 fffff880`0184a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02e07000 fffff800`02e50000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`01864000 fffff880`0186d000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`01287000 fffff880`01491000   iaStor   iaStor.sys   Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff800`00bc9000 fffff800`00bd3000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`017d9000 fffff880`017f3000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`019c3000 fffff880`019ee000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`00c79000 fffff880`00cbd000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`01000000 fffff880`0101a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`014c4000 fffff880`014cf000   msahci   msahci.sys   Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0111c000 fffff880`01126000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0154a000 fffff880`015a8000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01852000 fffff880`01864000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01871000 fffff880`01963000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01963000 fffff880`019c3000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff800`02e50000 fffff800`0342c000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01636000 fffff880`017d9000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01166000 fffff880`0117b000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`01133000 fffff880`01166000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`014cf000 fffff880`014df000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01600000 fffff880`01611000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00cbd000 fffff880`00cd1000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0101a000 fffff880`01054000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`00c00000 fffff880`00c2f000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`0184a000 fffff880`01852000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`00ecc000 fffff880`00ff2000   spuh     spuh.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`01a00000 fffff880`01bfd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`01126000 fffff880`01133000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`0117b000 fffff880`01190000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01190000 fffff880`011ec000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`015a8000 fffff880`015f4000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`00e19000 fffff880`00ebd000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ebd000 fffff880`00ecc000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ff2000 fffff880`00ffb000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Mini Kernel Dump does not contain unloaded driver list