I recent got a new PC. Updated everything and get this error usually within a minute or so of wondering around the world. Everything runs smoothly up until the crash.
Critial Error
Error #132 (numbers) Fatal acceptation
Process Id: 3048
Exception:Access Violation
The instruction at ‘long number’ reference at memory ‘long number’.
The memory could not be read.
I’ve exited discord and got rid of all other potential overlays.
Gone to every possible bnet and wow executable to make sure its run as administrator.
Actually had another error and had to take PC back to shop. Fully formated with classic wow as almost the only thing running on fresh instal and still this same error.
I see you have a Gigabyte X570, I was having the same problem with my MSI X570. My X570 had released a BIOS update recently, I updated it yesterday and have not experienced a problem since the update.
See if there is an update available for your BIOS.
Updating BIOS is technically not within our realm of support at Blizzard since it requires physical access to the device. Though I did want to provide a word of caution here.
If flashing the BIOS is not something you are familiar with I highly recommend having a local PC technician do it for you. Doing this process incorrectly can cause the computer to stop working permanently.
I would like to add to Kaldraydis’ advice that, if you are going to update your BIOS, try if at all possible to avoid updating with beta BIOS revisions. You really chance things with betas. But if you understand the risks, more power to you.
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.
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.
Hey, Chippiesyo! There’s been some known issues with the AMD Ryzen 3600/3600X processor having issues with BIOS versions after AGESA 1.0.0.3abb/1.0.0.3abba. It’s been causing game crashes, and random BSOD crashes.
It can help to revert to either F2 or F3 for the specific motherboard. This is not something that we directly support or can recommend, please only do so if you are comfortable with these changes or contact a local technician for assistance.
Just bringing this up to you, Caterpepi, but I have noticed that the game has produced a few error 132s on 1.0.0.3abb, but these ones did not crash the game. They were simply reported and noted that the memory was not “executed.” I’m at a loss for words here. Yeah, the game didn’t crash, but why would these errors generate now? Any idea?
Update:
Saw that another error 132 log produced, and now I can pretty much confirm that it randomly happens when I exit the game, hence why there is no actual crash window that pops up while gaming. It happens upon closing the client. This is on 1.0.0.3abb. Don’t know if anyone else has noticed this behavior in their retail WoW folder.
Update 2:
Did further testing. It seems that if I have the (beta) Bnet app set to exit upon entering WoW, then exit WoW, the client produces a crash error log. If I have the app minimize in the tray or otherwise, the client will not crash. Maybe this can get passed along, Caterpepi? I mean, it’s practically a non-issue, as it doesn’t affect anything while gaming. Just thought I’d bring it up.
Interesting, Crosswinds! I’ll get this added to our tracking. Thanks for the details At this moment, we’ve been requested to forward the 3600/3600X related issues to AMD support regarding game crashes, won’t launch, error #132, and the BEX 64 errors.
We’d like to get the contact information to you, could you contact our technical support team for the contact details? Due to this being a specific issue, we’d like to provide these details to individuals who we have confirmed the matter with. You can link this thread, I’ll leave notations on this thread and account just in case
I can already tell you, Caterpepi, that I’m not liking their support team’s observation of the problem. “System stability issue.” It’s not my hardware. If it were, I’d be having way more problems. This is singled out on WoW at later AGESA versions. Are you positive they’re aware of people like me contacting them?
I ask because it already feels like I’m being brushed off as if I don’t know what I’m doing.
This is the information our Quality Assurance team received from AMD to help investigate the issue. Unfortunately beyond that we can’t really comment - your best bet is to continue contacting them for now and do what you can to link all of the documentation you’ve already given us. Since they’re not our support we can’t speak for anything they’re having you do right now since we don’t know their procedures.
Oh, I understand, Drakuloth (by the way, you were the first to help me tackle this issue all the way back in November!). I appreciate everything you all are doing to get this matter resolved. Just expressing a level of frustration with AMD. But as with anything as complex as this issue is, I suppose I can understand the more basic troubleshooting to be handled first.
Sorry if I came off hostile. It’s just frustrating with having to have contended with this issue that’s been going on since November of last year. Thank goodness I could roll back the BIOS!
Oh absolutely, Crosswinds, I know we’ve been working on this with you for months now and I absolutely understand. I just wanted to reiterate the information we received from AMD on our end and note that we can’t comment on other support teams. You’re always welcome to forward them any threads on our forums to provide more context in case it helps them look into the extent of this issue.
Either way best of luck, and let us know if you need help with anything else on our end.
At this moment, we’ve been requested to forward the 3600/3600X related issues to AMD support regarding game crashes, won’t launch, error