Hi Ken,
Glad to help, looking forward to the results.
BSOD - Newly Built Computer - EventID 41 BugcheckCode 265
Just built this computer two weeks ago with all brand new components. I installed an OEM copy of Win10 clean. Updated it and updated the graphics card. I did not update BIOS or motherboard chipset. Everything was fine but a few days ago I started getting the same BSOD when playing World of Warcraft. It has happened multiple times now and always with the same error data in the event viewer (details below).
I ran my memory diagnostics with no errors. I am at a loss as to what to try next. Ideas?
System is as follows:
OS Name Microsoft Windows 10 Home
Version 10.0.17763 Build 17763
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-M7S0N8U
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor AMD Ryzen 7 3700X 8-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 0406, 6/15/2019
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product TUF GAMING X570-PLUS (WI-FI)
BaseBoard Version Rev X.0x
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume3
Locale United States
Hardware Abstraction Layer Version = "10.0.17763.652"
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 26.5 GB
Total Virtual Memory 36.7 GB
Available Virtual Memory 29.3 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
Event ID - details
| - | System |
|---|
| - | Provider | <br> | --- | --- | <br><br><br><br> | [ Name] | Microsoft-Windows-Kernel-Power | <br> | --- | --- | --- | --- | --- | <br><br><br><br><br> | [ Guid] | {331c3b3a-2005-44c2-ac5e-77220c37d6b4} | <br> | --- | --- | --- | --- | --- |
|---|
| EventID | 41 | <br> | --- | --- | --- |
|---|
| Version | 6 | <br> | --- | --- | --- |
|---|
| Level | 1 | <br> | --- | --- | --- |
|---|
| Task | 63 | <br> | --- | --- | --- |
|---|
| Opcode | 0 | <br> | --- | --- | --- |
|---|
| Keywords | 0x8000400000000002 | <br> | --- | --- | --- |
|---|
| - | TimeCreated | <br> | --- | --- | <br><br><br><br> | [ SystemTime] | 2019-09-06T01:37:41.168394300Z | <br> | --- | --- | --- | --- | --- |
|---|
| EventRecordID | 9925 | <br> | --- | --- | --- |
|---|
| Correlation | <br> | --- | --- |
|---|
| - | Execution | <br> | --- | --- | <br><br><br><br> | [ ProcessID] | 4 | <br> | --- | --- | --- | --- | --- | <br><br><br><br><br> | [ ThreadID] | 8 | <br> | --- | --- | --- | --- | --- |
|---|
| Channel | System | <br> | --- | --- | --- |
|---|
| Computer | DESKTOP-M7S0N8U | <br> | --- | --- | --- |
|---|
| - | Security | <br> | --- | --- | <br><br><br><br> | [ UserID] | S-1-5-18 | <br> | --- | --- | --- | --- | --- |
|---|
| - | EventData |
|---|
| BugcheckCode | 265 |
|---|
| BugcheckParameter1 | 0xa39ff0e3c878d516 |
|---|
| BugcheckParameter2 | 0xb3b6fd6a1af712c1 |
|---|
| BugcheckParameter3 | 0xfffff803022fff88 |
|---|
| BugcheckParameter4 | 0x1 |
|---|
| SleepInProgress | 0 |
|---|
| PowerButtonTimestamp | 0 |
|---|
| BootAppStatus | 0 |
|---|
| Checkpoint | 41 |
|---|
| ConnectedStandbyInProgress | false |
|---|
| SystemSleepTransitionsToOn | 2 |
|---|
| CsEntryScenarioInstanceId | 0 |
|---|
| BugcheckInfoFromEFI | false |
|---|
| CheckpointStatus | 0 |
|---|
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
9 additional answers
Sort by: Most helpful
-
Anonymous
2019-09-06T02:32:23+00:00 Yes, so far its only happened while playing WOW and I also have web browser open on second screen. I will try the BIOS update and let you now. My memory diagnostic came back with no errors. Is there any way to tell if one of my DIMMS are bad?
-
Sumit D - IA 171.1K Reputation points Independent Advisor
2019-09-06T02:28:59+00:00 Hi,
Memory corruption was the cause of this error. Does this only happen while playing WOW?
Update BIOS to 1005, yours is a bit old.
https://www.asus.com/Motherboards/TUF-GAMING-X5...
Disclaimer:
This is a non-Microsoft website which would provide accurate and safe information. Watch out for ads on the site which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.
-
Anonymous
2019-09-06T02:22:28+00:00 Hi ksk,
I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.
We need log files(called dump files) that tell us what lead to crash.
Please share them with us for a better analysis of the problem. Instructions can be found here:
https://answers.microsoft.com/en-us/windows/for...
Please let us know if you need any assistance about posting dump files.
Thank you.
Dump File OneDrive link:
-
Sumit D - IA 171.1K Reputation points Independent Advisor
2019-09-06T02:06:18+00:00 Hi ksk,
I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.
We need log files(called dump files) that tell us what lead to crash.
Please share them with us for a better analysis of the problem. Instructions can be found here:
https://answers.microsoft.com/en-us/windows/for...
Please let us know if you need any assistance about posting dump files.