"often" BSoD after years(8+) without any

K

kamidak

Member
Joined
Nov 29, 2021
Posts
8
I have this PC for more than 8 years and never had a single BSoD but since last week i've some weird and random ones;
It begin last from nowhere, i turned on like any other day and after few minutes i opened the Discord and my first BSoD happened. The PC restarted "automaticly" but right after desktop appears it freezed and BSoD again, this one was the weirdest one, when the rebooted, the entire PC freezed in the ASUS screen (my motherboard), i had to "brute force" restart and the red light on the motherboard (inside, i can see by the side/case) didn't go off and it stuck in the black screen... After i turned if OFF for a few seconds i turned on and it booted "normally". Since it didn't crashed again, i back to my "normal routine" with discord talking with friends, watching some Stream in the background and playing Path of Exile but after few hours it BSoD again.
This time i took a time to run all kind of scan possible; HD, mem. Test, file integraty check and for the last did a windows update (had 1-2 pending KB update). After all those verification it seemed fixed and i start use/play with my PC with some software open just in case, i have been using CrystalDiskInfo, Real Temp and MSI Afterburner to see if something is "broken", everything looks ok.
Was a few days (1 week) without any problem, playing or just watching stuffs without any sign of problem but today (11/29) it happened again right after the windows boot (desktop)... So i decide look for help to try find wtf is going on...

(from the last day, the only thing i updated was DbD via steam; when the first BSoD happend last week, the only thing i remember that it updated the day before (or before that), was Discord)

The code that appears on all BSoD: System Service Exception


  • System Manufacturer?
  • Laptop or Desktop? Destkop
  • Exact model number (if laptop, check label on bottom)
  • OS ? (Windows 10, 8.1, 8, 7, Vista) win10
  • x86 (32bit) or x64 (64bit)? x64
  • (Only for Vista, Windows 7) Service pack?
  • What was original installed OS on system? win7
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM, upgrade to win10 few months after the release
  • Age of system? (hardware) almost 10 years
  • Age of OS installation? +-5 years with win10
  • Have you re-installed the OS? no (tbh i don't ever remember LUL)
  • CPU Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz 3.40 GHz
  • RAM (brand, EXACT model, what slots are you using?) 16GB (4x4gb)
  • Video Card gtx750ti
  • MotherBoard - (if NOT a laptop) Asus P8Z77-M
  • Power Supply - brand & wattage (if laptop, skip this one) Corsair 750w (5+ years old)
  • Is driver verifier enabled or disabled? i dunno what is this :/
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) firewall always ON. Windows Defender ninja run in the background sometimes and i have the free Malwarebytes where i do some scan each 2 month's ich
  • Are you using proxy, vpn, ipfilters or similar software? no
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) no
  • Are you currently under/overclocking? Are there overclocking software installed on your system? no

Speccy = http://speccy.piriform.com/results/KHYX3WHc586Y1F52vQYdfok
windows MiniDump files = https://easyupload.io/hwblbu
SysnativeFileCollectionApp = https://easyupload.io/brc4am

My suspecious is that my PSU is dying and when some power oxilation happen it just BSoD me because some hardware have lack of energy... but this is a just a HUGE guess since i have 0 knowledge about those things

sry for my english
 
Last edited:
Please ATTACH the SysnativeFileCollectionApp and windows MiniDump files to your next post. Please do not use any 3rd party hosting sites. The links provided are asking for passwords.

Just attach the files, please.

Regards. . .

jcgriff2
 
Hi...

The bugcheck on all 5 BSODs = 0xe6 = illegal DMA operation was attempted by a driver being verified.

"NT" is named as the probable cause, which is impossible as it is the Windows kernel.

Re-run Driver Verifier, be sure to check "DMA Checking" box in options. Use system, if BSOD occurs, rerun the Sysnative/jcgriff2 collection app; attach output.

Thanks. . .

jcgriff2
 
5? when was the 5th one?? šŸ¤£
I don't think (remember) i did the Driver Verifier... pretty sure i didn't because i don't have the System Restore Point.
I'll take a time to read the Driver Verifier guide with attention before i try it, seems pretty "dangerous" for people like me without deep experience and i can't/want mess up the things šŸ§
thank you so much for now!
 
sorry for my ignorance but i did the driver verifier thing, it should show me any notification after the re-boot or is a "passive" (background data collector) stuff? I suppose it is ON by default
 
It'll run in the background, you can verify that it's running correctly by entering the following command in command prompt:

