Jump to content

Windows 10 BSOD

XandersWithS
By XandersWithS
in Windows
 Share
Go to solution Solved by LionSpeck,
3 minutes ago, XandersWithS said:

Hi, I just got a problem related with BSOD (CODE: SYSTEM_SERVICE_EXCEPTION)

 

I am clueless about this. All I remember is... I was downloading my NVIDIA driver to the latest version.

 

My spec:

Ryzen 5 2600 with GALAX RTX 2060

B350 Tomahawk

Corsair Vengeance LPX 2666Mhz 8x2

ADATA 512GB & SEAGATE BARRACUDA 2TB

Seasonic Focus Gold 550W

 

This BSOD always happened when i opened Apex, I haven't tried any games that I have. Anyone got solution?

 

I read all forums, they say about RAM, or update drivers/remove old drivers that make BSOD. Sorry for my english is not good.

One thing you could try is download Windbg from the Microsoft Store and use it to analyze the dump file created with the BSOD.

When Windows crashes, it usually creates a dump file with the contents of the running memory; Windbg allows you to debug that file and points out what the cause of the BSOD was, although in very technical language. You could post the results of the analysis here.

On how to use Windbg for this purpose: when you open it, it should recognize the recent crash automatically, and through either a notification, or in the home (I don't recall) show you the dump file. Once you open it up, you'll find yourself facing a console with a bunch of info regarding the file. Towards the bottom of it, there should be some underlined, blue text with a command (something like "!analyze -v") : click on that and let the software download the symbols translations from Microsoft (which are used to translate the bytecode of the crash into something more understandable) and log down in the console a whole bunch of info. All that is logged in the console is helpful information to find out what the cause of the crash is.

Posted

Hi, I just got a problem related with BSOD (CODE: SYSTEM_SERVICE_EXCEPTION)

 

I am clueless about this. All I remember is... I was downloading my NVIDIA driver to the latest version.

 

My spec:

Ryzen 5 2600 with GALAX RTX 2060

B350 Tomahawk

Corsair Vengeance LPX 2666Mhz 8x2

ADATA 512GB & SEAGATE BARRACUDA 2TB

Seasonic Focus Gold 550W

 

This BSOD always happened when i opened Apex, I haven't tried any games that I have. Anyone got solution?

 

I read all forums, they say about RAM, or update drivers/remove old drivers that make BSOD. Sorry for my english is not good.

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Solution
3 minutes ago, XandersWithS said:

Hi, I just got a problem related with BSOD (CODE: SYSTEM_SERVICE_EXCEPTION)

 

I am clueless about this. All I remember is... I was downloading my NVIDIA driver to the latest version.

 

My spec:

Ryzen 5 2600 with GALAX RTX 2060

B350 Tomahawk

Corsair Vengeance LPX 2666Mhz 8x2

ADATA 512GB & SEAGATE BARRACUDA 2TB

Seasonic Focus Gold 550W

 

This BSOD always happened when i opened Apex, I haven't tried any games that I have. Anyone got solution?

 

I read all forums, they say about RAM, or update drivers/remove old drivers that make BSOD. Sorry for my english is not good.

One thing you could try is download Windbg from the Microsoft Store and use it to analyze the dump file created with the BSOD.

When Windows crashes, it usually creates a dump file with the contents of the running memory; Windbg allows you to debug that file and points out what the cause of the BSOD was, although in very technical language. You could post the results of the analysis here.

On how to use Windbg for this purpose: when you open it, it should recognize the recent crash automatically, and through either a notification, or in the home (I don't recall) show you the dump file. Once you open it up, you'll find yourself facing a console with a bunch of info regarding the file. Towards the bottom of it, there should be some underlined, blue text with a command (something like "!analyze -v") : click on that and let the software download the symbols translations from Microsoft (which are used to translate the bytecode of the crash into something more understandable) and log down in the console a whole bunch of info. All that is logged in the console is helpful information to find out what the cause of the crash is.

DESKTOP PC - CPU-Z VALID | i5 4690K @ 4.70 GHz | 47 X 100.2 MHz | ASUS Z97 Pro Gamer | Enermax Liqmax II 240mm | EVGA GTX 1070Ti OC'd

HOME SERVER | HP ProLiant DL380 G7 | 2x Intel Xeon X5650 | 36GB DDR3 RDIMM | 5x 4TB LFF Seagate Constellation 7.2K | Curcial MX500 250GB | Ubuntu Server 20.04

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
1 minute ago, LionSpeck said:

One thing you could try is download Windbg from the Microsoft Store and use it to analyze the dump file created with the BSOD.

When Windows crashes, it usually creates a dump file with the contents of the running memory; Windbg allows you to debug that file and points out what the cause of the BSOD was, although in very technical language. You could post the results of the analysis here.

On how to use Windbg for this purpose: when you open it, it should recognize the recent crash automatically, and through either a notification, or in the home (I don't recall) show you the dump file. Once you open it up, you'll find yourself facing a console with a bunch of info regarding the file. Towards the bottom of it, there should be some underlined, blue text with a command (something like "!analyze -v") : click on that and let the software download the symbols translations from Microsoft (which are used to translate the bytecode of the crash into something more understandable) and log down in the console a whole bunch of info. All that is logged in the console is helpful information to find out what the cause of the crash is.

On my way to download it and i will send the results here

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
5 minutes ago, LionSpeck said:

One thing you could try is download Windbg from the Microsoft Store and use it to analyze the dump file created with the BSOD.

When Windows crashes, it usually creates a dump file with the contents of the running memory; Windbg allows you to debug that file and points out what the cause of the BSOD was, although in very technical language. You could post the results of the analysis here.

On how to use Windbg for this purpose: when you open it, it should recognize the recent crash automatically, and through either a notification, or in the home (I don't recall) show you the dump file. Once you open it up, you'll find yourself facing a console with a bunch of info regarding the file. Towards the bottom of it, there should be some underlined, blue text with a command (something like "!analyze -v") : click on that and let the software download the symbols translations from Microsoft (which are used to translate the bytecode of the crash into something more understandable) and log down in the console a whole bunch of info. All that is logged in the console is helpful information to find out what the cause of the crash is. 

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3281

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 13839

    Key  : Analysis.Init.CPU.mSec
    Value: 937

    Key  : Analysis.Init.Elapsed.mSec
    Value: 105299

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 96


FILE_IN_CAB:  021422-13750-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8057b68adc0

BUGCHECK_P3: fffff805800e9920

BUGCHECK_P4: 0

CONTEXT:  fffff805800e9920 -- (.cxr 0xfffff805800e9920)
rax=006c006e0077006f rbx=ffff81055a844000 rcx=0000000044f2fb7d
rdx=006c006e0077006f rsi=ffff810542a02280 rdi=3333333333333333
rip=fffff8057b68adc0 rsp=ffffdb8e9ef1e560 rbp=ffffdb8e9ef1e5d0
 r8=0000000000020000  r9=2779a35826cf7dd8 r10=0000000000000000
r11=ffff810542a02290 r12=0000000000000000 r13=0000000000000000
r14=ffff81055a845fc0 r15=00000000000007c4
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!RtlpHpVsContextFree+0x380:
fffff805`7b68adc0 8b4af8          mov     ecx,dword ptr [rdx-8] ds:002b:006c006e`00770067=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:  
ffffdb8e`9ef1e560 fffff805`7b689554     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpVsContextFree+0x380
ffffdb8e`9ef1e600 fffff805`7bdb1149     : 00000000`00007bc0 ffff8105`42a02100 00000000`5d400000 01000000`00100000 : nt!ExFreeHeapPool+0x4d4
ffffdb8e`9ef1e6e0 fffff805`891ae2d6     : 00000000`00000000 fffff805`7b6079f3 00000000`00000103 00000000`00000000 : nt!ExFreePool+0x9
ffffdb8e`9ef1e710 fffff805`891ad2f9     : ffffdb8e`9ef1e7e0 ffffde09`d90102f8 ffff8105`00000000 ffff8105`6384be00 : Npfs!NpReadDataQueue+0x246
ffffdb8e`9ef1e780 fffff805`7b68f825     : ffff8105`48bcd8d0 ffff8105`00006b78 00000000`58d11000 ffff8105`6384be80 : Npfs!NpFsdRead+0x259
ffffdb8e`9ef1e830 fffff805`78fb4696     : 00000000`58b54ff8 00000000`00000001 ffff8105`584460c0 fffff805`7b9f5f71 : nt!IofCallDriver+0x55
ffffdb8e`9ef1e870 fffff805`7b68f825     : ffff8105`53d13580 00000000`0f3bf590 ffffdb8e`9ef1eb80 00000000`00000000 : FLTMGR!FltpDispatch+0xd6
ffffdb8e`9ef1e8d0 fffff805`7ba75c98     : ffff8105`53d13580 00000000`00000000 ffff8105`53d13580 00000000`00000000 : nt!IofCallDriver+0x55
ffffdb8e`9ef1e910 fffff805`7ba8ca09     : ffff8105`00000000 ffffdb8e`9ef1eb80 00000000`00000000 ffffdb8e`9ef1eb80 : nt!IopSynchronousServiceTail+0x1a8
ffffdb8e`9ef1e9b0 fffff805`7b808db8     : ffff8105`54db0080 00000000`00000000 00000000`00000001 00000000`58b54ff8 : nt!NtReadFile+0x599
ffffdb8e`9ef1ea90 00000000`772e1cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0f2bec98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e1cfc


SYMBOL_NAME:  Npfs!NpReadDataQueue+246

MODULE_NAME: Npfs

IMAGE_NAME:  Npfs.SYS

IMAGE_VERSION:  10.0.19041.1526

STACK_COMMAND:  .cxr 0xfffff805800e9920 ; kb

BUCKET_ID_FUNC_OFFSET:  246

FAILURE_BUCKET_ID:  AV_Npfs!NpReadDataQueue

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {967a7d6d-529b-8728-e4d1-f4b704143503}

Followup:     MachineOwner
---------

 

Here is my data from that debug..

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

All from that I understand is Discord is the culprit... Kinda weird because I use it everyday but no problem. Only today the problem starts

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
4 minutes ago, XandersWithS said: 
Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3281

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 13839

    Key  : Analysis.Init.CPU.mSec
    Value: 937

    Key  : Analysis.Init.Elapsed.mSec
    Value: 105299

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 96


FILE_IN_CAB:  021422-13750-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8057b68adc0

BUGCHECK_P3: fffff805800e9920

BUGCHECK_P4: 0

CONTEXT:  fffff805800e9920 -- (.cxr 0xfffff805800e9920)
rax=006c006e0077006f rbx=ffff81055a844000 rcx=0000000044f2fb7d
rdx=006c006e0077006f rsi=ffff810542a02280 rdi=3333333333333333
rip=fffff8057b68adc0 rsp=ffffdb8e9ef1e560 rbp=ffffdb8e9ef1e5d0
 r8=0000000000020000  r9=2779a35826cf7dd8 r10=0000000000000000
r11=ffff810542a02290 r12=0000000000000000 r13=0000000000000000
r14=ffff81055a845fc0 r15=00000000000007c4
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050206
nt!RtlpHpVsContextFree+0x380:
fffff805`7b68adc0 8b4af8          mov     ecx,dword ptr [rdx-8] ds:002b:006c006e`00770067=????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:  
ffffdb8e`9ef1e560 fffff805`7b689554     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpVsContextFree+0x380
ffffdb8e`9ef1e600 fffff805`7bdb1149     : 00000000`00007bc0 ffff8105`42a02100 00000000`5d400000 01000000`00100000 : nt!ExFreeHeapPool+0x4d4
ffffdb8e`9ef1e6e0 fffff805`891ae2d6     : 00000000`00000000 fffff805`7b6079f3 00000000`00000103 00000000`00000000 : nt!ExFreePool+0x9
ffffdb8e`9ef1e710 fffff805`891ad2f9     : ffffdb8e`9ef1e7e0 ffffde09`d90102f8 ffff8105`00000000 ffff8105`6384be00 : Npfs!NpReadDataQueue+0x246
ffffdb8e`9ef1e780 fffff805`7b68f825     : ffff8105`48bcd8d0 ffff8105`00006b78 00000000`58d11000 ffff8105`6384be80 : Npfs!NpFsdRead+0x259
ffffdb8e`9ef1e830 fffff805`78fb4696     : 00000000`58b54ff8 00000000`00000001 ffff8105`584460c0 fffff805`7b9f5f71 : nt!IofCallDriver+0x55
ffffdb8e`9ef1e870 fffff805`7b68f825     : ffff8105`53d13580 00000000`0f3bf590 ffffdb8e`9ef1eb80 00000000`00000000 : FLTMGR!FltpDispatch+0xd6
ffffdb8e`9ef1e8d0 fffff805`7ba75c98     : ffff8105`53d13580 00000000`00000000 ffff8105`53d13580 00000000`00000000 : nt!IofCallDriver+0x55
ffffdb8e`9ef1e910 fffff805`7ba8ca09     : ffff8105`00000000 ffffdb8e`9ef1eb80 00000000`00000000 ffffdb8e`9ef1eb80 : nt!IopSynchronousServiceTail+0x1a8
ffffdb8e`9ef1e9b0 fffff805`7b808db8     : ffff8105`54db0080 00000000`00000000 00000000`00000001 00000000`58b54ff8 : nt!NtReadFile+0x599
ffffdb8e`9ef1ea90 00000000`772e1cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0f2bec98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772e1cfc


SYMBOL_NAME:  Npfs!NpReadDataQueue+246

MODULE_NAME: Npfs

IMAGE_NAME:  Npfs.SYS

IMAGE_VERSION:  10.0.19041.1526

STACK_COMMAND:  .cxr 0xfffff805800e9920 ; kb

BUCKET_ID_FUNC_OFFSET:  246

FAILURE_BUCKET_ID:  AV_Npfs!NpReadDataQueue

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {967a7d6d-529b-8728-e4d1-f4b704143503}

Followup:     MachineOwner
---------

 

Here is my data from that debug..

Can you confirm the date and time of the file (021422-13750) are those of the BSOD, and not another crash?
From what I see here, the cause of the crash was Discord, which doesn't necessarily mean that it's a bug of Discord: could be some feature it tried to access that caused a crash somewhere else. In this case, the module crashed (as alluded to by the BSOD message, a system service throwing an exception) is Npfs.SYS, of which I don't have direct knowledge, but I'm doing some research right now.
The stack is giving away a little bit of info regarding what was the system doing when it crashed: something was trying to read a file in a named pipe (a type of FIFO), called a driver (Npfs in this case), tried to read data, tried to free the kernel heap pool, then, at this nt!RtlpHpVsContextFree step, it crashed. All of this is guessing game on my part, it's a bit too advanced for my knowledge, I'd be happy if anyone with better understanding of this stuff could chime in. But here I go nonetheless, I'm going to research all that I can about this issue to try and see what it is.

After reading a bit about this Npfs, it looks like it's something that is accessed very frequently by any application using the Windows API; the fact that Discord caused the crash may or may not be telling anything useful.

It could just be a hardware instability problem, for all we know. If this were the case, it seems to me like it could be CPU / memory related.

 

Additional resources

https://www.file.net/process/npfs.sys.html

https://en.wikipedia.org/wiki/Named_pipe#In_Windows

DESKTOP PC - CPU-Z VALID | i5 4690K @ 4.70 GHz | 47 X 100.2 MHz | ASUS Z97 Pro Gamer | Enermax Liqmax II 240mm | EVGA GTX 1070Ti OC'd

HOME SERVER | HP ProLiant DL380 G7 | 2x Intel Xeon X5650 | 36GB DDR3 RDIMM | 5x 4TB LFF Seagate Constellation 7.2K | Curcial MX500 250GB | Ubuntu Server 20.04

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
2 minutes ago, LionSpeck said:

Can you confirm the date and time of the file (021422-13750) are those of the BSOD, and not another crash?
From what I see here, the cause of the crash was Discord, which doesn't necessarily mean that it's a bug of Discord: could be some feature it tried to access that caused a crash somewhere else. In this case, the module crashed (as alluded to by the BSOD message, a system service throwing an exception) is Npfs.SYS, of which I don't have direct knowledge, but I'm doing some research right now.
The stack is giving away a little bit of info regarding what was the system doing when it crashed: something was trying to read a file in a named pipe (a type of FIFO), called a driver (Npfs in this case), tried to read data, tried to free the kernel heap pool, then, at this nt!RtlpHpVsContextFree step, it crashed. All of this is guessing game on my part, it's a bit too advanced for my knowledge, I'd be happy if anyone with better understanding of this stuff could chime in. But here I go nonetheless, I'm going to research all that I can about this issue to try and see what it is.

After reading a bit about this Npfs, it looks like it's something that is accessed very frequently by any application using the Windows API; the fact that Discord caused the crash may or may not be telling anything useful.

It could just be a hardware instability problem, for all we know. If this were the case, it seems to me like it could be CPU / memory related.

 

Additional resources

https://www.file.net/process/npfs.sys.html

https://en.wikipedia.org/wiki/Named_pipe#In_Windows

RAM Swap is helping some cases? I read about that with related issues.

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
3 minutes ago, LionSpeck said:

Can you confirm the date and time of the file (021422-13750) are those of the BSOD, and not another crash?
From what I see here, the cause of the crash was Discord, which doesn't necessarily mean that it's a bug of Discord: could be some feature it tried to access that caused a crash somewhere else. In this case, the module crashed (as alluded to by the BSOD message, a system service throwing an exception) is Npfs.SYS, of which I don't have direct knowledge, but I'm doing some research right now.
The stack is giving away a little bit of info regarding what was the system doing when it crashed: something was trying to read a file in a named pipe (a type of FIFO), called a driver (Npfs in this case), tried to read data, tried to free the kernel heap pool, then, at this nt!RtlpHpVsContextFree step, it crashed. All of this is guessing game on my part, it's a bit too advanced for my knowledge, I'd be happy if anyone with better understanding of this stuff could chime in. But here I go nonetheless, I'm going to research all that I can about this issue to try and see what it is.

After reading a bit about this Npfs, it looks like it's something that is accessed very frequently by any application using the Windows API; the fact that Discord caused the crash may or may not be telling anything useful.

It could just be a hardware instability problem, for all we know. If this were the case, it seems to me like it could be CPU / memory related.

 

Additional resources

https://www.file.net/process/npfs.sys.html

https://en.wikipedia.org/wiki/Named_pipe#In_Windows

About that time, Yes today around 5PM in my timezone. It happened 3 times, so it must be one of them..

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Somehow I restarted my Discord. ITS SAFE.. I don't understand at all from that three times crash..

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
1 minute ago, XandersWithS said:

RAM Swap is helping some cases? I read about that with related issues.

May or may not be related, honestly. All I know is that the OS was trying to free up memory in order to read from a FIFO, and in doing so it crashed. I'm trying to find out if that line on top of the stack says something about the reason why.

 

2 minutes ago, XandersWithS said:

About that time, Yes today around 5PM in my timezone. It happened 3 times, so it must be one of them..

Alright, good. Since there's other crashes, could you do the same Windbg analysis to those dump files as well? You can close this current file and open the others, one at a time, repeating the same process. To find out where the files are, use Windows search to find out where the current 021422-13750-01.dmp file is, and the others should be in the same place.

DESKTOP PC - CPU-Z VALID | i5 4690K @ 4.70 GHz | 47 X 100.2 MHz | ASUS Z97 Pro Gamer | Enermax Liqmax II 240mm | EVGA GTX 1070Ti OC'd

HOME SERVER | HP ProLiant DL380 G7 | 2x Intel Xeon X5650 | 36GB DDR3 RDIMM | 5x 4TB LFF Seagate Constellation 7.2K | Curcial MX500 250GB | Ubuntu Server 20.04

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
2 minutes ago, XandersWithS said:

Somehow I restarted my Discord. ITS SAFE.. I don't understand at all from that three times crash..

If it were hardware instability (perhaps an overclock or failing hardware), the crashes would be sort-of random, inexplicable. To exclude this, we should find out what was common among all the three occurrences: the applications that were open, most importantly those that usually aren't running (you mentioned you were downloading the latest NVIDIA drivers).

DESKTOP PC - CPU-Z VALID | i5 4690K @ 4.70 GHz | 47 X 100.2 MHz | ASUS Z97 Pro Gamer | Enermax Liqmax II 240mm | EVGA GTX 1070Ti OC'd

HOME SERVER | HP ProLiant DL380 G7 | 2x Intel Xeon X5650 | 36GB DDR3 RDIMM | 5x 4TB LFF Seagate Constellation 7.2K | Curcial MX500 250GB | Ubuntu Server 20.04

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
2 minutes ago, LionSpeck said:

May or may not be related, honestly. All I know is that the OS was trying to free up memory in order to read from a FIFO, and in doing so it crashed. I'm trying to find out if that line on top of the stack says something about the reason why.

 

Alright, good. Since there's other crashes, could you do the same Windbg analysis to those dump files as well? You can close this current file and open the others, one at a time, repeating the same process. To find out where the files are, use Windows search to find out where the current 021422-13750-01.dmp file is, and the others should be in the same place.

Oh, I forgot: the reason I'm asking you to do the analysis of all the other crashes, is to see if the exception is the same among them or if the crashing component / process is different. If it was the same kind of crash, I think it would be safe to assume there is no hardware fault.

DESKTOP PC - CPU-Z VALID | i5 4690K @ 4.70 GHz | 47 X 100.2 MHz | ASUS Z97 Pro Gamer | Enermax Liqmax II 240mm | EVGA GTX 1070Ti OC'd

HOME SERVER | HP ProLiant DL380 G7 | 2x Intel Xeon X5650 | 36GB DDR3 RDIMM | 5x 4TB LFF Seagate Constellation 7.2K | Curcial MX500 250GB | Ubuntu Server 20.04

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
22 minutes ago, LionSpeck said:

May or may not be related, honestly. All I know is that the OS was trying to free up memory in order to read from a FIFO, and in doing so it crashed. I'm trying to find out if that line on top of the stack says something about the reason why.

 

Alright, good. Since there's other crashes, could you do the same Windbg analysis to those dump files as well? You can close this current file and open the others, one at a time, repeating the same process. To find out where the files are, use Windows search to find out where the current 021422-13750-01.dmp file is, and the others should be in the same place.

Yes sir. Thank you very much about telling me the location of that file and the others :))

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
33 minutes ago, LionSpeck said:

Oh, I forgot: the reason I'm asking you to do the analysis of all the other crashes, is to see if the exception is the same among them or if the crashing component / process is different. If it was the same kind of crash, I think it would be safe to assume there is no hardware fault.

Both Chrome.exe (1-2) and Discord.exe (3) i dont know what cause of that chrome

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
23 minutes ago, XandersWithS said:

Both Chrome.exe (1-2) and Discord.exe (3) i dont know what cause of that chrome

Ok, this sort-of confirms my theory that it isn't application-related. Could you post the results of the analyses of the two other dumps? If the module crashing (Npfs.SYS) is the same, and the content of the stack (what was being done more precisely) is similar, then there could be a correlation, and I think we could exclude hardware fault. On the contrary, if the three crashes are completely unrelated, I would believe that the problem is some unstable OC (I don't know if any of your hardware is currently overclocked, or XMP is enabled, or any of that) or some hardware that is failing.

DESKTOP PC - CPU-Z VALID | i5 4690K @ 4.70 GHz | 47 X 100.2 MHz | ASUS Z97 Pro Gamer | Enermax Liqmax II 240mm | EVGA GTX 1070Ti OC'd

HOME SERVER | HP ProLiant DL380 G7 | 2x Intel Xeon X5650 | 36GB DDR3 RDIMM | 5x 4TB LFF Seagate Constellation 7.2K | Curcial MX500 250GB | Ubuntu Server 20.04

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
On 2/14/2022 at 7:28 PM, LionSpeck said:

Ok, this sort-of confirms my theory that it isn't application-related. Could you post the results of the analyses of the two other dumps? If the module crashing (Npfs.SYS) is the same, and the content of the stack (what was being done more precisely) is similar, then there could be a correlation, and I think we could exclude hardware fault. On the contrary, if the three crashes are completely unrelated, I would believe that the problem is some unstable OC (I don't know if any of your hardware is currently overclocked, or XMP is enabled, or any of that) or some hardware that is failing.

