Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: dxgkrnl.sys BSODs

30 Jan 2010   #11
usasma
Microsoft MVP

 
 

None of the BSOD's are Driver Verifier Enabled Memory Dumps.
They are 4 memory dumps with 4 different error messages and 4 different reasons.
As such I'd have to assume that this is a hardware problem or a Windows problem (and that Driver Verifier won't do a thing for this type of error - although it won't hurt to run it).

So, start with these diagnostics:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

*****
Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS
And, check your file system:
Quote:
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Then, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall/remove:
Quote:
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Code:
StarOpen.SYS Tue Jun 27 15:15:56 2006 - AT&T, Verizon, and/or Virgin mobile phone driver file.
Rtnicxp.sys  Mon Mar 31 01:41:05 2008 - Realtek Network driver
adfs.SYS     Thu Aug 14 10:57:15 2008 - Adobe File System driver
Summary of the BSOD's:
Code:
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Tue Jan 26 15:31:31.173 2010 (GMT-5)
System Uptime: 0 days 11:05:59.140
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck D1, {5d, 2, 1, 919e076f}
Probably caused by : kbdclass.sys ( kbdclass!KeyboardClassServiceCallback+2c7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Jan 29 14:32:46.027 2010 (GMT-5)
System Uptime: 0 days 3:59:16.993
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, 8325afc6, 9b0aabec, 0}
Probably caused by : hardware ( nt+223fc6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Jan 29 16:33:26.176 2010 (GMT-5)
System Uptime: 0 days 1:59:29.752
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Jan 29 18:27:10.256 2010 (GMT-5)
System Uptime: 0 days 0:13:59.223
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT



My System SpecsSystem Spec
.
08 Feb 2010   #12
diliantraikov

Windows 7 Ultimate 32 bit
 
 

Hi I'm back. I ran everything and no errors were found. I haven't written all this time because I thought the problem was solved cause I remembered that after I followed the advice of the guy in this thread I had plugged my network cable in the faulty jack. The thing is I have two jack where I can plug the cable and the guy from the forum said that the network adapter was causing them. Guess he was right but now even when I again returned the cable to the proper jack the bsods still occur. The thing is that in 7 of the 11 bsods BlueScreenView points that one of the faulty drivers is ntkrnlpa.exe. I've uploaded the minidump folder if it can be of any help. I'm getting really fed up with this as for the 5 months in which I have had my computer I have spent 2 repairing it. Please drop a line if you know what's going on.
My System SpecsSystem Spec
11 Feb 2010   #13
usasma
Microsoft MVP

 
 

Please let us know where you obtained your copy of Windows 7 from. It has a different code number than most, and the Microsoft Symbol Server doesn't recognize it.

I'm guessing here, but I'd blame (if we rule out hardware):
- Asus utilities (AIBooster, ASACPI.SYS, ASIO.sys etc) - I recommend uninstalling all Asus utilities that are installed on your system.
- Avast! Antivirus:
Quote:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Avast from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Avast using this free tool: http://www.avast.com/eng/avast-uninstall-utility.html
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
- networking drivers - download the latest drivers from the network card chipset manufacturer's website, uninstall the current drivers, then install the freshly downloaded drivers.

Please remove these drivers from you system:
Quote:
adfs.SYS Thu Aug 14 10:57:15 2008 - Adobe
AsIO.sys Mon Dec 17 04:10:20 2007 - Asus utility
Please ensure that Driver Verifier is turned off.

Summary of the BSOD's:
Code:
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Sat Jan 30 17:21:18.877 2010 (GMT-5)
System Uptime: 0 days 0:07:51.828
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for AsInsHelp32.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Sat Jan 30 17:52:20.808 2010 (GMT-5)
System Uptime: 0 days 0:00:24.384
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Sat Jan 30 18:07:17.144 2010 (GMT-5)
System Uptime: 0 days 0:12:11.095
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Sun Jan 31 06:06:14.238 2010 (GMT-5)
System Uptime: 0 days 0:34:18.189
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Sun Jan 31 08:48:49.871 2010 (GMT-5)
System Uptime: 0 days 0:32:15.822
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck A, {c065c058, 2, 0, 82abbdca}
*** WARNING: Unable to verify timestamp for ACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+3d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Mon Feb  1 05:06:39.172 2010 (GMT-5)
System Uptime: 0 days 0:32:51.123
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, 82b5d04d, 9bf5a6bc, 0}
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+2aa7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Mon Feb  1 05:52:01.654 2010 (GMT-5)
System Uptime: 0 days 0:44:12.605
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
BugCheck 1000008E, {c0000005, 8bee4541, 94df371c, 0}
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
*** WARNING: Unable to verify timestamp for aswRdr.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswRdr.SYS
Probably caused by : hardware ( tdx!TdxConnectConnection+3f7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Feb  5 14:56:29.726 2010 (GMT-5)
System Uptime: 0 days 9:00:02.676
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
BugCheck D1, {14, 2, 1, 8be89d6e}
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
Probably caused by : tdx.sys ( tdx!TdxSendDatagramTransportAddress+204 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Fri Feb  5 15:17:36.444 2010 (GMT-5)
System Uptime: 0 days 0:19:57.004
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000008E, {c0000005, 8b9bcf04, 8dd20df7, 0}
Probably caused by : hardware ( SCSIPORT!SpProcessCompletedRequest+591 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Sat Feb  6 07:19:59.937 2010 (GMT-5)
System Uptime: 0 days 3:18:05.888
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
BugCheck D1, {0, 2, 0, 8be88baf}
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
Probably caused by : tdx.sys ( tdx!TdxSendDatagramTransportAddress+204 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.20576.x86fre.win7_ldr.091115-1505
Debug session time: Mon Feb  8 10:10:49.010 2010 (GMT-5)
System Uptime: 0 days 4:15:22.961
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck A, {7d2e4d6c, 2, 1, 82a9757f}
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : ntkrnlpa.exe ( nt+7a57f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
My System SpecsSystem Spec
.

11 Feb 2010   #14
ickymay

win7 ultimate / virtual box
 
 

system specs filled out would be useful
My System SpecsSystem Spec
12 Feb 2010   #15
diliantraikov

Windows 7 Ultimate 32 bit
 
 

I uninstalled avast and installed Avira but I can't figure out how to remove the ASUS utilities (as they don't appear in Add or Remove Programs), AsIO.sys and adfs.sys. I downloaded Driver Genius even before some of the bsods and it updated the network drivers. I downloaded my Windows 7 from a torrent tracker. As it needs registration to view any torrents here is the title of the torrent : "Windows 7 Ultimate Retail English (x86) (MSDN/TechNet)". As for the system specs I wrote some of them in the beginning of the thread. I can check if youre asking about something specific. Driver Verifier is off because when I run it and restart the computer, it can't start and I have to launch System Repair which then deletes the settings.
My System SpecsSystem Spec
12 Feb 2010   #16
usasma
Microsoft MVP

 
 

To remove adfs.sys - uninstall all Adobe products on your system.
To remove ASIO.sys - you'll have to burrow through Device Manager to find which System Device is using that file

Another method (but it may break the programs that the drivers are associated with) is to stop the drivers from loading by using this free program: Autoruns for Windows
Just look in the Drivers tab and remove the check mark next to the driver to stop it from loading.

Once that's done, post back if any further BSOD's occur.
My System SpecsSystem Spec
13 Feb 2010   #17
diliantraikov

Windows 7 Ultimate 32 bit
 
 

I stopped ASIO.sys and I couldn't find the adfs but that is maybe because Adobe Photoshop and Adobe Flash were uninstalled during the windows installation. But 3 hours later again a BSoD occured... Here's the crash dump.
My System SpecsSystem Spec
13 Feb 2010   #18
usasma
Microsoft MVP

 
 

ASIO isn't stopped, it was loaded with this one. adfs.sys didn't show up tho'

1. Make a restore point (and have your installation DVD handy)
2. Search your hard drive for AsIO.sys.
3. Rename each and every instance to AsIO.BAK
4. Reboot and see if the driver loads (check msinfo32.exe...Software Environment...both "System Drivers" and "Loaded modules")

Here's the older drivers loaded in this one:
Code:
AsIO.sys     Mon Dec 17 04:10:20 2007 - Asus PCProbe Utility - Driver Reference
kbfiltr.sys  Wed Jan 24 05:08:39 2007 - Dritek HotKey Keyboard  Filter Driver by Dritek System Inc  (Dritek Website).  No drivers available at their website.
Rtnicxp.sys  Mon Mar 31 01:41:05 2008 - Realtek 10/100/1000 NDIS 5.1 Driver - Driver Reference
The AsIO.sys is common to all the memory dumps - so that's the most critical one now.

Also, please try Driver Verifier according to these directions:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users


Here's a summary of the BSOD:
Code:
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sat Feb 13 11:41:34.057 2010 (GMT-5)
System Uptime: 0 days 17:37:24.008
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck A, {0, 2, 1, 82b0fe7f}
Probably caused by : ntkrnlpa.exe ( nt+c2e7f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
My System SpecsSystem Spec
13 Feb 2010   #19
diliantraikov

Windows 7 Ultimate 32 bit
 
 

After the BSoD I found a folder named ASUS in Program Files and in it there was and uninstallation file so I ran it and deleted the folder. Now I can't find AsIO anywhere in C. I followed the steps for driver verifier and after I restarted the computer restarted on the Starting Windows screen. So now I'm writing from the Safe Mode with Networking.
My System SpecsSystem Spec
13 Feb 2010   #20
usasma
Microsoft MVP

 
 

Any new memory dumps (since you started Driver Verifier)? If so, please upload them.
My System SpecsSystem Spec
Reply

 dxgkrnl.sys BSODs




Thread Tools




Similar help and support threads
Thread Forum
Lock ups and BSODs dxgkrnl.sys NDProxy.SYS
Hi all, been getting lock ups and BSODs on win XP for a while and presumed it just needed reinstalling as it was several years old, however I took the oportunity to move to W7 (fresh install not upgrade) and I'm still having problems. It will either lock up or BSOD at random, it has happend...
BSOD Help and Support
Random BSODs: ntoskrnl, dxgkrnl, dxgmms1, nvlddmkm, BCCode 116
Hi Guys. I'd appreciate some help here. I've been getting BSODs for quite a while now and would like some help in finding a solution. Attached is my SF zip. Looking at the dmp files, it seems it's either ntoskrnl or (dxgkrnl, dxgmms1, nvlddmkm). I have no idea what this means.
BSOD Help and Support
directx BSODs - dxgmms1.sys and dxgkrnl.sys
I recently built myself a new computer, with the following specs: i5 3750k, asrock z77 extreme4, 8GB Gskill sniper low voltage (model F3-12800CL9D-8GBSR2, two sticks of 4GB). I have an OCZ SSD (which isnt being used for windows at all, so, the specs arent important) and a WD caviar black...
BSOD Help and Support
BSODs Atikmpag.sys / Atikmdag.sys / dxgkrnl.sys
Hello. I keep getting chrashes that either a) causes the screen to make the screen picture reset itself with the error message like "Display driver AMD driver stopped responding and has successfully recovered". B) causes my screen to go crazy with pixels and colours before chrashing into BSOD....
BSOD Help and Support
New Build BSODS:dxgkrnl
I just put together a new PC and am getting some strange BSOD's and errors involving dxgkrnl. If you need any more info please ask. Here are my dumps. Thanks for the help in advance.
BSOD Help and Support
Seemingly Random dxgkrnl.sys BSODs
Hello. After a few months of no problems thanks to some great people on this forum I'm having problems again. In the past few days I've had at least 4 blue screens. Remembering what someone recommended I uninstalled my video card drivers, used Driver Sweeper to get rid of any remnants, and...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:22.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App