| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 97501 | 2009-02-18 04:42:00 | PC Issues - blue screen | JMoore (9352) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 748931 | 2009-02-21 05:37:00 | Ok thanks for info. Looks like the freezing and W32Time errors only occur when I try and connect to this specific network. That is when I connect to a neighbours network it will allow me to enter a (incorrect) password and attempt to acquire network address, whereas when connecting to our home network it will freeze as soon as I click connect after entering password. Only device in device manager showing an X is an Intel(R) PRO/100 VE Network Connection under Network adapters. Hardware conflict? |
JMoore (9352) | ||
| 748932 | 2009-02-21 05:53:00 | To fix the time (hopefully) double click on the time on the taskbar. Go to internet time, change it to msltime1.irl.cri.nz then apply. You in NZ or somewhere else? times.windows.com I think doesnt exist Look in event viewer again, look for a save dump entry under system or application. Copy and paste it here Ah that X maybe because the onboard NIC is disabled? If it is thats normal Double click on it, does it say code 22? |
Speedy Gonzales (78) | ||
| 748933 | 2009-02-21 05:58:00 | Changed time settings, hopefully it will fix that problem. Can't seem to find any save dump entries in the event viewer should it say save dump under source? Or what do I need to look for? Yea you're right I realised shortly after I posted that the NIC was disabled (code 22). |
JMoore (9352) | ||
| 748934 | 2009-02-21 06:05:00 | It'll look similar to this (www.eventid.net) | Speedy Gonzales (78) | ||
| 748935 | 2009-02-21 06:15:00 | Like I mentioned before the system has just been freezing on connect recently rather than going to BSOD so that might have been the reason I wasn't getting a save dump. I just tried to connect now and got BSOD which I hadn't been getting before. Checked event viewer on reboot and found the following events: Source: Save Dump The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x86a75788, 0x86a75788, 0x0a000086). A dump was saved in: C:\WINDOWS\Minidump\Mini022109-01.dmp. Source: System Error Error code 00000019, parameter1 00000020, parameter2 86a75788, parameter3 86a75788, parameter4 0a000086. The system error contains basically all the information given in BSOD. |
JMoore (9352) | ||
| 748936 | 2009-02-21 06:27:00 | Is this a Netgear wireless network card, by any chance? By the looks of it (www.tweaksforgeeks.com) that BSOD (thats what 0x00000019 means), is common with Netgear wireless cards Did you get the drivers from the makers site, and NOT from windowsupdate? |
Speedy Gonzales (78) | ||
| 748937 | 2009-02-21 06:35:00 | No it's a D-Link DWL-520+ PCI card and got the drivers directly from D-Links NZ support site. Any ideas why the issue would occur only on this specific network? Could it be to do with the WEP or whatetever? | JMoore (9352) | ||
| 748938 | 2009-02-21 06:48:00 | I would update it, as it looks like its out of date / discontinued. And its only 11.b not g Or even better, if this computer has USB 2 ports get a USB 2 wireless adapter What is this trying to connect to at home? |
Speedy Gonzales (78) | ||
| 748939 | 2009-02-22 00:18:00 | Fair enough it probably wouldn't be too expensive although I was actually looking to buy a new PC and wanted to do some research on what to get before selling or whatever so having a net connection would be convenient. It still puzzles me that it only happens on this one network, which I set up last week - a wireless network with 64bit WEP on a Linksys VOIP router. | JMoore (9352) | ||
| 1 2 3 | |||||