Windows 10: BSOD every now and then, seems to happen only during games

Hey!

I've bought a new laptop a few weeks ago, and also use it for mild gaming. However, every now and the it reboots and I find a minidump using BlueScreenView. On average, there's one BSOD a week and it seems to happen during games. I didn't happen when I first started using this, the only updates I have done are regular Windows Updates and then BIOS (for the Windows Update) and GPU drivers both from HP's webpage. I dunno what else to do, so I am hoping someone else would help me with my problem, and hopefully get this fixed. Could the drivers be the problem?

:)

 

BSOD - Happens only during gaming

Driver verified and the crashes are caused by Xlguard.sys

*** ERROR: Module load completed but symbols could not be loaded for XLGuard.sys

Probably caused by : XLGuard.sys ( XLGuard+8d54 )

DRT has no reference of it, but a rough search on google relates this to ShenZhen Thunder Networking Technologies Ltd

Uninstalling the program should resolve your issue.

 

BSOD - Happens only during gaming

HI,

I used WhoCrashed software. nt_wrong_symbols.sys that is causing the problem. How do i rectify it?

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:

C:\WINDOWS

C:\WINDOWS\Minidump

On Fri 12/29/2017 9:18:21 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\122917-4015-01.dmp

This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)

Bugcheck code: 0xA (0xFFFFDC055F8C2F90, 0x2, 0x1, 0xFFFFF8010FC2BECD)

Error: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .

Google query: nt_wrong_symbols.sys IRQL_NOT_LESS_OR_EQUAL

On Fri 12/29/2017 9:18:21 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP

This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)

Bugcheck code: 0xA (0xFFFFDC055F8C2F90, 0x2, 0x1, 0xFFFFF8010FC2BECD)

Error: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.

This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .

Google query: nt_wrong_symbols.sys IRQL_NOT_LESS_OR_EQUAL

On Fri 12/29/2017 9:08:09 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\122917-4140-01.dmp

This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)

Bugcheck code: 0x19 (0xE, 0xFFFFCB886C52C570, 0xC05E03CD1EE8ED94, 0xC05E03CD1EE8ED96)

Error: BAD_POOL_HEADER

Bug check description: This indicates that a pool header is corrupt.

This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .

Google query: nt_wrong_symbols.sys BAD_POOL_HEADER

On Fri 12/29/2017 8:48:54 AM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\122917-3250-01.dmp

This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)

Bugcheck code: 0xC4 (0x2000, 0xFFFFF80CDE378D54, 0x0, 0x62527050)

Error: DRIVER_VERIFIER_DETECTED_VIOLATION

Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .

Google query: nt_wrong_symbols.sys DRIVER_VERIFIER_DETECTED_VIOLATION

 

Hello Derpping,

As this is a new laptop I would return it and ask for a replacement. The one BSOD report indicates that there is a hardware error. Without further testing it is not easy to determine what component might be failing but for a new laptop you should return it and show the following analysis. I would suspect motherboard or CPU at this stage.

The error record is attached and pinpoints AMD Northbridge
Code: Event[3113]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-01-24T01:30:03.975 Event ID: 20 Task: N/A Level: Virhe Opcode: Tietoja Keyword: N/A User: S-1-5-19 User Name: NT-hallinta\Paikallinen palvelu Computer: LAPTOP-PJTT046L Description: On ilmennyt vakava laitteistovirhe. Osa: AMD Northbridge Virheen lähde: Tietokoneen tarkistuksen poikkeus Virhetyyppi: 11 Suorittimen APIC-tunnus: 0[/quote]
Code: 1: kd> !errrec ffff9c875870b818 =============================================================================== Common Platform Error Record @ ffff9c875870b818 ------------------------------------------------------------------------------- Record Id : 01d394a2011b16d7 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 1/23/2018 23:29:30 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffff9c875870b898 Section @ ffff9c875870b970 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000660f01 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffff9c875870b8e0 Section @ ffff9c875870ba30 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 01 0f 66 00 00 08 04 00 - 0b 32 d8 3e ff fb 8b 17 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffff9c875870ba30 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffff9c875870b928 Section @ ffff9c875870bab0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) Status : 0xf2000010000b0c0f[/quote]

 

Thank you, I contacted the seller via email and showed the analysis. I forgot to mention, that I've heard a loud beep all of sudden from the motherboard, so could it also be related to this issue I'm facing now?

 

It could be, do you have any manual (could be online) for the motherboard which explains the cause of the beep? If it happens during the BIOS loading at startup it will usually help to pinpoint the hardware problem.

 

It has happened on a regular use, never on start-up. The last time I remember it happening when I was playing, it was one or two loud beeps and that's it. The laptop is HP Pavilion 15-ab171no, but I didn't find the manufacturer's guide for beeps or anything.

 

See this HP link for their beep codes:
HP and Compaq Desktop PCs - BIOS Beep Codes | HP® Customer Support

Download and install the HP UEFI diagnostics version 6.5: HP PC Hardware Diagnostics | HP® Official Site

Power on the computer and repetitively click the F2 key > run the loop until failure test overnight and report the results into the thread
If the test aborts it will display an error code and only HP can interpret the code.
If the test is still running and as made 2 passes > press the keyboard escape key to abort the test > view the UEFI diagnostic log > post the results into the thread.

 

Thank you! I'll run the test later as I was away from home. How long does the test take, so is it necessary to run it overnight? I also checked the beep codes - it's one long beep, but the American Megatrends BIOS section claims the beep codes are on startup.