[hmp3]

Fixed the fart noise. It was Distill Monitor that was making the 'buzzer' sound alert even though I didn't add the sound notification.

Back to the Device Manager entries.

[Advertisements]

I would check all drivers to see if they have a Power Management tab but on mine those three definitely have the tab so start with them.

[RKinner]

I would check all drivers to see if they have a Power Management tab but on mine those three definitely have the tab so start with them.

[hmp3]

I went through every entry in Device Manager and had only 2 entries whose 'allow the computer to turn off this device to save power' boxes were ticked.

It was Realtek family network adaptor and Bluetooth USB dongle (used to operate my bluetooth keyboard).

I've now unticked those boxes.

Edited by hmp3, 06 March 2022 - 11:32 AM.

[RKinner]

OK.  Now we just wait and see if the blue screen comes back.

[hmp3]

Okay, thanks!

[hmp3]

Update: No BSOD.

But I've noticed that sometimes, even having no firefoxes running, having two mp3 players (XMPlay and Foobar) open simultaneously, can cause audio to freeze.

[hmp3]

HI again RKinner. How can I test if my onboard LAN card is failing?

I've had some yellow symbols on my LAN connection system tray icon, noticing that all the lights on my router are green and Wi-Fi working fine, where restarting the router doesn't restore a working LAN connection, but restarting the computer does. Toggling to re-enable the adaptor doesn't solve it either.

Right-clicking the tray icon for LAN connection to 'Diagnose Connection/troubleshoot' causes my mouse to freeze, forcing me to restart using my keyboard.

 

I didn't find anything in Event Viewer the 3 times this has recently happened.

But during my diagnosis, the event viewer showed this information;

 

Details about network adapter diagnosis:

Network adapter Local Area Connection driver information:

   Description . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Manufacturer  . . . . . . . . . : Realtek
   Provider  . . . . . . . . . . . : Microsoft
   Version   . . . . . . . . . . . : 7.2.1127.2008
   Inf File Name . . . . . . . . . : C:\Windows\INF\netrtx64.inf
   Inf File Date . . . . . . . . . : 13 July 2009  20:37:30
   Section Name  . . . . . . . . . : RTL8168C.ndi
   Hardware ID . . . . . . . . . . : pci\ven_10ec&dev_8168&rev_02
   Instance Status Flags . . . . . : 0x180200a
   Device Manager Status Code  . . : 0
   IfType  . . . . . . . . . . . . : 6
   Physical Media Type . . . . . . : 14
 

And somehow the diagnosis process succeeded and logged this:

 

Root Cause: The default gateway is not available
The default gateway is a device that connects a local network or computer to the Internet. A broadband modem or router is usually the default gateway.

[RKinner]

Search for 

cmd

right click on Command Prompt and then Run as Admin.

 

Type:

 

ipconfig

hit Enter

 

You should see:

 

Ethernet adapter Local Area Connection:

 

   Connection-specific DNS Suffix  . :

   Link-local IPv6 Address . . . . . : fe80::7c60:19f5:99df:d89c%10

   IPv4 Address. . . . . . . . . . . : 192.168.68.128 <=If this address starts with 169. then DHCP has failed and you won't have a Default Gateway

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : fe80::3e84:6aff:fe8b:f7b3%10

                                       192.168.68.1  <=This is the IPv4 gateway.  It's just the IPv4 address of your router.  Note if you have no default gateway then it's not going to work a

 

 

 

To test your connectivity type (Use your Default Gateway and not mine):

ping 192.168.68.1

hit Enter

Should look like this:

 

C:\WINDOWS\system32>ping 192.168.68.1

 

Pinging 192.168.68.1 with 32 bytes of data:

Reply from 192.168.68.1: bytes=32 time=2ms TTL=64

Reply from 192.168.68.1: bytes=32 time=5ms TTL=64

Reply from 192.168.68.1: bytes=32 time=3ms TTL=64

Reply from 192.168.68.1: bytes=32 time=2ms TTL=64

 

Ping statistics for 192.168.68.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 2ms, Maximum = 5ms, Average = 3ms

 

 

 

If you don't get 4 replies then you have a problem.

 

If you want you can make the ping go on forever:

 

ping -t 192.168.68.1

 

Sometimes this is useful to minimize and leave running.  That way you can see if you have intermittent problems.  Will also keep Windows from putting the network card to sleep in order to save power.

(Stop it with Ctrl + c)

 

To test DHCP type:

 

sc query dhcp

 

should look like this:

>sc query dhcp

SERVICE_NAME: dhcp

        TYPE               : 30  WIN32

        STATE              : 4  RUNNING

                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)

        WIN32_EXIT_CODE    : 0  (0x0)

        SERVICE_EXIT_CODE  : 0  (0x0)

        CHECKPOINT         : 0x0

        WAIT_HINT          : 0x0

 

 

 

 

 

 

C:\WINDOWS\system32>ping 192.168.68.1

 

[hmp3]

Thank you RKinner and I hope you're doing well!!!

ipconfig yields the same as yours (ipv6 and default gateway start with fe80 like yours, but end differently), and ipv4 starts with 192 (not 169).

 

But I see 2 additional paragraphs;

"

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Unknown adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

".

 

Ping Test failed. I disabled MBAM and Comodo Firewall, but no avail;

"ping 192.168.68.1

Pinging 192.168.68.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.68.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
".

 

I didn't run the constant ping test because of the failure, but checked in device manager and can confirm that my computer is not allowed to shutdown network adapter in power management tab.

 

DHCP Query test shows same results as yours, but with a different top line:

"TYPE               : 20  WIN32_SHARE_PROCESS".

 

You ended your post with:

"C:\WINDOWS\system32>ping 192.168.68.1".

I'm not sure what to do with that.

Edited by hmp3, 20 April 2022 - 09:36 AM.

[RKinner]

I'm pretty sure your gateway is not the same as mine so it's no wonder the ping failed.  Remember to use your own gateway address in the ping command.

 

Not sure what the unknown Local Are Network is.  Do you see it in Device Manager, Network Adapters?

[hmp3]

Apologies. I pinged my Default Gateway and the 4 responses were 1ms, but No "ttl" at the end.

Packets: 0% loss.

"Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms"

 

I don't see Local Area Network in Device Manager, but it is the name of my Ethernet Internet Adapter in "All Control Panel Items\Network Connections".

Edited by hmp3, 20 April 2022 - 03:54 PM.

[RKinner]

I would try the ping -T option and let it run for 10 minutes or so then do Ctrl + c and it should tell you if it dropped any pings.  If not then the Network Adapter is probably OK.

[hmp3]

Ran Ping-T for 40mins. All results were either <1ms or =1ms.

 "

  Packets: Sent = 6427, Received = 6427, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 31ms, Average = 0ms

"

[hmp3]

The connection dropped again just now. Router showed no issues.

Just before restarting to fix the connection, I ran the ping test:

 

 

Request timed out.

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for fe80…:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[RKinner]

Try running ipconfig next time it fails.  See if anything has changed.