BSOD-Kernel-Power 41 error during sleep mode/Debug=Ksthunk.sys

[mackado]

Dell Xps 435t (12-2010 built)
Corsair 650W PSU,(installed a year ago)
win7 SP1 Home premium
i7 920 @ 2.7Ghz CPU,
6 Gig DDR3,
Radeon 5770 Video (installed a year ago)
M-Audio- Audiophile 2496 Audio.
Wacom Intuos Tablet







I'm hoping someone here could help me solve this issue without having to re-install W7 from scratch.


Basically for close to a month now this system is crashing while on Sleep mode or when coming out of 'Sleep mode', then reboots and generates a BSOD , then shuts down.


'Event viewer' reports Kernel-Power 41 error (minidump attached below)


I downloaded and installed MS debugger and managed to run it on several generated Memory.dmp files and with my limited knowledge I believe they point to error loading system file Ksthunk.sys, with one other past minidump pointing to ntoskrnl.exe.


I've done the following troubleshooting


disable AMD HD audio device (included with Radeon, read it might conflict with M-audio drivers)
Upgraded all drivers
reseated and checked all memory chips at mobo
Ran a memory test using Memtest86 (v4.20)at boot up (default test) 4 times =no errors
and finally ran several chkdsk checks/repair from W7. (it reboots into chkdsk before loading W7)


After running CHKDSK 'event viewer' logged a couple of NTFS HDD errors, I thought this was the problem and that it was fixed by chkdsk, but just today the system crashed in sleep mode with kernel-power 41 error again, although the HDD has not logged any other NTFS errors since last chkdsk/repair.


So now I'm thinking maybe the SYS files in question were moved to a new location by CHKDSK but these file(s) are corrupt and need replacing?


Any ideas/suggestions on what to do next?


Ps I'm including the latest memory.dmp file


View attachment 186067

View attachment 186068

 

[zigzag3143]

Dell Xps 435t (12-2010 built)
Corsair 650W PSU,(installed a year ago)
win7 SP1 Home premium
i7 920 @ 2.7Ghz CPU,
6 Gig DDR3,
Radeon 5770 Video (installed a year ago)
M-Audio- Audiophile 2496 Audio.
Wacom Intuos Tablet







I'm hoping someone here could help me solve this issue without having to re-install W7 from scratch.


Basically for close to a month now this system is crashing while on Sleep mode or when coming out of 'Sleep mode', then reboots and generates a BSOD , then shuts down.


'Event viewer' reports Kernel-Power 41 error (minidump attached below)


I downloaded and installed MS debugger and managed to run it on several generated Memory.dmp files and with my limited knowledge I believe they point to error loading system file Ksthunk.sys, with one other past minidump pointing to ntoskrnl.exe.


I've done the following troubleshooting


disable AMD HD audio device (included with Radeon, read it might conflict with M-audio drivers)
Upgraded all drivers
reseated and checked all memory chips at mobo
Ran a memory test using Memtest86 (v4.20)at boot up (default test) 4 times =no errors
and finally ran several chkdsk checks/repair from W7. (it reboots into chkdsk before loading W7)


After running CHKDSK 'event viewer' logged a couple of NTFS HDD errors, I thought this was the problem and that it was fixed by chkdsk, but just today the system crashed in sleep mode with kernel-power 41 error again, although the HDD has not logged any other NTFS errors since last chkdsk/repair.


So now I'm thinking maybe the SYS files in question were moved to a new location by CHKDSK but these file(s) are corrupt and need replacing?


Any ideas/suggestions on what to do next?


Ps I'm including the latest memory.dmp file


View attachment 186067

View attachment 186068

These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver (perhaps audiodg) 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. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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

 

[mackado]

Thanks, I'll re-check the memory again for a longer period and see, I already burnt the ISO of memtest86 yesterday and ran the boot test for 3 plus hours with no erros.

I'll see about that 'driver scanner' util, I read mixed reviews..

Any tips on how to find audiodg.exe to reinstall it?

 

[mackado]

Ran memtest for 12 hours overnight , 10 passes, no errors found

Installed and ran Driver Verifier as instructed, it mainly finds Intel Mobo outdated drivers only. I'll check by Dell, since I rather not upgrade these type of drivers from other sources.

After setting up Driver verifier as instructed and clicking on all non-ms loaded drivers and rebooting, system crashes and goes into a reboot-loop without generating any BSOD. Had to boot into 'safe mode' to stop/disable driver verifier.

Checked Minidump folder and no new 'dump file' was created, same for the memory.dmp file that loads under root C: directory. only the old ones posted here.

 

[mackado]

I thought the problem was resolved after the SFC scan even though it reported 'errors with some files could not be recovered" but my sys crashed again in sleep mode with Kernel-power 41 error.

Last thing I need to try is a full SFC scan from the boot drive but the "recovery disc" created will not reach the 'Recovery options' splash screen, it freezes and then displays error 0x4001100200001012.

This error apparently has to do with some bug in Dell computers according to this MS link on the issue

Windows 7 repair disk error code 0x4001100200001012 - Microsoft Answers

My Dell W7 install disc apparently is only for re-installations according to the label on it. and I don't know if the OEM original "recovery" partition is going to work now since I upgrade W7 with SP1.

 

[mackado]

Any other way to run the SFC scan?

Can I use a DOS boot thumb drive I created with help in this forum (Win98)to run SFC at boot in a Win7 system?

PS:I previously neglected to include the correct BSOD file format, here are the correct ones with the latest BSOD info.

View attachment 187232

View attachment 187233