Im sorry for replying too late.. I think that problem is gone for now.. Thank you very much about your help debugging that crash:) Have a good day and stay safe 🙂

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author
On 2/14/2022 at 7:28 PM, LionSpeck said:

Ok, this sort-of confirms my theory that it isn't application-related. Could you post the results of the analyses of the two other dumps? If the module crashing (Npfs.SYS) is the same, and the content of the stack (what was being done more precisely) is similar, then there could be a correlation, and I think we could exclude hardware fault. On the contrary, if the three crashes are completely unrelated, I would believe that the problem is some unstable OC (I don't know if any of your hardware is currently overclocked, or XMP is enabled, or any of that) or some hardware that is failing.

I never do something related to overclock, is it possible if bluescreen affected by clean or not inside of my PC.. I kinda struggled with my English to explain.. I haven't clean my inside PC yet.. maybe that problem may caused because of that.

Ryzen 5 2600 / MSI B350 Tomahawk / GALAX RTX 2060 6GB (1-Click OC) / Corsair Vengeance LPX 2666Mhz 8x2GB / ADATA SX6000 LITE 512 M.2 NVME / KLEVV 128 GB SATA / Seagate Barracuda 2TB 7200rpm / Seasonic Focus Gold 550W / Tecware Nexus C

Upgrade Plan: CPU: Ryzen 5 3600 RAM: GSkill TridentZ RGB 3200MHz/3600MHz MB: MSI B450 TOMAHAWK MAX

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
50 minutes ago, XandersWithS said:

Im sorry for replying too late.. I think that problem is gone for now.. Thank you very much about your help debugging that crash:) Have a good day and stay safe 🙂

Don't worry! I'm sorry we couldn't figure out the exact cause of the issue, but I'm glad it hasn't happened again.

 

49 minutes ago, XandersWithS said:

I never do something related to overclock, is it possible if bluescreen affected by clean or not inside of my PC.. I kinda struggled with my English to explain.. I haven't clean my inside PC yet.. maybe that problem may caused because of that.

I don't think that could be the reason; the worst that could do is make the fans louder and make the PC run a little hotter.

DESKTOP PC - CPU-Z VALID | i5 4690K @ 4.70 GHz | 47 X 100.2 MHz | ASUS Z97 Pro Gamer | Enermax Liqmax II 240mm | EVGA GTX 1070Ti OC'd

HOME SERVER | HP ProLiant DL380 G7 | 2x Intel Xeon X5650 | 36GB DDR3 RDIMM | 5x 4TB LFF Seagate Constellation 7.2K | Curcial MX500 250GB | Ubuntu Server 20.04

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Windows

×