Forum Home
Press F1
 
Thread ID: 141602 2016-01-19 06:42:00 Wifi Issues Driftwood (5551) Press F1
Post ID Timestamp Content User
1414698 2016-01-20 05:07:00 WHEA uncorrectable error can be cpu related. It can mean update the BIOS. If you use ASUS AI suite, this may also cause it.

Overclocking can also cause that stop error
Speedy Gonzales (78)
1414699 2016-01-20 05:29:00 Its a fairly old system.
I think its got the latest bios available.
Definitely not overclocked.

Just ran the hardware & devices troubleshooter.
Nothing showed up for networking.
Found & fixed something under devices.
Asked for a restart.
Still the same.

Just tried something.
While it's running happily, if I disconnect the network cable, the network icon changes to wifi & it will run for almost 2 minutes before the blue screen appears.
Driftwood (5551)
1414700 2016-01-20 05:35:00 Is it 32 orf 64 bit windows 10?? So youre getting that whea uncorrectable stop error with thst wireless card as well?

Can you upload the smaller dmp files somewhere. So I can download them. I'll see what else is installed on this system

That stop error can also mean something is overheating. Does it feel hot around the CPU?

If the case is full of dust, give it a clean

What's the specs of this thing?? Whats the mobo?

It's not a gigabyte mobo is it?? Programs like Easytune and Easysaver will cause this crash too. And if it's using an AMD card AMD Overdrive will also cause it
Speedy Gonzales (78)
1414701 2016-01-20 06:38:00 It's x32.
The error shows regardless of weather there is a wifi card or not.
There is nothing installed other than Classic Shell & CCleaner.
No overheating, case is open atm & clean as.
Specs, well it's an oldy.
Winfast Foxconn NF4K8AC-8EKRS with Athlon64 3200 @ 2 GHz
2GB memory

I'm thinking it's just too old to handle it.
Bit like me really.
Driftwood (5551)
1414702 2016-01-20 07:01:00 It finished ok but didn't cure the problem.

I've got the update issue sorted.

Actually read the full message on the blue stop screen.
WHEA uncorrectable error.

Points to hardware.

Found something else too.
Regardless of weather the wifi card is installed or not, the system wont run or boot without the network cable connected.

Check in the BIOS, look for PXE Boot, make sure its disabled, sounds a little like its trying to boot from a LAN connection first.
wainuitech (129)
1414703 2016-01-20 07:05:00 I see this mobo had a firewire header on it.

Whoever didnt plug a USB 2 cable into it, from the front did they? It looks like some people have done this, and they've received this 0x124 stop error.

And it'll also fry that header.
Speedy Gonzales (78)
1414704 2016-01-20 07:30:00 Disable the onboard LAN in the BIOS

Other people who have Nforce 4 mobos, have had the same stop error. (answers.microsoft.com)

That mobo uses an Nforce 4 chipset
Speedy Gonzales (78)
1414705 2016-01-20 08:04:00 Couldn't see anything in BIOS looking like PXE or LAN
BIOS settings are default, except for boot order & smart fan.
1st boot is DVD then HD.
Theres only 1 sata HD
Always been running this way.

Don't see a firewire header, but no connections have been changed recently.
Just swapping the wifi & trying different slots.
Driftwood (5551)
1414706 2016-01-20 08:14:00 I think you've nailed Speedy, I disabled MAC Lan now it runs only on wifi.
Boots up on it too.
Driftwood (5551)
1414707 2016-01-20 08:15:00 I would change the bootdisk to hdd. It may lessen the time to boot into windows

Sweet. There must a conflict or something when LAN is enabled. Or it may not be compatible with Win 10 somehow? Oh well at least it works now !
Speedy Gonzales (78)
1 2 3