I have 2 Windows 7 betas running on 2 pcs. When PC "A" is running and I start PC "B", PC A crashes. The crash occurs when the 2nd PC is loading the desktop. My assumption is that it has something to do with the network/network drivers??I really want to be able to use the homegroup feature to watch recordings on A, located on B.Has anyone else experienced this?Does anyone have any solutions/suggestions?Thanks

HiWhatyou callcrash?

Blue screen. The computer flashes a blue screen with some info (but only lasts about 1 second), and then reboots.

see error in event viewer or disable auto restart on boot by pressing F8 to open advanced boot menu

Basically there were 3 events around the time of the blue screen. The first 2 were at the time, and the last one was just prior - I think. Also note that the last one also occurred several other times - without causing shutdowns.Here are the events....Critical 8/02/2009 8:11:41 AM Kernel-Power 41 (63) - System - Provider [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4} EventID 41 Version 2 Level 1 Task 63 Opcode 0 Keywords 0x8000000000000002 - TimeCreated [ SystemTime] 2009-02-07T22:11:41.813216300Z EventRecordID 12187 Correlation - Execution [ ProcessID] 4 [ ThreadID] 8 Channel System Computer 7MC - Security [ UserID] S-1-5-18 - EventData BugcheckCode 209 BugcheckParameter 0x90223ddc BugcheckParameter 0x2 BugcheckParameter 0x8 BugcheckParameter 0x90223ddc SleepInProgress false PowerButtonTimestamp 128784263943942503The previous system shutdown at 8:10:10 AM on 8/02/2009 was unexpected. - System - Provider [ Name] EventLog - EventID 6008 [ Qualifiers] 32768 Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2009-02-07T22:12:05.000000000Z EventRecordID 12183 Channel System Computer 7MC Security - EventData 8:10:10 AM 8/02/2009 132264 D90702000000080008000A000A006201D90702000600070016000A000A006201600900003C000000010000006009000000000000B00400000100000000000000 Binary data: In Words 0000: 000207D9 00080000 000A0008 0162000A 0008: 000207D9 00070006 000A0016 0162000A 0010: 00000960 0000003C 00000001 00000960 0018: 00000000 000004B0 00000001 00000000 Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x001FD0D0B916. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. - System - Provider [ Name] Microsoft-Windows-DHCPv6-Client [ Guid] {6A1F2B00-6A90-4C38-95A5-5CAB3B056778} EventID 1001 Version 0 Level 2 Task 3 Opcode 74 Keywords 0x8000000000000000 - TimeCreated [ SystemTime] 2009-02-07T22:07:36.753155400Z EventRecordID 2716 Correlation - Execution [ ProcessID] 964 [ ThreadID] 6752 Channel Microsoft-Windows-Dhcpv6-Client/Admin Computer 7MC - Security [ UserID] S-1-5-19 - EventData HWLength 6 HWAddress 001FD0D0B916 StatusCode 121

I do not know, I would try to disable nic power management from nic proprties

I gave that a try but no luck. On the other PC the blue screen stayed around so I was able to see the error message.Driver IRQL not less or equalthen further down....Technical informationndiswan sys - address 8DFB2DDC, base at 8DF9D000, Date Stamp 4943237BIf anyone has any suggestions or knows what the problem could be I would love to hear it. In the mean time I am going to do fresh installs on both betas and not install a single thing other than the required drivers. i will then see if I have the problem still. At that point I will start slowly adding things to see what the problem could be???

Looks like hardware problemMaybe your computer is overclocked, so if this is the case revert all timings and clocks to defaults, then check RAM for errorsDo you use NIC driver for w7 or you have installed some old driver for xp or vista?

No, no overclocking at all. I am not sure if the driver is vista or w7. Windows update suggests a new driver with the new build, but I thought I would try the origianl one out first and see if I have the problem - if I do, I will update both drivers and see how I go.

The info there isn't giving me any clues. Can you check the reliability monitor:Control Panel\System and Security\Action Center\Reliability MonitorAnd see if you can locate some of the crashes, then double-click and paste the details. I am mainly interested in the BucketID but would love to see everything.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Hi Ned,I ended up doing fresh installs on both pc's. So far so good - they are not experiencing the problem. Having said that, they don't have much on them yet at all. Over the next couple of days I plan to start adding more, so if it happens again, I will report back here with the info you suggested.Thanks anyway.

No worries, we'll be here. :)Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Ned Pyle [MSFT] said: The info there isn't giving me any clues. Can you check the reliability monitor:Control Panel\System and Security\Action Center\Reliability MonitorAnd see if you can locate some of the crashes, then double-click and paste the details. I am mainly interested in the BucketID but would love to see everything. Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team There is no reliability monitor in w7, just in vista, why?Is this some bug i need to include in my bugs list?Even i click view system reliability nothing happen, so I though it is removed

You don't see it? It's right here:Control Panel\All Control Panel Items\Action Center\Reliability MonitorNed Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

NoI use w7 x64 and as I said there is not reliability monitor. When I paste this path in windows explorer and press enter address achanges to C:\Windows\System32\control.exe but nothing happen.Obviously this is bug

No, that was a path for you for you to follow manually in Control Panel. When you get to the Action Center, select Maintenance and 'Problem History'; this starts the Reliability Monitor. I'm not here to lie to you, it exists...Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

The error on the other PC is a relatively common error (STOP 0xD1) and is caused by a driver.The other error (BugCheck Code 209) is rare. It would help if you still had the memory dump for this error.- John

Sorry, I don't have it as I reinstalled the beta and haven't had the problem since. Having said that, I keep switching back and forth between the beta and vista as I keep running into other problems. As of this morning am on the beta again. :)

Ned Pyle [MSFT] said: No, that was a path for you for you to follow manually in Control Panel. When you get to the Action Center, select Maintenance and 'Problem History'; this starts the Reliability Monitor. I'm not here to lie to you, it exists... Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team OK but how to know that this ia reliability monitor?In vista it was under minitoring tools in computer managementIn W7 when I right click Monitoring tool category in computer management there is optin called View system reliability that do nothing if it is clickedThere definitely have buh because all other paths that I paste in windows explorer oppen tarfet, but only reliability monitor cannot be opened in this wayNed Pyle [MSFT]if you are from W7 developers team then you must know that there a lot od bygs in this betaCheck my bug list to see some of them to knw what must be fixedMy W7 system usese only drivers that comes with W7 so this are pure W7 bugs :)My W7 bugs list- updater frequently :)

Ah I see what you mean about that - I'll see if there's a bug filed on this already and will file one if not.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

The Win7x64 path to the reliability monitor is: Control Panel>All control Panel Items>Action Center(sic)>drop-down arrow on "Maintenance" then look at "Check for solution to problem reports" and make sure it is "on", then click on the "view system history" hyperlink which then opens as "Reliability Monitor"! This needs to be renamed so as not to be so arcane!

I draw the line at "center[sic]" majmac. Just because you want to misspell everything in the UK, Australia, and NZ doesn't mean the EN-US localized version of Windows has to. :-)So file bugs all day for centre, colour, theatre, and all the other nonsense. And while you're at it, file bugs for the awful habit you folks have for mispronouncing aluminum and advertisement. ;-)Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Right on, Ned.