BSOD Windows 7 [[re: ...timestamp for ntkrnlpa.exe]]

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Ultimate
       #1

    BSOD Windows 7 [[re: ...timestamp for ntkrnlpa.exe]]


    Hi all. Thanks for providing this wonderful forum 1st of all. Much appreciation for that.

    I'm having an issue with a recent fresh install of Windows 7 Ultimate. BSOD sporadically during reboot, sometimes in the middle of a task pc will simply shut down then when I try booting again I see the blue screen. Perhaps 30 minutes later I'm able to reboot cleanly when I see the following Windows message.

    Code:
    Problem signature:
      Problem Event Name:	BlueScreen
      OS Version:	6.1.7600.2.0.0.256.1
      Locale ID:	1033
    
    Additional information about the problem:
      BCCode:	c000021a
      BCP1:	8BE600A8
      BCP2:	00000000
      BCP3:	C0000001
      BCP4:	00100400
      OS Version:	6_1_7600
      Service Pack:	0_0
      Product:	256_1
    A little bit about my PC:
    • Dual core Compaq Intel Pentium 3.0 GHz
    • 225 GB harddrive
    • 3 GB RAM
    • 32-bit Windows 7 Ultimate

    I've read one of the .dmp files which reads in part the following:

    Code:
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    I have no idea what that means though to be honest. I'm pretty novice when it comes to pc upkeep or whatever... So.... I've attached the zipped up minidump folder and will appreciate assistance to get this issue fixed!

    Thanks in advance

    Jacquii.
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    Most likely the ntkrnlpa.exe error is due to improper symbols being loaded (or not loading at all) when running WinDbg. I didn't get that error when I ran your memory dump files.

    That being said, there still isn't a whole bunch of useful information in the memory dump files.
    FWIW - most times these sort of errors are due to malware - so I'd suggest running a couple of these free, online scans to rule that out: Malware

    Also, please remove or update 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 OR remove:
    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.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer 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:
    e100b325.sys Fri Nov 16 13:53:32 2007 - Intel(R) PRO/100 Adapter NDIS 5.1 driver - http://www.carrona.org/dvrref.html#e100b325.sys
    VSTBS23.SYS  Wed Oct 15 20:30:15 2008 - HSF_HWB2 WDM driver - http://www.carrona.org/dvrref.html#VSTBS23.SYS
    VSTCNXT3.SYS Wed Oct 15 20:29:13 2008 - SoftK56 Modem Driver - http://www.carrona.org/dvrref.html#VSTCNXT3.SYS
    VSTDPV3.SYS  Wed Oct 15 20:32:04 2008 - SoftK56 Modem Driver - http://www.carrona.org/dvrref.html#VSTDPV3.SYS
    If the BSOD's don't stop after all of that, then please run Driver Verifier according to these directions:
    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).

    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
    Summary of the BSOD's:
    Code:
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Thu May 13 04:58:21.578 2010 (GMT-4)
    System Uptime: 0 days 0:00:22.510
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Thu May 13 03:30:31.552 2010 (GMT-4)
    System Uptime: 0 days 0:00:18.408
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Wed May 12 23:35:58.854 2010 (GMT-4)
    System Uptime: 0 days 0:00:23.883
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Wed May 12 19:20:47.839 2010 (GMT-4)
    System Uptime: 0 days 0:00:12.480
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Wed May 12 18:20:32.028 2010 (GMT-4)
    System Uptime: 0 days 0:00:11.668
    PROCESS_NAME:  wininit.exe
    BUGCHECK_STR:  0xF4_5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Wed May 12 17:28:49.664 2010 (GMT-4)
    System Uptime: 0 days 0:00:15.927
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Tue May 11 17:01:16.744 2010 (GMT-4)
    System Uptime: 0 days 0:00:13.384
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Mon May 10 05:26:33.354 2010 (GMT-4)
    System Uptime: 0 days 0:00:12.994
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
      My Computer


  3. Posts : 9
    Windows 7 Ultimate
    Thread Starter
       #3

    Thanks for your quick response! I actually have ESET Smart Security installed - I ran a scan just yesterday and no malware, pups, trojans, etc... were found - So I don't really think this issue has anything to do with malware.

    I've checked via Device Manager and it seems that all my drivers are up to date.

    I've just had another BSOD earlier - see the attached file. Is there anything else to be done for such an error? I'd really like to get this remedied.

    Code:
    Problem signature:
      Problem Event Name:	BlueScreen
      OS Version:	6.1.7600.2.0.0.256.1
      Locale ID:	1033
    
    Additional information about the problem:
      BCCode:	c000021a
      BCP1:	93FB6EF0
      BCP2:	00000000
      BCP3:	C0000001
      BCP4:	00100400
      OS Version:	6_1_7600
      Service Pack:	0_0
      Product:	256_1
    Also - is there a way to fix that WinDbg error?

    Thanks again

    Jacquii.
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    Device Manager is not accurate when it comes to dating of drivers.
    At a minimum you'll have to update your Intel wifi driver - as the one that was loaded when the crash happened was from 2007. And Intel has updated this driver many times since then.

    I would suggest checking to see if your ESET is malfunctioning (sometimes it will cause these problems also). To do this, please follow these instructions:
    Anti-Virus Removal:
    Please do the following:
    - download a free antivirus for testing purposes: Free AntiVirus
    - uninstall the ESET Smart Security from your system (you can reinstall it, if so desired, when we're done troubleshooting)
    - remove any remnants of ESET Smart Security using this free tool: ESET Knowledgebase - How do I manually uninstall my ESET security product?
    - IMMEDIATELY install and update the free antivirus
    - check to see if this fixes the BSOD's
    Other than that, please follow the advice in my first post, then follow the advice in this post and we'll have a good shot at fixing it.

    Summary of the BSOD:
    Code:
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Debug session time: Fri May 14 00:55:51.193 2010 (GMT-4)
    System Uptime: 0 days 0:00:17.222
    BUGCHECK_STR:  0xc000021a_0
    PROCESS_NAME:  smss.exe
      My Computer


  5. Posts : 9
    Windows 7 Ultimate
    Thread Starter
       #5

    Thanks so much Mr. Cranky Pants :P
    I appreciate you taking the time to advise! I will follow your directions when I get over my hangover lol

    Jacquii.
      My Computer


  6. Posts : 9
    Windows 7 Ultimate
    Thread Starter
       #6

    I've found out ((perhaps - don't quote me on it)) that HP is not offering Windows 7 driver updates for Compaq Presario sr5050nx -- see Software & Driver Downloads Compaq Presario SR5050NX Desktop PC - HP Customer Care (United States - English)

    Seems that HP is doing the same for various other systems as well which I think is a bogus practice. Why on earth would they not want customers who have spent substantial money on their product to be able to update their os??? Makes no sense to me. I know there's a lot of disgruntled HP customers as you can see at Windows 7 drivers for Pavilion dv9000 - That's one thread of many...

    At anyrate - Software & Driver Downloads Compaq Presario SR5050NX Desktop PC - HP Customer Care (United States - English) does list downloads for Vista... Would I be able to install any of those updated drivers on my windows 7 since they might be newer than the current driver(s) I have installed?

    Please advise. And thanks again

    Jacquii.
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    MsJacquiiC said:
    I've found out ((perhaps - don't quote me on it)) that HP is not offering Windows 7 driver updates for Compaq Presario sr5050nx -- see Software & Driver Downloads Compaq Presario SR5050NX Desktop PC - HP Customer Care (United States - English)

    Seems that HP is doing the same for various other systems as well which I think is a bogus practice. Why on earth would they not want customers who have spent substantial money on their product to be able to update their os??? Makes no sense to me. I know there's a lot of disgruntled HP customers as you can see at Windows 7 drivers for Pavilion dv9000 - That's one thread of many...

    At anyrate - Software & Driver Downloads Compaq Presario SR5050NX Desktop PC - HP Customer Care (United States - English) does list downloads for Vista... Would I be able to install any of those updated drivers on my windows 7 since they might be newer than the current driver(s) I have installed?

    Please advise. And thanks again

    Jacquii.

    You can use the vista drivers IF you install them in compatibility mode. to do that right click the installer>properties>compatibility>vista

    Let us know if you need help

    Ken
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    I would suggest getting the Intel networking driver from the Intel Download Center.
    Here's a link to the page for the 32 bit Win7 driver: Network Adapter Driver for Windows 7*
      My Computer


  9. Posts : 9
    Windows 7 Ultimate
    Thread Starter
       #9

    zigzag3143 said:
    You can use the vista drivers IF you install them in compatibility mode. to do that right click the installer>properties>compatibility>vista

    Let us know if you need help

    Ken
    Okay - will give it a try.
    Thanks Ken

    usasma said:
    I would suggest getting the Intel networking driver from the Intel Download Center.
    Here's a link to the page for the 32 bit Win7 driver: Network Adapter Driver for Windows 7*
    I actually bought Driver Genius and scanned for driver updates... Found 14 driver updates and was able to update 12 of them - The network adapter driver you listed was included in the update actually - but when I try installing it - I get a mid-install "Intel(R) Network Connections Installer Information" message popup which states:

    Code:
    Cannot install drivers. No Intel(R) Adapters are present on this computer.
    I'm so lost with this stuff - I don't know what to do - and just tried another reboot - got another BSOD.

    HELP! ((sigh...))

    Jacquii.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    MsJacquiiC said:
    zigzag3143 said:
    You can use the vista drivers IF you install them in compatibility mode. to do that right click the installer>properties>compatibility>vista

    Let us know if you need help

    Ken
    Okay - will give it a try.
    Thanks Ken

    usasma said:
    I would suggest getting the Intel networking driver from the Intel Download Center.
    Here's a link to the page for the 32 bit Win7 driver: Network Adapter Driver for Windows 7*
    I actually bought Driver Genius and scanned for driver updates... Found 14 driver updates and was able to update 12 of them - The network adapter driver you listed was included in the update actually - but when I try installing it - I get a message which states:

    Code:
    Cannot install drivers. No Intel(R) Adapters are present on this computer.
    I'm so lost with this stuff - I don't know what to do - and just tried another reboot - got another BSOD.

    HELP! ((sigh...))

    Jacquii.

    You are better off going to the MFR site itself rather than using any sort of driver updating program. the driver on the site is newer.

    Ken
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 17:51.
Find Us