BSOD while playing games

Gator · Mar 28, 2015

Hi Cobalt, this BSOD seems like it could be a bit flip.

Memory_corruption One_Bit is usually bad memory

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
[COLOR=#ff0000]Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.[/COLOR]
Arg2: fffff6bffc3a7240
Arg3: [COLOR=#0000cd]000000000[/COLOR][COLOR=#ff0000]1[/COLOR][COLOR=#0000cd]000000[/COLOR]
Arg4: 0000000000000000

Debugging Details:
------------------


[COLOR=#ff0000]MEMORY_CORRUPTOR:  ONE_BIT[/COLOR]

BUGCHECK_STR:  0x1a_41792

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MOM.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

The page table is empty/null which is not normal.

Code:

kd> dt nt!_MMPFN fffff6bffc3a7240
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : (null) 
   +0x010 VolatilePteAddress : (null) 
   +0x010 Lock             : 0n0
   +0x010 PteLong          : 0
   +0x018 u3               : <unnamed-tag>
   +0x01c NodeBlinkLow     : 0
   +0x01e Unused           : 0y0000
   +0x01e VaType           : 0y0000
   +0x01f ViewCount        : 0 ''
   +0x01f NodeFlinkLow     : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x028 u4               : <unnamed-tag>

All signs still point to Memory corruption. Either your Memory or memory controller is most likely bad.

Run Memtest86+ again over night. Try to run for longer than 8 passes. Maybe 11-15 (whatever your schedule allows)

Try each ram in different slots

See the "If you have errors" section of the link below to test each memory module and dimm slot.
RAM - Test with Memtest86+ - Windows 7 Help Forums

Cobalt325 · Mar 28, 2015

First shall i run the memtest or try the ram in different slots?

Gator · Mar 28, 2015

Cobalt325 said:
First shall i run the memtest or try the ram in different slots?

Well tonight test the ram in each slots. Before bed, do memtest86+ for 11+ passes

We may continue testing each slot/module after the test as well.

Cobalt325 · Mar 29, 2015

I have 2 RAM sticks and 4 slots. The 1# stick was in the 1# slot. The 2# stick in the 3# slot. so i took the 2# ram from the 3# slot and i ran the memtest with the 1# stick in the 1# slot. 11 passes no errors. Now what shall i do? Test the 1# stick in the 3# slot?

TY!

Gator · Mar 29, 2015

Cobalt325 said:
I have 2 RAM sticks and 4 slots. The 1# stick was in the 1# slot. The 2# stick in the 3# slot. so i took the 2# ram from the 3# slot and i ran the memtest with the 1# stick in the 1# slot. 11 passes no errors. Now what shall i do? Test the 1# stick in the 3# slot?

TY!

It seems like #1 stick is "acting" good (because even without errors, Ram can still be bad) so try #1 stick in #3 slot (then 2 and 4 slots) for at least 8 passes.

If all of your slots come up clean, take stick #2 and test it in Slot 1, then slot 3. (Make sure slots 1 and 3 are the spots needed for your motherboards specifications).

If you still can't find any errors, you may need to get a pair of known good sticks of ram. If these fail or you get another BSOD, I think its safe to say your Dimm slots of memory controller is corrupted and the only way to fix that is a new motherboard.

Cobalt325 · Mar 29, 2015

"Make sure slots 1 and 3 are the spots needed for your motherboards specifications"

I dont understand this part.

Gator · Mar 29, 2015

Typically slots 1 and 3 are used, this is due to most motherboards being dual-channel. Let me take a look at your motherboard specifications for you

Gator · Mar 29, 2015

Yes, this is correct. Slots 1 and 3 are the correct slots so disregard that part of the post

Code:

If you want to install two memory modules, for optimal compa[FONT=sans-serif]tibility [/FONT]
[FONT=sans-serif]and reliability, it is recommended to install them in the sl[/FONT]
[FONT=sans-serif]ots: DDR3_[/FONT]
A1 and DDR3_B1, or DDR3_A2 and DDR3_B2

Cobalt325 · Mar 29, 2015

View attachment 59823

Asrock FM2A75 Pro 4

Cobalt325 · Mar 29, 2015

So i need to test only the 1# and 3# slots?

Gator · Mar 29, 2015

You currently have them in A2/B2 (Slot 2 and 4)

On the left side of that picture, near your ram, you can see A1,A2,B1,B2. That represents the slots on your motherboard. Have they always been in A2,B2?

Cobalt325 · Mar 29, 2015

Yes its always been there.

Gator · Mar 29, 2015

Cobalt325 said:
Yes its always been there.

Put them in slots A1 and B1 and see if that helps your problems.

Cobalt325 · Mar 29, 2015

Shall i stop the ram test?

Gator · Mar 29, 2015

Cobalt325 said:
Shall i stop the ram test?

Yes go ahead and stop the test, put them in Slots A1 and B1 and then just play a few games, wait for a BSOD.

If you have another BSOD, test your ram in the correct slot like normal.

Cobalt325 · Mar 31, 2015

ive got a BSOD again. ive just checked a few stuff in the internet i didnt play or anything else. i didnt even play today, and i had BSOD again. Do you have any idea why do i have a BSOD? or what shall i do? Thx.

Gator · Apr 3, 2015

So once again it looks like Ram/Memory Corruption.

Page Table is null

Code:

   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : (null) 
   +0x010 VolatilePteAddress : (null) 
   +0x010 Lock             : 0n0
   +0x010 PteLong          : 0
   +0x018 u3               : <unnamed-tag>
   +0x01c NodeBlinkLow     : 0
   +0x01e Unused           : 0y0000
   +0x01e VaType           : 0y0000
   +0x01f ViewCount        : 0 ''
   +0x01f NodeFlinkLow     : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x028 u4               : <unnamed-tag>

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=#ff0000]BugCheck 1A[/COLOR], {[COLOR=#ff0000]41792[/COLOR], fffff6bffc3a7240, 1000000, 0}

Probably caused by : memory_corruption ( ONE_BIT )

Followup: MachineOwner
---------

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
1: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=#ff0000]MEMORY_MANAGEMENT (1a)[/COLOR]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, [COLOR=#ff0000]A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.[/COLOR]
Arg2: fffff6bffc3a7240
Arg3: 0000000001000000
Arg4: 0000000000000000

Debugging Details:
------------------


[COLOR=#ff0000]MEMORY_CORRUPTOR:  ONE_BIT[/COLOR]

BUGCHECK_STR:  0x1a_41792

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MOM.exe

CURRENT_IRQL:  0

Again, ONE_BIT corruption generally comes down to faulty ram.

We can try to run Driver Verifier. This program is not full proof but sometimes if you have 3rd party drivers or other drivers that could be causing a problem.
Using Driver Verifier to identify issues with Drivers - Windows 7 Help Forums

Run Memtest86+ on 1 stick of ram in Slot 1. Find a stick of ram that passes 8+ passes. Test this stick of ram in each slot.

If its at all possible to get known good ram (even ram that shows know errors could be going bad) and ensure that Ram isn't the cause.

Post back the results.

Cobalt325 · Apr 11, 2015

Hi!

I tested #1 ram in each slot. No errors. But i played a game (fifa 15 only with #1 ram) only one match and i got a bsod(my computer restart). What now? Maybe my motherboard incorrect?
Here is the result:

Gator · Apr 14, 2015

This could be boiling down to a bad motherboard. Your latest BSOD is a Bugcheck 124. This is typically a hardware failure of some sorts.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=#ff0000]BugCheck 124[/COLOR], {0, [COLOR=#ff0000]ffffe0012197e8f8[/COLOR], 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!thread'
2: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!thread
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=#ff0000]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2:[COLOR=#ff0000] ffffe0012197e8f8[/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

WHEA_UNCORRECTABLE_ERROR is not a particularly helpful BSOD but sometimes it can mean you have a CPU problem which you can see below there are CPU related errors.

Code:

2: kd> !errrec ffffe0012197e8f8
===============================================================================
Common Platform Error Record @ ffffe0012197e8f8
-------------------------------------------------------------------------------
Record Id     : 01d074c3708b8ebb
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/12/2015 1:53:18 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe0012197e978
Section       @ ffffe0012197ea50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=#ff0000]Error Type    : BUS error[/COLOR]
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000610f01
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffe0012197e9c0
Section       @ ffffe0012197eb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 01 0f 61 00 00 08 04 00 - 0b 32 98 3e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffe0012197eb10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe0012197ea08
Section       @ ffffe0012197eb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=#ff0000]BUSLG_OBS_ERR_*_NOTIMEOUT_ERR[/COLOR] (Proc 0 Bank 4)
  Status      : 0xba000010000b0c0f

However, the "OBS" in BUSLG_OBS_ERR_*_NOTIMEOUT_ERR seems to be saying that the CPU was observing (OBS) and was not actually involved in this error. So instead of actually being the CPU as the problem its more likely to be a motherboard issue, probably related to the BUS as you can see above.

Cobalt325 · Apr 14, 2015

Alright. Then what would be the next? Do I need to run some of another test? Or how can I make sure which one is wrong?

BSOD while playing games

Power User

My Computer

New Member

My Computer

Power User

My Computer

New Member

My Computer

Power User

My Computer

New Member

My Computer

Power User

My Computer

Power User

My Computer

New Member

My Computer

New Member

My Computer

Power User

My Computer

New Member

My Computer

Power User

My Computer

New Member

My Computer

Power User

My Computer

New Member

My Computer

Power User

My Computer

New Member

My Computer

Power User

My Computer

New Member

My Computer