Rich (BB code): 
verifier /query
 
@jcgriff2 all the dump files appear to be Stop 0x3B?

Rich (BB code): 
1: kd> .cxr 0xffff95844404add0
rax=f7fff3bf06650fe8 rbx=fffff3bf00200290 rcx=00000000000000c8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8055fe8b926 rsp=ffff95844404b7d8 rbp=fffff3bf0665bfe8
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=f7fff3bf06650fe8 r12=0000000000000000 r13=fffff3bf06631000
r14=0000000000000000 r15=fffff3bf03bc8610
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!RtlRbRemoveNode+0x536:
fffff805`5fe8b926 498b4308        mov     rax,qword ptr [r11+8] ds:002b:f7fff3bf`06650ff0=????????????????

Rich (BB code): 
0: kd> .cxr 0xfffff8046dca6920
rax=0000000000000001 rbx=ffffd301cf1e3ee0 rcx=ffffd301cf1e3ee8
rdx=dfffd301cf1e3ee8 rsi=ffffd301ce789080 rdi=ffffd301d6c6d521
rip=fffff8046a8803e6 rsp=ffff8300c2cae1f0 rbp=ffff8300c2cae2b9
 r8=0000000000000000  r9=0000000000000000 r10=fffff80465448180
r11=ffff8300c2cae3b0 r12=ffffd301d6c6d510 r13=0000000000000005
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!KeWaitForMultipleObjects+0x246:
fffff804`6a8803e6 48390a          cmp     qword ptr [rdx],rcx ds:002b:dfffd301`cf1e3ee8=????????????????

Rich (BB code): 
3: kd> .cxr 0xffffb90116c3f920
rax=ffff8e0f80985b40 rbx=ffffb901165ec180 rcx=f7ff8e0f80986980
rdx=ffff8e0f84797dd0 rsi=ffff8e0f84797d10 rdi=ffff8e0f80985b20
rip=fffff80149686510 rsp=ffff88065686f670 rbp=ffff88065686fb80
 r8=0000000000000001  r9=0000000000000000 r10=ffff8e0f799e7ed0
r11=ffff8e0f83cb06b0 r12=0000000000000000 r13=0000000000000002
r14=ffff8e0f84797dc8 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!IopCompleteRequest+0x530:
fffff801`49686510 483901          cmp     qword ptr [rcx],rax ds:002b:f7ff8e0f`80986980=????????????????

All the crashes appear to be due to bit flips and this is almost guaranteed to be some form of hardware failure, in particular RAM or the processor. I would suggest running MemTest86 for at least 4-8 passes (preferably 8).
 
x BlueRobot said:
It'll run in the background, you can verify that it's running correctly by entering the following command in command prompt:

Rich (BB code): 
verifier /query
Click to expand...
Sorry, the 15 minute rules for edit have caught me off guard.
Yeah, i can tell Driver Verifier is running by the terrible FPS in-game :ROFLMAO:, i don't think i'll try play anything for a while just until i have something to "work with" (crash data).

damn, RAM or Processor... this can be a headache. Is weird because, after the day where i had 3 BSOD, i did my routine playing Path of Exile with juicy maps, 100% usage of everything the game can, easily consuming 10G mem., 100% GPU mem., CPU at least 60%+, literally "frying" everything for a entire week 10 hours straight daily but yet nothing new from my routine.
In fact, the only thing i noticed tracking after the first day of BSOD was the CPU temp, where in most of time in-game was above 80ĀŗC and sometimes reaching 91ĀŗC.

91c.png


