From BSOD to Windows Crash

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 Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   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.

Ztruker said:

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

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.

Slartybart said:

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.

Same here. I had to change the time source to a different server. It worked fine after that.

Thanks Steve, thought I was losing it for a couple of weeks ... just couldn't nail down the cause.

I hope that I don't sidewind this thread ... I'm not always up-to-date on Intel things

Came across this: Intel Extreme Memory Profile (Intel XMP) and Overclock RAM
and wondered if Raygon was overclocking.

The other thing I tried to determine was if the RAM was matched (and if the MoBo certified that RAM), but I couldn't find which file had specific ram module information.

ASRock > Z97 Pro4 specs

Memory

- Dual Channel DDR3/DDR3L Memory Technology - 4 x DDR3/DDR3L DIMM Slots - Supports DDR3/DDR3L 3100+(OC)/2933(OC)/2800(OC)/2400(OC)/2133(OC)/1866(OC)/1600/1333/1066 non-ECC, un-buffered memory - Max. capacity of system memory: 32GB* - Supports Intel® Extreme Memory Profile (XMP) 1.3 / 1.2

Sorry to interrupt - you folks are the knowledgeable ones.

Bill
.

I couldn't find which file had specific ram module information

That would be the dumps:

Code:

[Memory Device (Type 17) - Length 40 - Handle 0014h]
  Physical Memory Array Handle  000eh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                ChannelA-DIMM1
  Bank Locator                  BANK 1
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  1315
  Serial Number                         
  Asset Tag Number                        
  Part Number                   BLS8G3D1609DS1S00.
[Memory Device (Type 17) - Length 40 - Handle 0017h]
  Physical Memory Array Handle  000eh
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          8192MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                ChannelB-DIMM1
  Bank Locator                  BANK 3
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1600MHz
  Manufacturer                  1315
  Serial Number                         
  Asset Tag Number                        
  Part Number                   BLS8G3D1609DS1S00.

See if this looks right http://www.crucial.com/usa/en/bls8g3d1609ds1s00

Thanks, the RAM is a pair and in the correct slots for dual priority 1
and the RAM is certified for the AsRock Mobo

Type	Speed	Size	Vendor	Module	SS/DS	Sgl Chan	Dual Chan	OC
DDR3	1866	8GB	Crucial	BLE8G3D1869DE1TX0.16FED	DS	v	v	v
DDR3	1600	8GB	Crucial	BLS8G3D1609DS1S00.16FED	DS	v	v

but the OC column is not checked

Raygon said:

Microcenter built my pc. I gave them the specs and they put it together. I did not overclock it.

Thanks, I thought you built it and was going to praise your skill.

I'm not adding anything here, you have the best StopCode hunters helping you.