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

[MsJacquiiC]

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.

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:

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.

 

[usasma]

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:

e100b325.sys Fri Nov 16 13:53:32 [COLOR=Red][U][B]2007[/B][/U][/COLOR] - 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:

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

 

[MsJacquiiC]

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.

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.

 

[usasma]

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:

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

 

[MsJacquiiC]

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

Jacquii.

 

[MsJacquiiC]

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.

 

[zigzag3143]

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

 

[usasma]

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*

 

[MsJacquiiC]

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

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:

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.

 

[zigzag3143]

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

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:

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

 

[MsJacquiiC]

When I try installing chipset or various other drivers - I either get a mid-install message "Your system does not meet the minimum requirements for this update. Update has been cancelled (9998)" OR the "Intel(R) Network Connections Installer Information" message popup I posted earlier which states:

Cannot install drivers. No Intel(R) Adapters are present on this computer.

It's crazy because looking in devices shows several intel drivers and the adapter. This is so frustrating! I would not have thought installing a brandnew windows 7 would result in these types of errors ARG. I've uploaded most recent minidump files at http://jacquiicooke.com/Minidump.rar

Any further assistance will be appreciated - especially if you can give detailed info (including hp.com urls perhaps) to which exact drivers I should update for my pc to work correctly with windows 7?

Maybe this pc is just not meant to work correctly with windows 7??? It's only a year and a half old! I would think compaq/hp would provide detailed support info for the upgrade - but they are giving me nothing - I've spent some 6+ hours googling various things, mostly of which has turned up nothing but BS and customer complaints. Should I consider forgetting the entire thing and reinstall vista? That would totally suck because I love the windows 7 so much better than vista ((sigh))

Jacquii.

 

[zigzag3143]

When I try installing chipset or various other drivers - I either get a mid-install message "Your system does not meet the minimum requirements for this update. Update has been cancelled (9998)" OR the "Intel(R) Network Connections Installer Information" message popup I posted earlier which states:

Cannot install drivers. No Intel(R) Adapters are present on this computer.

It's crazy because looking in devices shows several intel drivers and the adapter. This is so frustrating! I would not have thought installing a brandnew windows 7 would result in these types of errors ARG. I've uploaded most recent minidump files at http://jacquiicooke.com/Minidump.rar

Any further assistance will be appreciated - especially if you can give detailed info (including hp.com urls perhaps) to which exact drivers I should update for my pc to work correctly with windows 7?

Maybe this pc is just not meant to work correctly with windows 7??? It's only a year and a half old! I would think compaq/hp would provide detailed support info for the upgrade - but they are giving me nothing - I've spent some 6+ hours googling various things, mostly of which has turned up nothing but BS and customer complaints. Should I consider forgetting the entire thing and reinstall vista? That would totally suck because I love the windows 7 so much better than vista ((sigh))

Jacquii.

Most of these seem to be caused by smss.exe which is the user subsystem of win 7. SInce a win 7 file is suspected I would run a system file check
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know if you need help

Ken

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sun May 16 18:09:54.009 2010 (GMT-4)
System Uptime: 0 days 0:00:15.038
BUGCHECK_STR:  0xc000021a_0
PROCESS_NAME:  smss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
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

 

[MsJacquiiC]

I ran the scan:

Check out the CBS.log file if you like - I'm not exactly sure what all that means -- I've yet to reboot though - but will do so shortly. Perhaps that will have helped...? Hopefully. But the smss.exe file was not even mentioned in that .log file.

Anyway - I appreciate the assistance - would be nice to have my pc back and functioning like the good ol' days LOL - I miss him terribly

Jacquii.

 

[zigzag3143]

I ran the scan:

Check out the CBS.log file if you like - I'm not exactly sure what all that means -- I've yet to reboot though - but will do so shortly. Perhaps that will have helped...? Hopefully. But the smss.exe file was not even mentioned in that .log file.

Anyway - I appreciate the assistance - would be nice to have my pc back and functioning like the good ol' days LOL - I miss him terribly

Jacquii.

That is a good sign. It found corrupt files and repaired them. Lets seee if he is cured. <g>

 

[usasma]

There's a lot of generalizations when speaking about PC's.
In this case, it appears that that the Compaq Presario sr5050nx was originally designed when Windows XP was out - and then was continued after Windows Vista was released. As such, that makes the design somewhat outdated.

That being said, the people at Compaq have to decide what systems to support and what systems not to support as each release of Windows comes out. They just can't afford to support everything for every OS - for several reasons.

For example, there may be hardware limitations that doesn't support the new Operating System - so the system can't be upgraded. When they sold the system with Vista on it they had no idea about Windows 7.
Also, it'll depend on how many people need the drivers. It costs a lot of money for them to have someone write a driver for Windows 7 if one doesn't exist - then they've gotta test it and make sure it works with all possible scenarios and programs. The development costs are enormous!.

But, there's enough of these devices out in the world that it's usually possible to find Windows 7 drivers. And, in many cases, it's possible to use Vista drivers in compatibility mode (usually with good success). But as I said previously, these are generalizations - so we've gotta work things out for your particular system.

