New
#11
Ah, silly me. Thank you.
So I just re-run the dm log collector and repost the zip?
That is what I have done here.
I hope the next crash is the other BSOD I've been getting
Ah, silly me. Thank you.
So I just re-run the dm log collector and repost the zip?
That is what I have done here.
I hope the next crash is the other BSOD I've been getting
I can't load the dump, not sure why.
Please check your system files, it might be an indication for the why.
Diagnostics Test
System File Check
Please try following:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
I ran sfc/scannow twice, one pre-restart and one post-restart.
Both said "Windows Resource Protection did not find any integrity violations."
I'll try googling the ntoskrnl.exe module and the fixes associated with that. I found something about overclocking cpus, but I'm fairly certain I have done no overclocking.
What else do we try?
Googling won't help, gives memory issues as result.
Ntoskrnl is Windows related, if it truly was the cause you would have much more problems.
So, now what?
Rerun memtest?
Keep googling?
Wait for the other BSOD crash dump?
All of the above, I suppose.
Hey,
So I just got another 0x03B BSOD, but I didn't get another .dmp file. Do you have any insight as to why?
I haven't changed anything else since our previous discussions.
Hard to say, try following and SFC
Diagnostics Test
Malware scan
Please run a threat scan with Malwarebytes*, a full scan with your AV, scan your system with Adwcleaner, Kaspersky TTDSKiller, ESET Online Scanner and SuperAntiSpyware
Note*(Uncheck trial version in the installation process)
Yesterday evening I swapped out my new (2x4gb) RAM with my old (2x2gb) RAM, and have played for a cumulative of ~10 hours, and have not had a single freeze or BSOD. This seems indicative that my computer does not agree with the new RAM sticks, even though memtest said they were OK. BIOS is up to date, and all the voltage controls are set to automatic. Do I have to tell the bios to recalculate the auto voltage required to run the new RAM? I honestly have no idea anymore.
What are/were the voltages and frequency values of the new ram?
It is either that these values are wrong, or MemTest86+ is just wrong what happens rarely.