Windows 10: BSOD stared to appear since a week ago.

Hi. I'm using Macbook Pro 2018 15"i7-8750H, 16 GB RAM, 256 GB SSD, Radeon Pro 560x.


Suddenly I've been getting this BSOD since a week ago.


Here's dump:


******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************IRQL_NOT_LESS_OR_EQUAL aAn attempt was made to access a pageable or completely invalid address at aninterrupt request level IRQL that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: 0000000000000020, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation only on chips which support this level of statusArg4: fffff8053546ae75, address which referenced memoryDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 1 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-GES2S9U Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 1 Key : Analysis.Memory.CommitPeak.Mb Value: 60 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: aBUGCHECK_P1: 20BUGCHECK_P2: 2BUGCHECK_P3: 1BUGCHECK_P4: fffff8053546ae75WRITE_ADDRESS: 0000000000000020 BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemTRAP_FRAME: fffff80538e7c660 -- .trap 0xfffff80538e7c660NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=000001cb5486ae7c rbx=0000000000000000 rcx=ffffe68325538000rdx=000001cb00000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8053546ae75 rsp=fffff80538e7c7f0 rbp=fffff80538e7c8f0 r8=0000000000000000 r9=0000000000000000 r10=ffffe6832a2a5b48r11=fffff80538e7ca10 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na pe ncnt!KiExecuteAllDpcs+0x2e5:fffff805`3546ae75 49894720 mov qword ptr [r15+20h],rax ds:00000000`00000020=????????????????Resetting default scopeSTACK_TEXT: fffff805`38e7c518 fffff805`355d32e9 : 00000000`0000000a 00000000`00000020 00000000`00000002 00000000`00000001 : nt!KeBugCheckExfffff805`38e7c520 fffff805`355cf62b : ffffd500`18b29ab0 fffff805`38e7ca20 ffffe683`35764000 fffff805`4e91b297 : nt!KiBugCheckDispatch+0x69fffff805`38e7c660 fffff805`3546ae75 : fffff805`309e0f80 ffffe683`257f0000 fffff805`38e7c8f0 00000000`00000000 : nt!KiPageFault+0x46bfffff805`38e7c7f0 fffff805`3546a4ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2e5fffff805`38e7c930 fffff805`355c5024 : 00000000`00000000 fffff805`309de180 fffff805`35991400 ffffe683`3933d080 : nt!KiRetireDpcList+0x1effffff805`38e7cb60 00000000`00000000 : fffff805`38e7d000 fffff805`38e76000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84SYMBOL_NAME: nt!KiExecuteAllDpcs+2e5MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 2e5FAILURE_BUCKET_ID: AV_nt!KiExecuteAllDpcsOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {b88a28a0-fcde-99e9-6174-619833d00ab9}Followup: MachineOwner



I updated graphics driver days ago.

It's custom driver bootcampdrivers.com but there's no one who complains about BSOD in forum.

I ran Apple Hardware Test, and it says there's no problem with hardware.

What's the problem??

:)

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.

 

Frequent and random appearing BSOD 'internal power error'.


Update:
I did steps 6 and 7:

BIOS reset. I choose the 'optimized defaults':







And then I did steps 8 through 11.

Next step is the memtest86+. I created a bootable DVD, and tested if it works. (It does.) I plan these memory-tests the coming nights.
However, I can't see how I can test every SDRAM module separately. How do I do that?

(NB: After closing my game yesterday, I got the first BSOD in weeks, with a (new) message: "reference by pointer".)

 

BSODs start from a week ago

Hi there!

My dell XPS 13 started randomly crash since a week ago. Sometimes it happened from boot, sometimes it happened when waking from hibernation. Sometimes it happened when I was using it.

I followed the online wiki about posting problems on BSOD. The required files are included below. For the computer specification, I thought the MSinfo contain them. Mine is DELL xps 13, bought last November and had functioned all right until last week.

Thanks in advance for any possible help!

Link to the dump files and specification of machine.

BSOD

Edited:

I checked online and found someone with similar problem as me: bfe.dll causes the crash with Macfee firewall installed. I unable the firewall and still wait to see whether it will crash again.

BSOD related to Base Filtering Engine

Yet another question: I check the dfe.dll file and found it was updated 3.29 when I didn't see any updates in the
"View Your Update history" at that time. Also, the "previous version" tab of the 3.29-modified
dfe.dll shows nothing. Could it be a virus change the library? I used
sfc /scanfile" and it showed no violation. Still confused about the cause of BSOD.

Moved from: Windows / Windows 10 / Windows update, recovery, & backup