BSOD ntoskrnl.exe =(

BBMorti · 13 Jul 2010

Another humble and desperate hope for help..

I have a crash dump analyzis here.

On Tue 13-07-2010 09:56:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x3, 0xFFFFF880065FE1D0, 0xFFFFF080065FE1D0, 0xFFFFF880065FE1D0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\071310-15381-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Fri 09-07-2010 18:23:32 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x3, 0xFFFFF80002C4D7B0, 0xFFFFF80002C4D7B0, 0xFFFFFA0002C4D7B0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\070910-16177-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Fri 09-07-2010 17:47:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x20000000028, 0x2, 0x1, 0xFFFFF80002ACB328)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\070910-16848-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Wed 07-07-2010 17:33:41 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA80096B47E0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Dump file: C:\Windows\Minidump\070710-16536-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

My screens happens only when the computer is under "stress" Meaning when I play game or I am doing rendering if that is important information. Especially the game Dragon Age Origins is bad.. My system is very new and it does my tummy no good to have problems sigh.

The one who can help me out I will visit and cook a good dinner for

ttran · 13 Jul 2010

Can you please post your actual crash dump file
https://www.sevenforums.com/crashes-d...tructions.html

BBMorti · 13 Jul 2010

Yes I was waiting for the thread to be approved so I could do it.. here you go.
Please let me know if I need to translate a word somewhere

ttran · 13 Jul 2010

I suspect the graphic card, please download and install fresh copy of the driver, then please run this free stress test:
FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Another thing I want to mention
In looking through your drivers, I can see 2 things:

Code:

:
     ASACPI   ASACPI.sys   Mon Mar 28 09:30:36 2005 (42476C4C)

It's date from 2005 has been known for causing BSOD, please update it right away following this instruction:
https://www.sevenforums.com/787431-post2.html

Virtual CD program such as Deamon tool or Alcohol 120% are known for causing BSODs. Please remove them now for testing purpose. Then use this tool to remove sptd.sys, which is the component of those program that can't be removed by simple uninstall.
DuplexSecure - Downloads

Code:

:
     sptd     sptd.sys     Mon Oct 12 03:55:14 2009 (4AD24632)

You can reinstall them later if it's not the cause
BUGCHECK SUMMARY:

Code:

BugCheck 50, {fffffaa01e9e1940, 0, fffff8800500b145, 5}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+33b145 )

Followup: MachineOwner
---------
BugCheck C4, {91, 2, fffffa80096b47e0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )

Followup: MachineOwner
---------
BugCheck 19, {3, fffff80002c4d7b0, fffff80002c4d7b0, fffffa0002c4d7b0}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )

Followup: Pool_corruption
---------
BugCheck A, {20000000028, 2, 1, fffff80002acb328}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2e8 )

Followup: MachineOwner
---------
BugCheck 19, {3, fffff880065fe1d0, fffff080065fe1d0, fffff880065fe1d0}

Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )

Followup: Pool_corruption
---------

BBMorti · 13 Jul 2010

Thank you sir!

I updated my gfx drivers a few days ago to the newest catalyst 10.6.. removed all the old drivers with Driver Sweeper. Rebooted and installed the fresh new ones.. is that process sufficient and should I repeat it or?

I will follow your other advices emidiately, I get a little nervous about the Furmark program since they post boasting images of gfx-cards that is fried.. also the download I see in your link is 'DOWNLOAD FurMark v1.8.2 - Windows XP / Vista 32-bit (2010.04.19)' But I run windows 7 64bit version.. Do they have one for that or?

Im just nervous since its such a new system.. I am baffled I even have 2005 drivers, thank god for the expertise of friendly others!

BBMorti · 13 Jul 2010

Update:

Ok so I have updated the asacpi.sys as guided and now when I check my windows/system32 folder I see That two files by that name now is from 2009 but a third by the same name is from 2005 still.

C:\windows\system32\drivers (a 2009 version)
C:\windows\system32\driverstore\filerepository\..... (a 2009 version)
C:\windows\system32\driverstore\filerepository\..... (a 2005 version)

So it updated but left one there? :x

Then I went to duplexSecure and downloaded the program for 64bit and ran it as administrator.. it gave me the choises to 'Update' or 'uninstall' or 'cancel' .. I tried update since it said I didn't have the newest version and then it asked me to reboot.. after rebooting I ran the program again and it gave me the three same choises and this time said that the same version (1.69) was detected and proceeded to give me the same three choises.. how should I proceed? Or did I do what I should already?..
Note: This was done after removing Daemon Lite as was said I should.

Still waiting for feedback about what version of Furmark to use and maybe something to put my poor heart at peace after having seem them boasting about frying gfx cards.. few days ago I sweeped and updated to newest official drivers as part of my own troubleshooting as mentioned.

BBMorti · 13 Jul 2010

I guess I will check in tomorrow..

ttran · 13 Jul 2010

For the duplexsecure, please choose the uninstall option to remove sptd.sys. It caused your BSOD. As I mentioned earlier, remove Deamon tool first, then use the Duplexsecure to remove sptd.sys. A lot of users thought that they update the sptd.sys, it's wrong.
For the Furmak thing, please download and use the newest version of it, no need one for win7, vista and xp is ok. Make sure to follow the instruction I gave you earlier, step by step.
I'm not sure why You still have the 2005 one in your system. Did you download the right one? In the article I sent you, it said that the driver is about 8th item down, however, it might be 10th or 11th, make sure to double check the name that article mentioned. I think I can double check the date in next crash dump if possible

Regard,

Tuan

BBMorti · 14 Jul 2010

Thank you sir, I will do as mentioned and return with feedback. Karma given

Edit: Yes I did download the correct one and it did update.. but for some reason it left one of them there from 2005.. I now have three files with the same name two updated (2009) and a third from 2005.. I dont know what to do about that one.

BBMorti · 14 Jul 2010

I ran the driver verifier as described in this thread on the forum --> Using Driver Verifier to identify issues with Drivers

Until I reached my next BSOD.. should I upload Newest memory dump file?..