My Helios 300 restarting itself

JackE · June 2019

Looks like it was released last week. Supposed to fix World of Warships error, Win10 GPU timeout resets, and performance issues with dual displays. Probably the reset thing. Good luck with it. Jack E/NJ

OGMike · June 2019

@JackE havent tested with gaming but so far so good, *knock on wood*

OGMike · June 2019

I'm also noticing my laptop is using less power, it usually stayed around like 15w even while idling now its around 5-10w.

JackE · June 2019

So game on! Jack E/NJ

OGMike · June 2019

So far so good, i will continue updating.

OGMike · June 2019

Update, it froze again.
Min not seeing anything that would have caused it though??
May have just been a random thing or overheating, it’s been getting pretty hot.

OGMike · June 2019

I wanting to say it’s more corrupt drivers, such as Realtek HD Audio background source, I have an error every time I start it up in my event log saying it has stopped working, I know it’s not a display error this time cause I’m no longer get the error with Nvidia display, nor am I getting black screens, the system will just freeze up, audio stops completely, keyboard lights up, and everything becomes unresponsive.

JackE · June 2019

So disable it in Device Manager. Do your thing without sound to see what happens. Jack E/NJ

OGMike · June 2019

@JackE i will try that, if anything do you know of any apps that can fix corrupted files or drivers?

OGMike · June 2019

Here is my suspect.

Log Name:      Application
Source:        Application Error
Date:          6/10/2019 3:55:29 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-VFCCEAC
Description:
Faulting application name: RAVBg64.exe, version: 1.0.0.295, time stamp: 0x5bc04e16
Faulting module name: RAVBg64.exe, version: 1.0.0.295, time stamp: 0x5bc04e16
Exception code: 0xc0000005
Fault offset: 0x0000000000042dff
Faulting process id: 0x2c40
Faulting application start time: 0x01d51fdf99a3e33a
Faulting application path: C:\Program Files\Realtek\Audio\HDA\RAVBg64.exe
Faulting module path: C:\Program Files\Realtek\Audio\HDA\RAVBg64.exe
Report Id: 1b411a94-6bae-4718-842e-587fad999118
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-06-10T22:55:29.446022000Z" />
    <EventRecordID>1099</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-VFCCEAC</Computer>
    <Security />
</System>
<EventData>
    <Data>RAVBg64.exe</Data>
    <Data>1.0.0.295</Data>
    <Data>5bc04e16</Data>
    <Data>RAVBg64.exe</Data>
    <Data>1.0.0.295</Data>
    <Data>5bc04e16</Data>
    <Data>c0000005</Data>
    <Data>0000000000042dff</Data>
    <Data>2c40</Data>
    <Data>01d51fdf99a3e33a</Data>
    <Data>C:\Program Files\Realtek\Audio\HDA\RAVBg64.exe</Data>
    <Data>C:\Program Files\Realtek\Audio\HDA\RAVBg64.exe</Data>
    <Data>1b411a94-6bae-4718-842e-587fad999118</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>

JackE · June 2019

>>> do you know of any apps that can fix corrupted files or drivers?>>>

Yep. Uninstall the device drivers from Device Manager. Exit Device Manager without trying to manually re-install anything yourself. Shutdown. Turn the machine back on and let Windows automatically re-detect the hardware on startup and re-install fresh drivers. Jack E/NJ

OGMike · June 2019

@JackE okay, fixed that, now one more question...any clue on this?

v\Log Name:      Application
Source:        Application Error
Date:          6/10/2019 6:09:17 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-VFCCEAC
Description:
Faulting application name: mmc.exe, version: 10.0.18362.1, time stamp: 0x288c7033
Faulting module name: ntdll.dll, version: 10.0.18362.145, time stamp: 0xd3b10352
Exception code: 0xc0000409
Fault offset: 0x000000000008c47f
Faulting process id: 0x1f3c
Faulting application start time: 0x01d51ff21007ad96
Faulting application path: C:\WINDOWS\system32\mmc.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 345b8290-4131-495f-8da9-6752da1d430f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-06-11T01:09:17.908134500Z" />
    <EventRecordID>1416</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-VFCCEAC</Computer>
    <Security />
</System>
<EventData>
    <Data>mmc.exe</Data>
    <Data>10.0.18362.1</Data>
    <Data>288c7033</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.18362.145</Data>
    <Data>d3b10352</Data>
    <Data>c0000409</Data>
    <Data>000000000008c47f</Data>
    <Data>1f3c</Data>
    <Data>01d51ff21007ad96</Data>
    <Data>C:\WINDOWS\system32\mmc.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>345b8290-4131-495f-8da9-6752da1d430f</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>

OGMike · June 2019

fixed it actually

OGMike · June 2019

Still having system freezes though, still trying to figure out what may be casuing it.

OGMike · June 2019

I got a software that detects any kind of junk/viruses/instability issue etc. and i cleaned up a lot of stuff and also found out my laptop was on high performance mode, so i set it to balanced and turned all the sleep settings to never and any other related thing, so hopefully that helps.