NO BSOD restarts - Windows 8.1

Mavromatis

Member
Joined
Feb 18, 2013
Posts
18
W8.1 restarts itself randomly without any bsod or anything related on event log. No overheating, no load, no overclock.
Checking the Event Log I've only found :
"The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S5). This can result in reduced resume performance."
"The AODDriver4.3 service failed to start due to the following error:" MSI Afterburner's problem
and 7 "Kernel-Power" Critical event stating that "The system has rebooted without cleanly shutting down first. "
I built this machine ~2 weeks ago. It's running W8.1 on UEFI over an SSD disk, 8GB ram in a single module, AMD FX-8320, Sapphire Radeon R9 270X, GIGABYTE 970A-D3.

I suspect something about the sleep state but I disabled timed sleep, and hibernation.
 

Attachments

Now I got a BSOD, though I didn't see it since the PC was on but I wasn't there.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x000000000000000d, 0xfffff90145392ca0, 0x79799445af7dc52f, 0x7979d445af7dc52f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101914-11328-01.
Added it as attachment.
 

Attachments

Hi,

BAD_POOL_HEADER (19)

This indicates that a pool header is corrupt.

Code:
BugCheck 19, {d, fffff90145392ca0, 79799445af7dc52f, 7979d445af7dc52f}

Code:
4: kd> !pool fffff90145392ca0
GetPointerFromAddress: unable to read from fffff803d0bde138
Pool page fffff90145392ca0 region is unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
Unknown
 fffff90145392000 size:  1d0 previous size:    0  (Allocated)  Ttfd
 fffff901453921d0 size:   a0 previous size:  1d0  (Free)       Usqm
 fffff90145392270 size:   f0 previous size:   a0  (Allocated)  Gla8
 fffff90145392360 size:   30 previous size:   f0  (Free)       Free
 fffff90145392390 size:   f0 previous size:   30  (Allocated)  Gla4
 fffff90145392480 size:  370 previous size:   f0  (Free)       Gfnt
 fffff901453927f0 size:  4b0 previous size:  370  (Allocated)  Usti Process: 7979cd454ff1408f
[COLOR=#ff0000]*fffff90145392ca0 size:  360 previous size:  4b0  (Free ) *Gdrs[/COLOR]
        [B]Pooltag Gdrs : Gdi GDITAG_DRVSUP[/B]

1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys and rename AODDriver2.sys to AODDriver.2old and then Restart.

2. Uninstall Glary Utilities.

3. Run Memtest for no less than 8 passes:

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works (you don't need to read, it's only for those interested in the specifics):

Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.

The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.

The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.

Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
If it shuts off without warning and it's not over heating it's usually power related.
Just to error on the side of caution disconnect the case power and reset(if equipped) start the system using the tip of a screwdriver momentarily across the two power switch pins. if the system runs without issue the case wiring or switch(es) are the problem.
If you still have an issue swap in a known good power supply.

What are the brands and models of the components used in the build?
 
BugCheck 19, {d, fffff90145392ca0, 79799445af7dc52f, 7979d445af7dc52f}

The parameters are "reserved" (undocumented), but I suppose the bugcheck is due to a single bit error between 3 and 4. Single bit flip is a reason to suspect a hardware failure.

79799445af7dc52f=111100101111001100101000100010110101111011111011100010100101111
7979d445af7dc52f=111100101111001110101000100010110101111011111011100010100101111
 
BugCheck 19, {d, fffff90145392ca0, 79799445af7dc52f, 7979d445af7dc52f}

The parameters are "reserved" (undocumented), but I suppose the bugcheck is due to a single bit error between 3 and 4. Single bit flip is a reason to suspect a hardware failure.

79799445af7dc52f=111100101111001100101000100010110101111011111011100010100101111
7979d445af7dc52f=111100101111001110101000100010110101111011111011100010100101111

Indeed, which is why I am surprised Memtest passed.
 
Which model 600w PSU, some of them are real clunkers.
Thermaltake's power that came with the case.
BugCheck 19, {d, fffff90145392ca0, 79799445af7dc52f, 7979d445af7dc52f}
The parameters are "reserved" (undocumented), but I suppose the bugcheck is due to a single bit error between 3 and 4. Single bit flip is a reason to suspect a hardware failure.

79799445af7dc52f=111100101111001100101000100010110101111011111011100010100101111
7979d445af7dc52f=111100101111001110101000100010110101111011111011100010100101111


Indeed, which is why I am surprised Memtest passed.

I'll run memtest for today too.
 
If you already ran it yesterday and it came up with no errors, it won't be different. Have you tried removing the RAM and re-seating it? Possibly a chip creep issue.

Regards,

Patrick
 
Memtest gave me a problem, one bit changed.
0022b9d85b4 - 8889.5MB
Good Bad
c9497e55 c9487e55

Err-Bits
00010000
So, what's the procedure here, do I have faulty ram or it might be some power issue? Keep in mind that the problem mostly arises when I leave the house.
 
I will probably take the ram the store tomorrow but I noticed something odd about the resets; they mostly occurs when I turn off the monitor, lock windows and leave for work. Nearly all of them happens during that time period so I wonder if this can be some sleep and/or power related issue.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top