Finally, sometimes the manufacturer will change parts during the manufacturing run - either due to cost, or due to issues with parts. As such we try the specified drivers first. Then, if they don't work, we try other things.

So, please open Device Manager and expand the Network Adapters category.
Right click on your network device there (if there's more than one there - do it for each one)
Select Properties
Select the Details tab
Select Hardware ID in the dropdown box.
Please write down the 4 characters immediately following the VEN_ and the 4 characters immediately following the DEV_
We'll use those characters at the PCI Vendor and Device Lists website to determine the make and model of your networking device(s) that are actually installed.

 

[MsJacquiiC]

That being said, the people at Compaq have to decide what systems to support and what systems not to support as each release of Windows comes out. They just can't afford to support everything for every OS - for several reasons.

Could have been nice to place a big yellow or green sticker on the product I paid $600+ for so that I (and other "want to upgrade to the best possible os available" type customers...) would know that we could possibly be shyt out of luck when something better comes along...? IDK - but when you have thousands and millions of dollars coming in to your business via said customers - it would make sense that we should have a better support system than, "Sorry - you're shyt out of luck. We're not gonna allow you to upgrade. Feel free to purchase another hefty-dollar HP/Compaq product if you like..."

Meh. I digress...

So, please open Device Manager and expand the Network Adapters category.
Right click on your network device there (if there's more than one there - do it for each one)
Select Properties
Select the Details tab
Select Hardware ID in the dropdown box.
Please write down the 4 characters immediately following the VEN_ and the 4 characters immediately following the DEV_
We'll use those characters at the PCI Vendor and Device Lists website to determine the make and model of your networking device(s) that are actually installed.

I very much appreciate your assistance at anyrate usasma. Would that I could chuck this pc out the damn window and purchase a quad-core blablabla... Unfortunately - I have no money tree in which to pick off fabulous money leaves..

I suppose we can all dream...

Anyway - I've done as you've recommended:

• The 4 characters immediately following the VEN_ are 8086
• The 4 characters immediately following the DEV_ are 27DC

All I know of those digits is that they are in no particular combination that I'd have personally chosen. They are the digits as requested though... The question is - can you help me figure out exactly what to do with them? Ideally - I'd like to download/install drivers that will make my computer operable. As it is - I'm being told that "Your system does not meet the minimum requirements for this update. Update has been cancelled (9998)" OR the "Cannot install drivers. No Intel(R) Adapters are present on this computer."

Frustrating it is... Frustrating I would like it not to be.

Um... again - I say much appreciation for both of you guys' assistance. Let's get on the same page so we can fix this crummy pc ARG

Thanks

Jacquii.

 

[usasma]

FWIW - there's not much money made on selling computers. They actually make their money on selling accessories.

The VEN_ code of 8086 is the code for Intel
The DEV_ code of 27DC is the code for Intel® PRO/100 VE Desktop Adapter

I find this information at PCI Vendor and Device Lists
Then, I go to the Intel Download Center at http://downloadcenter.intel.com

The next part is a bit fuzzy:
- I find the appropriate Product Family (I chose anything related to networking)
- Then I find the Product Line (I guessed that this was a Desktop network adapter)
- Then I find the Product Name (Pro 100 VE)

Interestingly, Intel doesn't even offer Vista drivers - so I suspect that HP/Compaq is using a modified XP driver so that it'll function under Vista. So, we've gotta look elsewhere for Win7 drivers.

So I did this Google search: Intel PRO/100 VE Desktop Adapter driver windows 7 - Google Search
And I clicked on the first link ( Support for the Intel® PRO/100 VE Desktop Adapter ).
Then clicked on the Is my Intel® Ethernet Adapter supported in Microsoft Windows 7*? link
And it says I can

Manually download the latest Intel® Ethernet Software & Driver files
Wired Ethernet Adapter Drivers for Windows 7*

And the latest version there is at this link: Â Network Adapter Driver for Windows 7*

Give that a try and we'll see where we can go from there.

Good luck!
http://downloadcenter.intel.com/SearchResult.aspx?keyword=PROWin32.exe&OSVersion=Windows+7*

 

[MsJacquiiC]

I've tried installing that driver before, only to get the following error message:

Interestingly enough - I've been googling all night and a couple pages on the Intel site caught my attention: A guide to Intel® PRO/100 Network Adapter drivers and Is my Intel® Ethernet Adapter supported in Microsoft Windows 7*? -- both of which allude to no adapter available for windows 7

I'm seriously considering reverting back to Vista - I don't want to - but this is just ridiculous.

Any further suggestions/recommendations?

Thanks again ((sigh...))

Jacquii.

 

[usasma]

If those drivers don't work, then it's likely that there's a problem with the Intel network card.

I'd suggest a new ethernet card (a card for a PCI slot - not a PCIe slot). They're fairly cheap (about $15 at most retailers, less online) and easy to install. According to the specs of your system on the HP/Compaq site, you've got 3 PCI slots available on the system.

Once it's installed, be sure to disable the other one in Device Manager. If you need assistance with any of this, just post back here.