Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
How did you test your RAM?
What are your specs?
Ultimately millions of people run Steam and ESO without BSOD's, so my instinct is that this is a system issue of some kind and you're on the hook to troubleshoot it. I'm not convinced you've completely ruled out RAM issues yet.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x50--page-fault-in-nonpaged-area on the surface that error seems to deal with invalid memory addresses, bad memory addreses would be invalid too. So if it were me I'd be interested in confirming the RAM is good.
So I guess the question is how long have you been using this RAM? Have you tried testing it with memtest86? And it passes all tests?
I'm not sure what any of this means but here's the dump file.
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffff9a00006f56d8, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000006, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Type
Value: Read
Key : Analysis.CPU.mSec
Value: 6015
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 28488
Key : Analysis.Init.CPU.mSec
Value: 1405
Key : Analysis.Init.Elapsed.mSec
Value: 25852
Key : Analysis.Memory.CommitPeak.Mb
Value: 102
Key : Bugcheck.Code.DumpHeader
Value: 0x50
Key : Bugcheck.Code.Register
Value: 0x50
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 080222-5625-01.dmp
BUGCHECK_CODE: 50
BUGCHECK_P1: ffff9a00006f56d8
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 6
READ_ADDRESS: fffff807144fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffff9a00006f56d8
MM_INTERNAL_CODE: 6
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffc18d085c6550 -- (.trap 0xffffc18d085c6550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9a4d26934000 rbx=0000000000000000 rcx=ffff9a00006f56d8
rdx=ffff9a4d26934000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80713a32800 rsp=ffffc18d085c66e8 rbp=ffff9a4d26934000
r8=ffff9a4d26800018 r9=0000000000000002 r10=0000000000000002
r11=ffff9a00006f56d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MI_READ_PTE_LOCK_FREE:
fffff807`13a32800 488b01 mov rax,qword ptr [rcx] ds:ffff9a00`006f56d8=????????????????
Resetting default scope
STACK_TEXT:
ffffc18d`085c61c8 fffff807`13c1f91b : 00000000`00000050 ffff9a00`006f56d8 00000000`00000000 ffff9a4d`26800018 : nt!KeBugCheckEx
ffffc18d`085c61d0 fffff807`13a6d9a7 : 00000000`00000000 00000000`00000000 ffffc18d`085c6550 00000000`00000000 : nt!MiInPagePageTable+0x20438b
ffffc18d`085c6320 fffff807`13a6ce4a : ffffdc84`73000000 00000000`00000000 ffffc18d`085c65d0 00000000`00000000 : nt!MiUserFault+0x5e7
ffffc18d`085c63b0 fffff807`13c06a5e : ffffdc84`6fe021c0 00000000`0000004c ffffdc84`73001040 fffff807`13a451eb : nt!MmAccessFault+0x16a
ffffc18d`085c6550 fffff807`13a32800 : fffff807`13b21831 00000000`00000200 00000000`00000000 00000000`004b77e8 : nt!KiPageFault+0x35e
ffffc18d`085c66e8 fffff807`13b21831 : 00000000`00000200 00000000`00000000 00000000`004b77e8 fffff807`141b21c4 : nt!MI_READ_PTE_LOCK_FREE
ffffc18d`085c66f0 fffff807`1872381d : ffff9a81`00000000 ffff9a81`cebd5180 00000000`00000000 ffff9a00`00bace90 : nt!MmBuildMdlForNonPagedPool+0x1f1
ffffc18d`085c67b0 fffff807`331a3bef : 00000000`000000bc ffff9a81`cebe0240 ffffdc84`7848e040 00000000`00000000 : ndis!NdisAllocateMdl+0x3d
ffffc18d`085c67f0 00000000`000000bc : ffff9a81`cebe0240 ffffdc84`7848e040 00000000`00000000 00000000`0000013c : bcmwl63a+0x93bef
ffffc18d`085c67f8 ffff9a81`cebe0240 : ffffdc84`7848e040 00000000`00000000 00000000`0000013c fffff807`3318600c : 0xbc
ffffc18d`085c6800 ffffdc84`7848e040 : 00000000`00000000 00000000`0000013c fffff807`3318600c ffffdc84`757738e0 : 0xffff9a81`cebe0240
ffffc18d`085c6808 00000000`00000000 : 00000000`0000013c fffff807`3318600c ffffdc84`757738e0 ffffdc84`759d1780 : 0xffffdc84`7848e040
SYMBOL_NAME: bcmwl63a+93bef
MODULE_NAME: bcmwl63a
IMAGE_NAME: bcmwl63a.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 93bef
FAILURE_BUCKET_ID: AV_R_(null)_bcmwl63a!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d2a604c6-01f6-6ce2-ad0c-3565bf3123ab}
Followup: MachineOwner
---------
Okay so I've checked those links out. Had the same exact Module name in the dump as the post (funny enough the person who posted a fix was replying to me on microsoft.com). I've been going at this now for over 8 hours. And what I've found out so far is that my network adapter card that is messed up. However, I have no money to get it looked/at fixed and i think I very well may have to go that route.
I've tried updating and rolling it back to a previous install and nothing has worked. I did recently get a few updates on my computer today and yesterday, and I've uninstalled those and blocked them cus stupid windows 10 keeps trying to auto install, was thinking that those updates may have been the cause.
After doing all of that, I'm now running the ESO installer again, to see if it's fixed.
you can ask ESO nicely , but i doubt it they have to look into it and included such pc.
https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170
ps.
did you even know what you have bought at all. same as wrong system in my book.
cant say they they dont want to make emulations or whatever later , but call it a MS support system is not the case and maybe never will be.
ARM-based CPU , you need games requirement supported in cpu, afaik not seen or notice such yet, but i have not looked for it.
could he have memory issue that scamble content, never seen a log mention a arm64 issue if its not a problem.
and ask ESO game support
No its something wrong with my network adapter. I think I need a new one. I'm saying this because I just reset my computer. wiped out all files, settings and apps and reinstalled windows 10 and I'm still having the same issue.
Only thing is now I'm getting dns server errors when searching for websites on the web. And yes I'm still getting BSOD when downloading ESO even after updating all my drivers after the new install.
Either that or its time for a new computer. The one I have now is 8 years old.
PAGE_FAULT_IN_NONPAGED_AREA (50)
and then it go dark from there as it cant solve the issue with multi issue and get a fit with multi choise and it need to explan whats its doing
Arg1: ffff9a00006f56d8, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000006, (reserved)
is that Laptop in Full performance, and it like the laptop missing update or that Brand laptop own support place dont give them update to you, most laptop has automatic Brand Driver update app, but i and other have seen such need own checking because they dont work with win10 migration and 8 year old pc was before win10, so uoi might have Drivers that newer and never got them.
sense you just wipe and got frsh system files i see no point in dism and sfc checkup
ask own Brand laptop support , but i bet if its asus they say aient it time for buying new laptop. its like they dont care with whats wrong, aks any here it seem you have game requirement.
except the good old argument run things in balance mode on laptop can cause some games issue with highend cpuc cycle throttle, its a weel know argument, and yet its not , you bought a laptop that can do that a deskyop pc dont, end of debat in cpu cycle throttle, and desktop pc dont have that max power scematic reduced mode.
and its here a laptop is not same as a desktop pc. ( pc thats build for max power saveing cant be compare with standard pc. ) most game requirement dont even mention laptop as reference at all.
CPU: Intel(R) Core i7-4700HQ CPU @ 2.40GHz <------
2.4 as basecore is over 20 years ago, most games today is 3ghz+ to 4ghz+ the highend
so technicaly if you run in max power saveing thats is minimum performance then you have a pc that is so reduce that might explan this app cant ID it and then it cant help you if such was done, i did not make the code or can see from here if that the case,
or as you said it broken hardware, that require you have some IT expert on the case from remote access if you are not skilled enough,
point is you can find 100 of post like this, other use the word like interference app that cause issue even that ( crapware or other things ) all this is of cause debatable but in the end should not made eso crash.
its like the old threas app cant figureout whats wrong and run back to mother and cry and give a worst case senario, i have never seen a log give bit issue with such im sure other might have seen such before. ( and lets hope its lack of update rather then broken hardware assume the best for you, noone here can fix that, or waste time on such in all-in-one product as a laptop is just like that. )
get a tech dude to that if you are not that yourself, get a trusted friend to look at it.
but lets not kidding outself here if you have the money buy a better pc
GTX 850m
and 8 gb ram
is seen as you point out, have seen better days, and GPU card is not seen in most laptop as upgrade possible.
dont throw it out, its 1 game that do this according to you, not sure that cover it a a broken pc
most healper here will agree on that, more like something cause this, and might be fixable then its ID better.
but as i said and cause of why this happend.
Yeah after I reset my PC, there was some updates that it automatically installed. Shortly after that I did a DNS flush (due to a separate issue I was having after reset). I then uninstalled and reinstalled steam, and was able to download ESO without any problems.
The only small issue I had was when I reset the PC during reinstallation of windows, my computer blue screened again. It only did it one time.
It restarted itself and I was able to make selections for the windows 10 setup.
https://store.steampowered.com/app/1754000/The_Elder_Scrolls_Online_High_Isle/
but even that dont add up , you have it, as i see this maybe they want to help you more because BSOD is not that simple unless they can proff you dont have newest Driver installed or maintain pc the right way.
okay atleast that explan alot , what ever happend in old OS is gone, as i understand it game run now, and yet you still have system issue, you might want to recheck own brand support and Microsoft own VC+++ support page files, im sure you might think game devs and steam know whhats best + MS, but, pc and its way and alot of ppl can tell thats not the case anymore, its user that need to do the update and check up.
and im sorry we other take it for granted today, again why we dont think it can be that now and not related to BSOD.
or maybe you got both because you block it maybe a long time ago i seen such in av app and why.
things has been change sense ransomware and games once worked require folder access now.
and why steam made "new root/steamlib" as default. on multi drives steam libs
gl with it.