Windows 7 Continued BSoD Issues with ntokrnl.exe: Seeking Assistance After Driver Updates

P

pman860507

New Member
Joined
Sep 20, 2010
Messages
84
i posted previously about bsod and i got excellent help. i was able to update my drivers and fix 99% of the problem. i am still having one issue. since 9-25-10 i have had 4 BSoD caused by ntokrnl.exe. its pretty random it seems they are happening either during the night hours or when im trying to use it remotely in the morning. i will attach all 4 of my dump files but im just really not sure what to do.
View attachment Minidump1.rar

Thanks.
 
Solution
I see a few possible problems.

Start out by removing Daemon Tools, or whatever other CD virtualization or ISO program you are using. It uses a driver, SPTD.sys, that has been causing crashes since Vista.

Remove SPTD when you're done, with this tool: Link Removed due to 404 Error

Remove Gigabyte's Easy Saver program:
Code: 
gdrv.sys     Thu Mar 12 23:22:29 2009
It too has been causing BSODs.

If the crashes persist, enable driver verifier: Driver Verifier - Enable and Disable - Windows 7 Forums

Post any new dumps you may get.

...Summary of the Dumps:
Code: 
[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct  5 03:02:24.308 2010 (UTC - 4:00)
System Uptime: 0 days 4:54:26.196
BugCheck...
Sort by date Sort by votes
I see a few possible problems.

Start out by removing Daemon Tools, or whatever other CD virtualization or ISO program you are using. It uses a driver, SPTD.sys, that has been causing crashes since Vista.

Remove SPTD when you're done, with this tool: Link Removed due to 404 Error

Remove Gigabyte's Easy Saver program:
Code: 
gdrv.sys     Thu Mar 12 23:22:29 2009
It too has been causing BSODs.

If the crashes persist, enable driver verifier: Driver Verifier - Enable and Disable - Windows 7 Forums

Post any new dumps you may get.

...Summary of the Dumps:
Code: 
[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct  5 03:02:24.308 2010 (UTC - 4:00)
System Uptime: 0 days 4:54:26.196
BugCheck 50, {89152b0, 0, 7fef53b4c63, 8}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43017 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 30 14:20:04.866 2010 (UTC - 4:00)
System Uptime: 0 days 5:46:10.770
BugCheck 19, {3, fffff8a0054ac460, fffff8a0054ac460, fffff8a0054ac450}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 29 10:59:08.014 2010 (UTC - 4:00)
System Uptime: 0 days 2:23:39.902
BugCheck 109, {a3a039d8997166c0, b3b7465eebee38b6, fffff80003519ef0, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 25 14:22:15.758 2010 (UTC - 4:00)
System Uptime: 0 days 2:54:20.646
BugCheck 1000007E, {ffffffffc0000005, fffff80002f140a2, fffff880009a9868, fffff880009a90d0}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
 
Upvote 0 Downvote
Solution
After uninstalling Daemon Tools, you'll need to use the installer/uninstaller found here to remove sptd.sys. Be careful to uninstall as opposed to update:

Link Removed

This driver is also an issue:

PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009

Navigate to C:\Windows\System32\drivers and delete it. Reboot and then run Ccleaner to clean the registry.

Update your very old Bluetooth driver from motherboard or other manufacturer's website:

BtHidBus BtHidBus.sys Wed Jan 07 10:29:05 2009

Definitely uninstall TeamViewer as it is eay too old to run well on Windows 7:

teamviewervpn teamviewervpn.sys Thu Dec 13 04:22:09 2007

----------

Do all that and you should be fine. Other than that, Driver Verifier isn't necessary as I can easily see all problem drivers by eye.

Enjoy and good luck. Post new crashes after doing all the above, if necessary.
 
Upvote 0 Downvote
i removed Daemon tools the last time i had this issue but no one said anything about the program to remove sptd thank i have gotten rid of that. i also believe i have removed Gigabyte's Easy Saver program.

TorrentG said
Update your very old Bluetooth driver from motherboard or other manufacturer's website:

BtHidBus BtHidBus.sys Wed Jan 07 10:29:05 2009

not really sure how to do this since i didnt even know i had a bluetooth device. the only thing i have not done is uninstall teamviewer yet. i need to find a good replacement before i can actually remove it.

and then tonight i got another BSoD and here is the dump file.
View attachment 100510-16660-01.rar
 
Upvote 0 Downvote
Time to enable driver verifier: Driver Verifier - Enable and Disable - Windows 7 Forums

Those are Windows drivers:
Code: 
bthport.sys  [B]Mon Jul 13 20:06:56 2009[/B] (4A5BCC20)
No need to worry about those.

Just update Teamviewer; remove whatever old version you are using, and install the latest one. I use TeamViewer, and I know I don't have that version of the driver on my machine.

...Summary of the Dumps:
Code: 
[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct  5 22:08:28.446 2010 (UTC - 4:00)
System Uptime: 0 days 3:24:31.335
BugCheck 1A, {31, fffffa8006e29660, fffff8800c5a4000, fffff8a00aa98a40}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+6368 )
BUGCHECK_STR:  0x1a_31
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
 
Upvote 0 Downvote

i updated teamviewer to 5.1.9220 i am using the host version my my pc.

on the driver verifier topic it says
5. Click on "Provider" at the top to sort the list by manufacturer. Select all drivers not provided by Microsoft Corporation. The only other drivers that do not get selected are amdxata.sys, and secdrv.sys.
Click to expand...

does this apply to me also since you stated that they were windows drivers that were causing it?
 
Upvote 0 Downvote
Uninstall TeamViewer completely, as I've said. When bsods stop, then you can reinstall anything you want...and can know if what you did caused it:

teamviewervpn teamviewervpn.sys Thu Dec 13 04:22:09 2007

And update Bluetooth software however you can.

BtHidBus BtHidBus.sys Wed Jan 07 10:29:05 2009

Bsods will not stop until you do these things.
 
Upvote 0 Downvote
pman860507 said:
i updated teamviewer to 5.1.9220 i am using the host version my my pc.

on the driver verifier topic it says


does this apply to me also since you stated that they were windows drivers that were causing it?
Click to expand...
The dump blamed Windows drivers; we know that is not the true cause though. It just means that the debugger can't find a better cause.
 
Upvote 0 Downvote
i did the verifer and all it did was give me BSoD when ever i tried to boot normal so i booted into safe mode and removed all the settings i also uninstalled teamviewer. and i am currently looking for my bluetooth driver update. also here are the dump files. from the last 2

View attachment Minidump.rar
 
Upvote 0 Downvote
TorrentG- these are Windows 7 drivers, the Bluetooth ones:
Code: 
BthEnum.sys  Mon Jul 13 20:06:52 2009
[B]BtHidBus.sys Wed Jan 07 10:29:05 2009[/B]
bthpan.sys   Mon Jul 13 20:07:00 2009
bthport.sys  Mon Jul 13 20:06:56 2009
BTHUSB.sys   Mon Jul 13 20:06:52 2009
Check out the July 13, 2009 timestamp.

The OP will have a heck of a time finding updates for these, unfortunately.

The bold driver is 3rd-party; check on your computer manufacturer's site for an update.

Still, I seriously doubt that is the issue. Verifier did not cause them to fail. I have to suspect a hardware problem.

Check RAM: RAM - Test with Memtest86+ - Windows 7 Forums

Test CPU: CPU - Stress Test with Prime95 - Windows 7 Forums

Temporarily remove Perfect Disk; I don't know if this could be causing anything.

...Summary of the Dumps:
Code: 
[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 17:27:28.553 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:27.083
BugCheck A, {fffff8000337bc06, 2, 0, fffff800031047a2}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 11:14:28.866 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:36.395
BugCheck A, {7240112, 2, 0, fffff800030a52b3}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
 
Upvote 0 Downvote
i have been looking everywhere for the bluetooth driver. but i cant find it also didnt know i had a bluetooth in my computer. here are my most recent dump files. its really random it ran find for 3 days and then i walk to the computer and see BSoD

Thanks for all the help i really appreciate it.

View attachment Minidump1.rar
 
Upvote 0 Downvote
You're having hardware based errors with PerfectDisk involved now:

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032af0e0
 000000fffff7fd23 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeQueryValuesProcess+a0
fffff800`03046dba 488b8120fdffff  mov     rax,qword ptr [rcx-2E0h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  PDAgent.exe
Code: 
STACK_COMMAND:  kb

FOLLOWUP_IP: 
volsnap!StorSqmInitialize+100
fffff880`01188890 c07448488b      sal     byte ptr [rax+rcx*2+48h],8Bh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  volsnap!StorSqmInitialize+100

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_volsnap.sys

BUCKET_ID:  X64_IP_MISALIGNED_volsnap.sys

Followup: MachineOwner
---------
Uninstall PerfectDisk then run chkdsk /r command from an elevated command prompt. If errors continue, then it could be a RAM defect.
 
Upvote 0 Downvote

will do i got as far as doing the cpu test last night which didnt bring back any errors. i will uninstall perfect disk and run the check disk. thanks. let you know what i come up with.
 
Upvote 0 Downvote
1) Update the video card driver:

atikmdag atikmdag.sys Wed Aug 25 21:47:22 2010

Link Removed

2) I would uninstall VirtualBox as it is likely responsible.

3) Instead of 2, you're welcome to run Driver Verifier to see if new crash dumps show the exact cause and then post if/when they happen. Here's how:

Link Removed
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Question Question
Windows 7 Troubleshooting Screen Issues with Microsoft Flight Simulator after Driver Update
Replies
1
Views
948
Saltgrass
X
  • Solved
Windows 7 PC Boot Issues and Blue Screen Errors After Driver Update
Replies
1
Views
1K
patcooke