And we’re back. It wouldnt let me reply in my other thread sorry which is belw.
Im still getting the #132 error.
I’ve had discord completely closed getting the same error.
I’ve also disabled the Xbox / windows dvr recorder as well.
FYI: the Motherboard is running the F12E which is the latest version from what I can see. (Was this version from the very beginning)
Also had the following issue:
Fix CHKDSK error ‘volume bitmap is incorrect’. Check disk gives this error when the master file table’s (MFT) bitmap file is incorrectly implemented.
^ Fixed this with the Check Disk thingo. (had a mate find this one)
Since the below crashes, I’ve disabled the realtek Wireless adapter and am just working off a wired connection.
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
C:\Windows\LiveKernelReports
On Fri 29/05/2020 1:58:28 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060120-9359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA0 (0x10E, 0xA, 0x0, 0xDC38)
Error: INTERNAL_POWER_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=Microsoft Corporation)
description: NT Kernel & System
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 29/05/2020 11:35:20 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052920-9062-01.dmp
This was probably caused by the following module: rtwlane01.sys (0xFFFFF8052D600117)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8052D600117)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rtwlane01.sys
product: [Realtek PCIEWireless LAN PCI-E NIC ](http://www.google.com/search?q=Realtek PCIEWireless LAN PCI-E NIC )
company: [Realtek Semiconductor Corporation ](http://www.google.com/search?q=Realtek Semiconductor Corporation )
description: Realtek PCIE NDIS Driver 69342 29887
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: rtwlane01.sys (Realtek PCIE NDIS Driver 69342 29887, Realtek Semiconductor Corporation ).
Google query: [rtwlane01.sys Realtek Semiconductor Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL](http://www.google.com/search?q=rtwlane01.sys+Realtek Semiconductor Corporation +DRIVER_IRQL_NOT_LESS_OR_EQUAL)
On Fri 29/05/2020 11:35:20 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ndis.sys (ndis!NdisMAllocateNetBufferSGList+0x68C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8052D600117)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=Microsoft Corporation)
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 29/05/2020 9:38:55 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052920-9109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x192 (0xFFFF9683BE0E5080, 0xFFFF9683BE107638, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=Microsoft Corporation)
description: NT Kernel & System
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 29/05/2020 9:10:49 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052920-9234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xD1 (0xFFFFF80500400A02, 0xA, 0x8, 0xFFFFF80500400A02)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=Microsoft Corporation)
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 28/05/2020 2:54:29 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052820-9656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8077BD20EA0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](http://www.google.com/search?q=Microsoft® Windows® Operating System)
company: [Microsoft Corporation](http://www.google.com/search?q=Microsoft Corporation)
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.