Hey Been have a stack load of BSOD recently in windows 10 did a Memory test and it has come back failed. Ram is T-Force DDR4 36000 16gb (2X8GB) Truth be told never had RAM issues before so no idea how i should really proceed re this issue or if there is anything i can do re the problem ? Any advice greatly appreciated. The below is the Dump from the Memory Diagnostics results... Is this a bad stick of ram? Log Name: System Source: Microsoft-Windows-MemoryDiagnostics-Results Date: 03/01/2019 23:21:13 Event ID: 1102 Task Category: None Level: Error Keywords: User: SYSTEM Computer: INTRON-ROG Description: The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5f92bc59-248f-4111-86a9-e393e12c6139}" /> <EventID>1102</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2019-01-03T23:21:13.233730500Z" /> <EventRecordID>7302</EventRecordID> <Correlation /> <Execution ProcessID="1420" ThreadID="8052" /> <Channel>System</Channel> <Computer>INTRON-ROG</Computer> <Security UserID="S-1-5-18" /> </System> <UserData> <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events"> <LaunchType>Manual</LaunchType> <CompletionType>Fail</CompletionType> <MemorySize>16308</MemorySize> <TestType>10</TestType> <TestDuration>1661</TestDuration> <TestCount>12</TestCount> <NumPagesTested>4120056</NumPagesTested> <NumPagesUnTested>1766</NumPagesUnTested> <NumBadPages>30</NumBadPages> <T1NumBadPages>0</T1NumBadPages> <T2NumBadPages>0</T2NumBadPages> <T3NumBadPages>2</T3NumBadPages> <T4NumBadPages>15</T4NumBadPages> <T5NumBadPages>0</T5NumBadPages> <T6NumBadPages>0</T6NumBadPages> <T7NumBadPages>0</T7NumBadPages> <T8NumBadPages>0</T8NumBadPages> <T9NumBadPages>7</T9NumBadPages> <T10NumBadPages>6</T10NumBadPages> <T11NumBadPages>0</T11NumBadPages> <T12NumBadPages>0</T12NumBadPages> <T13NumBadPages>0</T13NumBadPages> <T14NumBadPages>0</T14NumBadPages> <T15NumBadPages>0</T15NumBadPages> <T16NumBadPages>0</T16NumBadPages> </Results> </UserData> </Event>
Possibly, thought Windows' built-in tool isn't the most reliable of beasts... Get a second opinion with Memtest if you can
Yeah slept on it and was trying to remember a program i used ages ago ... i think it was that going to try that again tonight then. if it fails ill do process of elimination and swap the sticks out to find out which is the offending stick So kinda jumped the gun with the above post..... I appreciate you pointing me in the right direction.
Update on this one .... Memtest still showed an error took the ram out re seated it and tested again ... no error ... all fine... not sure what it could have been but the PC was Transported and i never actually checked and made sure everything was seated ok before start up... Maybe it just wasn't 100% snugly seated i dont know but all seems to be ok... I will keep playing and see how it goes.. once again appreciate your assistance and sorry for jumping the gun with the thread
Ram has a tendency to come out of full systems when transported. It's far worse when they come all the way out. This is an issue many system integrators deal with.
