010220-7968-01.dmp 1/2/2020 9:05:30 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff71c`633b44b5 ffff8d8e`b12adfe0 00000000`00000000 win32kbase.sys win32kbase.sys+44b5 Base Win32k Kernel Driver Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.1 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\010220-7968-01.dmp 16 15 18362 1,065,700 1/2/2020 9:06:16 AM


BSOD back again even with a new power supply. :(

=With two different trigger events I would start to think seriously that the disk is corrupted., or just starting to fail :-(

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

my guess is OS corruption or bad hard drive.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Seeing how you continue to have BSODs that can be caused by "invalid memory, bad/corrupt drivers, bad hardware", I'm going back to what you said earlier...

I haven't swapped everything. However, when I put the GTX in the other machine with the Ryzen 5 I get a BSOD. It doesn't get a BSOD without it. It works fine. So I assumed it was the GTX 1050 so I put a GT710 in the Ryzen 7 and I still get a BSOD.

If two different videocards get a BSOD it may be the motherboard that's broken, or more likely the PCIe slot you're putting the cards in.

---

Seeing how you continue to have BSODs that can be caused by "invalid memory, bad/corrupt drivers, bad hardware", I'm going back to what you said earlier...

I haven't swapped everything. However, when I put the GTX in the other machine with the Ryzen 5 I get a BSOD. It doesn't get a BSOD without it. It works fine. So I assumed it was the GTX 1050 so I put a GT710 in the Ryzen 7 and I still get a BSOD.

If two different videocards get a BSOD it may be the motherboard that's broken, or more likely the PCIe slot you're putting the cards in.

Hmm....I'll try that Idea. Thanks.!

Today when I booted it up it did something odd. The speaker gave me about 3 beeps and would not boot up. I hit the reset button and it booted up fine.

Three beeps that repeat after a pause and occur when you power on your computer indicate a problem with the system memory. Three beeps that play and then stop as the computer starts successfully mean that the BIOS was restored.

---

Three beeps that repeat after a pause and occur when you power on your computer indicate a problem with the system memory. Three beeps that play and then stop as the computer starts successfully mean that the BIOS was restored.

Time to drop G.Skill. Its brand new memory and its in the other computer too.

I did run Memtest a second time it took 3 hours 22 minutes to finish and it passed. I think I just take out all the parts and get a new MB. A different brand.

have you tried re-installing Windows to eliminate the possibility that the OS is corrupted?

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

have you tried re-installing Windows to eliminate the possibility that the OS is corrupted?

No but its a brand new computer I built not that long ago with a new clean install of Windows 10. And I reset it once after I put the SSD drive in.

given how many different BSODs you're experiencing, I think it's a strong possibility that your problem is software related.

I would wipe it out and reinstall Windows from scratch to be sure.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

All his BSODs point to hardware and driver problems, not to the OS being the problem. Typically when you have OS problems, you'll notice long start up times, damaged, corrupted or missing files, Windows starting with chkdisk, sudden shutdowns, failures to boot up, etc.

Just because Windows BSODs a lot doesn't mean it's Windows that's the cause.

IRQL_NOT_LESS_OR_EQUAL the blue screen of death, in this case, appears as a result of the conversion process kernel mode memory area while the unacceptably high level for it IRQL is used. This error may be due to a malfunction of the drivers, system services or incompatible software, like a software emulator or antivirus software.

KMODE_EXCEPTION_NOT_HANDLED this causes a blue screen as a result of an error in the kernel process so that you try to run an unknown instruction. It may be associated with incompatibility or equipment malfunction and errors in drivers or system services.

ATTEMPTED_WRITE_TO_READONLY_MEMORY is issued if a driver attempts to write to a read-only memory segment.

SYSTEM_SERVICE_EXCEPTION this Stop Error is usually received in cases of excessive paged pool usage and can occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

The trouble with all the driver related problems he may have is that all the above errors happened either in ntoskrnl.exe, win32k.sys or win32kfull.sys
You have to know what each of these are to understand the cause:

- ntoskrnl.exe is the Windows kernel. It holds several sub systems: Cache Manager, I/O Manager, Configuration Manager, Local Procedure Call, Memory Manager, Process Structure, Object Manager and Security Reference Monitor. Collectively, they form part of Executive services and System Services. Without it, Windows won't be Windows. But before you go "Well, that says that Windows is corrupt", it doesn't. It just crashes in here when it happened in one of the sub-systems above.

- win32k.sys is the Graphics Device Interface and provides functionality for outputting graphical content to monitors, printers and other output devices. A crash in this points to problems with the graphics drivers, or with the graphics hardware, or any hardware the graphics hardware is connected to.

- win32kfull.sys is a kernel mode device driver for Windows 10. Most of the errors within it are caused by hardware problems, outdated firmware, corrupt drivers.

As you can see, the overall relation is trouble with drivers, or hardware. And also because the problems started when he added a videocard. If he had never added the second videocard, he may not have had any trouble.

Then the clincher, the 3 beeps: these are POST beeps, at cold start up. One beep indicates all is OK, as soon as there are other beeps, best look them up. https://www.computerhope.com/beep.htm, depending on the sort of BIOS, or the computer, it can indicate problems with memory, or a dying motherboard. Problems with memory don't always point to memory being the problem, it can also be a problem with the motherboard.

A corrupt Windows will never give 3 beeps at cold start up. A corrupt Windows will not give any sounds. Reinstalling Windows at this point is IMHO a waste of time, and when more hardware trouble happens while installing it, it can cause full corruption with no option to boot. Besides, when he has gotten his new motherboard, he may have to reinstall Windows anyway.

---

Someone a while back suggested using WinDbg. I opened the last .dmp file and I think it thinks the issue is with either memory Corruption or some software I have installed DashLane. I uninstalled and reinstalled Dashlane and I haven't had the issue yet. Waiting for the next BSOD.....

I've never used WinDbg before but those are the two things that popped up.

but the problem continued to occur after he removed the GPU also.

The fact that all his BSODs, though varied, were related to core pieces of the OS, is why I lean towards OS corruption. It's very possible that there are issues with those modules themselves due to some previous event. Something as small as an improper shutdown can corrupt Windows, and that corruption can propagate.

the motherboard beeps *could* be relevant, or it could be a random event. Sounds like it only happened one time. I've certainly had this happen on several boards, sometimes on rare occasions it just doesn't boot right and need a retry.

but I at least appreciate that you are making claims and backing them up, rather than telling the guy to throw random parts at the thing. replacing the PSU was pointless.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

At least the computer is a lot more quiet that it was before. I like the new power supply. :) Even though it didn't fix the issue. lol

4th day without a BSOD. I reinstalled Dashlane is the only thing I've did.

4th day without a BSOD. I reinstalled Dashlane is the only thing I've did.

Usually userspace programs shouldn't be able to corrupt kernel memory no matter what, but I know many supposedly userspace programs come with kernel driver/modules for various legitimate purposes. Assuming you are talking about the app from dashlane.com, unpacking the installer shows a bunch of worryingly-named dlls like UAC.dll and System.dll. So it's possible it has modules loaded into kernel that could corrupt kernel memory due to bugs or file corruption. Unfortunately I don't know enough about Windows programs to figure out what those dll are doing...

Hopefully that's the end of your BSOD story. Debugging these are always annoying, but looks like you got lucky with windbg. :-)

---

4th day without a BSOD. I reinstalled Dashlane is the only thing I've did.

Usually userspace programs shouldn't be able to corrupt kernel memory no matter what, but I know many supposedly userspace programs come with kernel driver/modules for various legitimate purposes. Assuming you are talking about the app from dashlane.com, unpacking the installer shows a bunch of worryingly-named dlls like UAC.dll and System.dll. So it's possible it has modules loaded into kernel that could corrupt kernel memory due to bugs or file corruption. Unfortunately I don't know enough about Windows programs to figure out what those dll are doing...

Hopefully that's the end of your BSOD story. Debugging these are always annoying, but looks like you got lucky with windbg. :-)

I thought so..... till just now.

010820-7640-01.dmp 1/8/2020 8:32:14 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00061941 00007ffc`81536f80 00000000`0000001d ffffe087`75f79b00 ntoskrnl.exe ntoskrnl.exe+1c14e0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.18362.535 (WinBuild.160101.0800) x64 ntoskrnl.exe+1c14e0 C:\Windows\Minidump\010820-7640-01.dmp 16 15 18362 888,244 1/8/2020 8:32:59 AM

I have ordered new memory. Just in case.

8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: 00007ffc81536f80
Arg3: 000000000000001d
Arg4: ffffe08775f79b00

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HA01I3L

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 3

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

Key : Analysis.System
Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 61941

BUGCHECK_P2: 7ffc81536f80

BUGCHECK_P3: 1d

BUGCHECK_P4: ffffe08775f79b00

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: WmiPrvSE.exe

STACK_TEXT:
ffffe087`75f79958 fffff803`4960d24a : 00000000`0000001a 00000000`00061941 00007ffc`81536f80 00000000`0000001d : nt!KeBugCheckEx
ffffe087`75f79960 fffff803`495cf520 : ffffb00f`30c92040 000001d6`fcf25be0 00000000`00000000 ffffb00f`30cbdc60 : nt!MmAccessFault+0x19a6aa
ffffe087`75f79b00 00007ffc`81536f80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x360
00000022`89efd658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`81536f80


MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

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