windows 7 crashes whenever connected to network
i have home network with 1 PC, 1 netbook, 1 laptop and a network printer all connected together via a 2wire router cum ADSL modem. The PC which is running windows 7 professional 64bit, crashes with a BSOD randomly whenever my laptop is switched on and connected to the network. By randomly i mean sometimes it can run an online game for a couple of hours before it crashes, but sometimes it will just crash even when idle. All the crashing will only occur if my laptop (which is a 4 yr old fujitsu lifebook running win xp pro) is switched on. If my laptop is not on, the PC can run for as long as it like without crashing. Another thing to take note is that the crashes happen even after i just format and reinstall Windows 7. I updated all my device drivers to the latest versions already, and it still happens. However, i tried installing win xp home 32bit on the PC instead of the win 7 pro 64 bit, the problem is gone, the PC never crash. But win xp home 32 bit runs very slow on my PC, so i still want to try using win7 pro 64, but i got to fix the BSOD crashing problem. Ok, i was looking at other similar thread, so i disabled automatic restart after the BSOD, and this is the error msg i get in the BSOD: Tech information *** STOP: 0x0000007F (0x0000000000000008, 0x0000000080050031, 0x00000000000006F8, 0xFFFFF80002A94C91) Hope i can get some help on this! Thank you very much! info of the Systems in my home network: PC: Intel Core i5 on Asus P7H55-M, ATI Radeon HD4670, Windows 7 Professional 64bit. Laptop: Fujitsu Lifebook S7110, Intel Centrino Duo, Windows XP Professional 32bit Netbook: Asus EeePC Printer: Fuji Xerox C1110 Router/ADSL Modem: 2Wire 2701HGV-E
August 12th, 2010 6:28am

Hi, This issue can be caused by the driver issue. I suggest we go to check the latest network card driver, update the NIC and the router. Please go to test this issue in Clean Boot and Safe Mode with Networking to determine the possible cause. If it works fine in Clean Boot, the root cause can be the third party software. If the issue reoccurs in Clean Boot, but works fine in Safe Mode, the cause can be the incompatible hardware drivers. You may narrow down the causes in Device Clean Boot. Device Clean Boot ================= 1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter. 2. Expand "Sound, video and game controllers". 3. Right click on your sound card and then click "Properties. 4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK. 5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled. Also, you can refer to the following KB article to test this issue: General causes of "STOP 0x0000007F" errors http://support.microsoft.com/kb/137539/en-us · If the issue persists, would you please upload more minidump files for further research? Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. 4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder". 5. Please send the ZIP file to us. You can refer to the following link to upload the information: http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65 You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Sabrina Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2010 12:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics