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

MsJacquiiC · 17 May 2010

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 · 17 May 2010

MsJacquiiC said:

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

Code:

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 · 17 May 2010

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 :P

Jacquii.

zigzag3143 · 17 May 2010

MsJacquiiC said:

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 :P

Jacquii.

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

usasma · 18 May 2010

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 · 24 May 2010

usasma said:

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

usasma said:

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 o.O

Thanks

Jacquii.

usasma · 25 May 2010

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!

MsJacquiiC · 26 May 2010

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 · 26 May 2010

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.