Windows 10: From BSOD to Windows Crash

I would really love to find out whats going on with my rig.
It's a home built gaming rig from Microcenter.
i5-4690
ASRock Z97 Pro4 Motherboard
16GM RAM
240GB SSD HD.
Now at first I had WoW installed and had no issues then went to install ArcheAge and I had BSOD's issues where the game would just close (not the client just the game) I was working with support for about a month adjusting my paging file making the initial size 1.5 times the size of my RAM and the max size 2X the size of my RAM, making all kinds of adjustments. I reformatted and reinstalled Windows10 and just installed WoW and Archeage and still had issues with Archeage (but not WoW) so finally I gave up on that game. I took my computer back to Microcenter and had them check out my computer. They said they checked all the hardware and everything was fine and the operating system was fine too the problem had to be the game. I ran a memcheck on my RAM (8 passes ran for 19 hours and 38 min) and my RAM had zero errors) so I don't think my Ram is bad) so I reinstalled Windows 10 again after that and just installed Skyforge only. Ran Windows updates until no more updates could be downloaded, Made sure my graphics card drivers were updated, installed the GeForce Experience and optimized the game but now instead of BSOD's windows has been crashing the game. I ran the BSOD tool and am attaching the zip file I really hope you can find something because I'm at a loss, I have had the hardware checked, I've reformatted and reinstalled windows several times and the game still crashes and i don'Attachment 84695t know why.

Obi-wan, Your my only hope!

:)

 

Endless IRQL_NOT_LESS_OR_EQUAL and MEMEORY_MANAGEMENT

The 0xf7 bugcheck dump was interesting as it is quite different from the 0xa bugcheck dumps.

See if Driver Verifier flags any 3rd party drivers -
http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html

 

My PC keeps getting BSOD. Help! ntoskrnl.exe

OK.

So here is the really weird thing.

My pc crashed/bsod multiple times while trying to install/update my windows 10, from the windows 10 media creation tool you linked previously.

So I thought ok well I'll try to run verifier and recreate the crash from the windows 10 media creation tool, so I can figure out what is causing the crash....
But it's not crashing..... I don't know why but when I run verifier my pc is not going into bsod. I mean it is still putting a huge strain on my pc everything is sluggish and laggy, but it's not causing any bsod's if anything it's preventing
a bsod....

I'm not sure why this is, the only thing I could think of would be that the bsods are not caused by a driver therefore they're not reacting to the verifier but that doesn't mean it would just stop the pc from bsoding :l

First attempt at installing/updating windows 10 while using verifier ( due to reasons stated above) Didn't work out.

Screenshot - efbfcdff76747f5776616050aa7d933f - Gyazo

 

He sent his padawan first .... if I need I will call him. You know the master is busy.

Test your RAM modules for possible errors.MemTest86+ - Test RAM Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

I will ask Master Kenobi to look at your thread after seeing the resulting situation.

 

I did run the MemTest 86+ Test for Ram if you see my post. 8 passes took 19 hours and 38 minutes. It showed no errors. I didn't know to take a screenshot and didn't see an option to take a screenshot. However I will upload the files from the flashdrive here if thats where they saved them.Attachment 84732Attachment 84732

 

You need to take a camera snap of the memtest86+ screen.

By the way, your crash dumps are pointing to memory corruption, prima facie. One is directly blaming the memory .....
Code: BugCheck 109, {a3a01f597f48b898, b3b72bdfd1c65f41, fffff802882560e0, 1} Probably caused by : memory_corruption Followup: memory_corruption ---------[/quote] And the other one ....
Code: BugCheck 4E, {99, 2723ee, 2, 60002700027246d} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1f759 ) Followup: MachineOwner ---------[/quote] .... is a bugcheck caused due to memory corruption, specially.

Now, memory corruption may occur not only due to a failing RAM, but also for some other reasons. If the RAM is actually failing, then sehing for the other reasons will not be anyhow effective. And hence the confirmation is required. The proper confirmation is the camera snap; but if you want the troubleshooting may proceed on your statement, any risk associated with this confirmation will be shifted to you.

Let us know which sort of confirmation is ok for you .... documented or verbal. We will go accordingly.

 

Hi Raygon, when we are working BSODs, we have to follow what the dump files tell us. They are not always right and memtest is not always correct. However, they are the best tools we have for analyzing these things.