Since i live in a small town i had to order a decent thermal paste via internet. It arrive today and i just changed it. Also i changed my PSU with my old one just in case (corsair 500w), i was using the 750w one because this one was doing a loud noise like a mixer, i bought a machine oil and follow a tutorial to clean it and so far the noise is gone. (if the noise back i'll just swap back)

I need find my pen-drive somewhere here to do the mem. test, i did the Windows10 mem. test and it report no issues.
Thanks once again, i'll keeping the Drive Verifier ON for a while and see if something happens.
 
If you don't experience any crashes with Driver Verifier within the next 24 hour period then I would suggest you stop running it.
 
x BlueRobot said:
If you don't experience any crashes with Driver Verifier within the next 24 hour period then I would suggest you stop running it.
Click to expand...
hmm... have been 2 days already without BSOD, leave the Driver Verifier running can do any ""damage"" to PC? I'm just watching stuffs here if have no problem leave it on i can do another day or 2 just i case šŸ¤”
 
kamidak said:
leave the Driver Verifier running can do any ""damage"" to PC? I'm just watching stuffs here if have no problem leave it on i can do another day or 2 just i case šŸ¤”
Click to expand...
No, it just wouldn't be worth running, especially when it can be quite resource intensive.
 
x BlueRobot said:
No, it just wouldn't be worth running, especially when it can be quite resource intensive.
Click to expand...
Ok. So since is running already i'll let it for today then turn it OFF when i go to bed (verifier /reset).
Once again, thank so much everyone for helping... if another BSOD heppens i'll turn it ON with the 24hour cycle. Sadge
 
Please post a verifier /querysettings before turning off the tool.



Code: 
3: kd> !verifier
fffff8014a02a5c0: Unable to get verifier list



How come Malwarebytes entries are located in the hosts file?
 
zbook said:
Please post a verifier /querysettings before turning off the tool.
Click to expand...
you mean:
Code: 
C:\WINDOWS\system32>verifier /querysettings

Sinalizadores do Verificador: 0x001a89ab

  Sinalizadores PadrĆ£o:

    [X] 0x00000001 Pool especial.
    [X] 0x00000002 ForƧar verificaĆ§Ć£o de IRQL.
    [X] 0x00000008 Rastreamento de pool.
    [ ] 0x00000010 VerificaĆ§Ć£o de E/S.
    [X] 0x00000020 DetecĆ§Ć£o de deadlock.
    [X] 0x00000080 VerificaĆ§Ć£o de DMA.
    [X] 0x00000100 VerificaƧƵes de seguranƧa.
    [X] 0x00000800 VerificaƧƵes diversas.
    [X] 0x00020000 VerificaĆ§Ć£o de compatibilidade DDI.

  Sinalizadores Adicionais:

    [ ] 0x00000004 SimulaĆ§Ć£o de recursos baixos aleatĆ³ria.
    [ ] 0x00000200 ForƧar solicitaƧƵes de E/S pendentes.
    [ ] 0x00000400 Log de IRP.
    [ ] 0x00002000 VerificaĆ§Ć£o de MDL invariĆ”vel para pilha.
    [ ] 0x00004000 VerificaĆ§Ć£o de MDL invariĆ”vel para driver.
    [X] 0x00008000 Teste de fuzzing de atraso da estrutura de energia.
    [ ] 0x00010000 VerificaĆ§Ć£o de interface de porta/miniporta.
    [ ] 0x00040000 SimulaĆ§Ć£o de recursos baixos sistemĆ”tica.
    [X] 0x00080000 VerificaĆ§Ć£o de compatibilidade DDI (adicional).
    [ ] 0x00200000 VerificaĆ§Ć£o de NDIS/WIFI.
    [ ] 0x00800000 Teste de fuzzing de atraso da sincronizaĆ§Ć£o do kernel.
    [ ] 0x01000000 VerificaĆ§Ć£o de comutador VM.
    [ ] 0x02000000 VerificaƧƵes de integridade do cĆ³digo.

  Sinalizadores Internos:

    [X] 0x00100000 Sinalizadores do Verificador Estendido (internos).

    [X] Indica que o sinalizador estĆ” habilitado.

  Modo de InicializaĆ§Ć£o:

    Persistent

  Regras:

    Todas as regras estĆ£o usando configuraƧƵes padrĆ£o

  ExtensƵes:

    wdm: rules.all

  Drivers Verificados:

    cimfs.sys
    vboxnetadp6.sys
    asupio.sys
    asio.sys
    nvlddmkm.sys
    hecix64.sys
    rt640x64.sys
    nvvad64v.sys
    nvmoduletracker.sys
    nvvhci.sys
    logi_joy_bus_enum.sys
    logi_joy_xlcore.sys
    lgbusenum.sys
    lgjoyxlcore.sys
    nvhda64v.sys
    rtkvhd64.sys
    dump_diskdump.sys
    dump_storahci.sys
    dump_dumpfve.sys
    lgcoretemp.sys
    logi_joy_vir_hid.sys
 
zbook said:
How come Malwarebytes entries are located in the hosts file?
Click to expand...
They look like blocked domain names for known adware/spyware sites.

kamidak said:
you mean:
Click to expand...
That's right.

kamidak said:
Once again, thank so much everyone for helping... if another BSOD heppens i'll turn it ON with the 24hour cycle. Sadge
Click to expand...
I would recommend running MemTest86 as mentioned in my previous post if you experience another crash.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top