As Arc said, your dump files show memory corruption. We have found, from a lot of experience, that it is always wise to follow what we read from the dump files.

Trust me, I know very well what a pain it is to run memtest86+. I have had to run it myself as many as 20 times to fix one of my own computers. You can take a picture with a cell phone or a digital camera. We are not concerned with the quality of the picture, we just need to be able to read the info on the screen. This will tell you how to upload it here. https://www.tenforums.com/tutorials/1...en-forums.html

 

Ok, so yo want me to take the 19 hour memtest again which is not always correct so i can take a picture with m phone?

 

What you do is up to you. We can only make suggestions and recommendations. It is your computer and you can do whatever you want to do. Unfortunately, Windows does not come equipped with a Fix It button. The only tools we have are reading the dump files, we do not have the computer in front of us. As of right now, the dump files are telling us,

Code: BugCheck 109, {a3a01f597f48b898, b3b72bdfd1c65f41, fffff802882560e0, 1} Probably caused by : memory_corruption Followup: memory_corruption[/quote] How would you think we should react to that information, which is all we have to go on? Whether you run Memtest86+ is entirely your decision. Can I guarantee you the memory is your problem? No. Can I rule out Memory as the problem, no again. It's your call. What I can guarantee you is that if memory is the problem, we will be led on a 'wild goose chase' running down a lot of other things that are not the problem. Again, what you do is entirely up to you.

 

As a side note, curious why you are changing the date/time or timezone regularly? Could that have any impact on this?

 

Oh I know and I am not trying to be flippant or anything, I am truly just wondering; you said that this program is not always correct and lets say I run the program again and I get the exact same results (8 passes no errors with a picture that shows it) and yet the dump files say otherwise, then what?

How would you think we should react to that information, which is all we have to go on? Whether you run Memtest86+ is entirely your decision. Can I guarantee you the memory is your problem? No. Can I rule out Memory as the problem, no again. It's your call. What I can guarantee you is that if memory is the problem, we will be led on a 'wild goose chase' running down a lot of other things that are not the problem. Again, what you do is entirely up to you.[/quote]

 

Memory corruption is a thing that is the most coming back in the dumps, because the memory mechanism of Windows is extremely large and complicated. When memory corruption is shown the first step is to rule out the memory as best as possible. The next step is to rule out the drivers what can be done with driver verifier if none is flagged. If drivers are also not causing any problems then we (or at least myself) usually check for the hard drives. Hard drives can also cause memory corruption, as it is the non-volatile version of memory, but there are usually signs about hard drive problems when we suggest something for the hard drive. Another memory corruption is the VRAM, but when that happens there are also signs about it.

 

Raygon, @axe0 explained it pretty nicely and pretty completely. @Arc and axe0 are two of the best BSOD analysts I know. If I can't figure it out, they are who I go to. In my opinion, a memory error is the worst error to get if you don't catch it first. It will cause every driver in the system to show errors, when it was ram all along. I just like to rule that out first, especially when it is shown as the cause in the dump files.

This is technically Arc's thread, so I will leave it up to him. If I can help in any way, I'll be more than happy to. Both Arc and axe0 know that.

 

Memtest86+ is not always correct. Sometimes it fails to get the right thing and those are exceptions. Exception that proves the rule.

@Raygon, let us take a different approach; let us consider that it is a failing/rogue driver that is passing bad information to the memory. Based on this hypothesis we will stress test the drivers for a few times. If the stressing flags any driver, we will try to rectify it.

So please enable Driver Verifier to monitor the drivers. Driver Verifier - Enable and DisableRun Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

[youtube]BjsofLPNosc[/youtube]



Information Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.


Warning Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.


Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

Where do you see this being changed? I've missed stuff before - just ask Archie or Steve, or well, just about any member.

There have been some reports of the timezone being changed ... by Windows? an update?

On my machine
The Scheduled task ForceSynchronizeTime in Microsoft\Windows\Time Synchronization had never run and showed an error code (since fixed - sorry don't remember the code)
I tried running it manually, but it never finished.

The last cumulative update set my timezone to Pacific time (UTC-8), at least that seems to be the most likely candidate
when I changed it to Eastern (UTC-5) and rebooted, I was off +3 hours (UTC-2 ... Eastern Greenland or somewhere in the mid Atlantic)
... I set the time correctly, checked my timezone and ran Internet time using nist.gov as the time server

The scheduled task ran successfully sometime after that.