Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

New system - Various BSODs


  • Please log in to reply
14 replies to this topic

#1 lucasbceo

lucasbceo

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:02:55 AM

Posted 13 April 2014 - 12:38 PM

Hello,

 

I've been receiving lots of BSODs on a brand new system, they are:

 

 - MEMORY_MANAGEMENT (log from WhoCrashed)

 - IRQL_NOT_LESS_OR_EQUAL

 - WHEA_UNCORRECTABLE_ERROR (Showed up once, log from WhoCrashed)

 

This is going for a week now, since I bought this PC.

 

As I was researching to solve these problems I ended up hearing about Windows Debugging Tool and this forum, so here am I.

 

I have a report for the IRQL_NOT_LESS_OR_EQUAL from Windows Debugging Tool, here it is:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`030a6e90
Debug session time: Sun Apr 13 13:38:04.165 2014 (UTC - 3:00)
System Uptime: 0 days 14:54:51.241
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffda018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff6800000bc30, 0, 0, fffff80002f1616a}

Probably caused by : Unknown_Image ( nt!MiSwapWslEntries+6a )

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

16.1: kd:x86> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff6800000bc30, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002f1616a, address which referenced memory

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


READ_ADDRESS:  fffff6800000bc30 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiSwapWslEntries+6a
fffff800`02f1616a 49              dec     ecx

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!MiSwapWslEntries+6a
fffff800`02f1616a 49              dec     ecx

SYMBOL_NAME:  nt!MiSwapWslEntries+6a

FOLLOWUP_NAME:  MachineOwner

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_NAME:  Unknown_Image

BUCKET_ID:  INVALID_KERNEL_CONTEXT

MODULE_NAME: Unknown_Module

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

16.1: kd:x86> lmvm Unknown_Module
start             end                 module name

My PC:

 

CPU: AMD FX-8120
GPU: HD 7850 Core Edition 2GB
Memory: (4x) OCZ Gold Edition 2GB DDR3 1033 (Total of 8GB)
HD: Seagate 1TB 64mb
Mobo: Asus M5A78L LE

PSU: Cooler Master Extreme Power Plus 600W

 

Windows 7 64 bits

 

Drivers:

 

7JLPdPp.png


Edited by hamluis, 16 April 2014 - 12:11 PM.
Moved from Win 7 to Internal Hardware - Hamluis.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,287 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:55 PM

Posted 13 April 2014 - 02:15 PM

Please download MiniToolBox  , save it to your desktop and run it.

Checkmark the following checkboxes:

  List last 10 Event Viewer log

  List Installed Programs

  List Users, Partitions and Memory size.

Click Go and paste the content into your next post.

 

Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link of the snapshot in your next post.

\

Louis



#3 lucasbceo

lucasbceo
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:02:55 AM

Posted 13 April 2014 - 02:58 PM

As requested

MiniToolBox

MiniToolBox by Farbar  Version: 23-01-2014
Ran by Lucas (administrator) on 13-04-2014 at 16:53:53
Running from "C:\Users\Lucas\Downloads"
Microsoft Windows 7 Ultimate  Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************

========================= Event log errors: ===============================

Application errors:
==================
Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:49:11 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:28:49 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.

Error: (04/13/2014 04:28:49 PM) (Source: Microsoft-Windows-CAPI2) (User: )
Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
.


System errors:
=============
Error: (04/13/2014 01:39:07 PM) (Source: Service Control Manager) (User: )
Description: The AODDriver4.2.0 service failed to start due to the following error: 
%%3

Error: (04/13/2014 01:39:05 PM) (Source: BugCheck) (User: )
Description: 0x0000000a (0xfffff6800000bc30, 0x0000000000000000, 0x0000000000000000, 0xfffff80002f1616a)C:\Windows\MEMORY.DMP

Error: (04/13/2014 01:39:05 PM) (Source: BugCheck) (User: )
Description: 

Error: (04/13/2014 01:39:02 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 13:37:25 on ?13/?04/?2014 was unexpected.

Error: (04/13/2014 01:06:25 PM) (Source: Service Control Manager) (User: )
Description: The PnkBstrA service terminated unexpectedly.  It has done this 1 time(s).

Error: (04/12/2014 10:43:36 PM) (Source: NetBT) (User: )
Description: The name "LUCAS-PC       :0" could not be registered on the interface with IP address 192.168.0.105.
The computer with the IP address 192.168.0.107 did not allow the name to be claimed by
this computer.

Error: (04/12/2014 10:43:36 PM) (Source: Service Control Manager) (User: )
Description: The AODDriver4.2.0 service failed to start due to the following error: 
%%3

Error: (04/12/2014 10:43:37 PM) (Source: BugCheck) (User: )
Description: 0x0000001a (0x0000000000041287, 0x00000000017b8000, 0x0000000000000000, 0x0000000000000000)C:\Windows\MEMORY.DMP

Error: (04/12/2014 10:43:35 PM) (Source: BugCheck) (User: )
Description: 

Error: (04/12/2014 10:43:35 PM) (Source: EventLog) (User: )
Description: The previous system shutdown at 22:41:59 on ?12/?04/?2014 was unexpected.


Microsoft Office Sessions:
=========================
Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:49:12 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:49:11 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:28:49 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Error: (04/13/2014 04:28:49 PM) (Source: Microsoft-Windows-CAPI2)(User: )
Description: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cabA required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.


=========================== Installed Programs ============================

µTorrent (Version: 3.4.1.30768)
7-Zip 9.20 (x64 edition) (Version: 9.20.00.0)
Adobe Acrobat X Pro - English, Français, Deutsch (Version: 10.1.1)
Adobe AIR (Version: 3.1.0.4880)
Adobe Creative Suite 6 Master Collection (Version: 6)
AIDA64 Extreme v4.30 (Version: 4.30)
AMD Catalyst Install Manager (Version: 8.0.916.0)
AMD Wireless Display v3.0 (Version: 1.0.0.14)
bl (Version: 1.0.0)
BS.Player FREE (Version: 2.66.1075)
Catalyst Control Center InstallProxy (Version: 2014.0312.1131.18796)
CL-Eye Driver (Version: 5.3.0.0341)
CPUID CPU-Z 1.69
DAEMON Tools Lite (Version: 4.49.1.0356)
Dark Souls Prepare to Die Edition (Version: 1.0.0000.130)
Debugging Tools for Windows (x64) (Version: 6.12.2.633)
eReg (Version: 1.20.138.34)
Far Cry 2
FileZilla Client 3.8.0 (Version: 3.8.0)
Fraps (remove only)
Google Chrome (Version: 34.0.1847.116)
Google Update Helper (Version: 1.3.23.9)
Grand Theft Auto IV
Half-Life 2
Java 7 Update 51 (Version: 7.0.510)
Java Auto Updater (Version: 2.1.9.8)
Killing Floor
Logitech Gaming Software (Version: 8.45.88)
Logitech Gaming Software 8.53 (Version: 8.53.150)
Logitech SetPoint 6.61 (Version: 6.61.15)
Mass Effect 2
Microsoft .NET Framework 4.5 (Version: 4.5.50709)
Microsoft Games for Windows - LIVE Redistributable (Version: 3.5.95.0)
Microsoft Games for Windows Marketplace (Version: 3.5.50.0)
Microsoft Visual C++ 2005 Redistributable (Version: 8.0.61001)
Microsoft Visual C++ 2005 Redistributable (x64) (Version: 8.0.61000)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022 (Version: 9.0.21022)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17 (Version: 9.0.30729)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148 (Version: 9.0.30729.4148)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022 (Version: 9.0.21022)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 (Version: 9.0.30729)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148 (Version: 9.0.30729.4148)
Microsoft Visual C++ 2010  x64 Redistributable - 10.0.30319 (Version: 10.0.30319)
Microsoft Visual C++ 2010  x86 Redistributable - 10.0.30319 (Version: 10.0.30319)
Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.61030 (Version: 11.0.61030.0)
Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.50727 (Version: 11.0.50727.1)
Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030 (Version: 11.0.61030)
Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030 (Version: 11.0.61030)
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.50727 (Version: 11.0.50727)
Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.50727 (Version: 11.0.50727)
Microsoft Windows SDK for Windows 7 (7.1) (Version: 7.1.30514)
Microsoft Windows SDK for Windows 7 (7.1) (Version: 7.1.7600.0.30514)
Microsoft_VC80_CRT_x86 (Version: 8.0.50727.4053)
Microsoft_VC90_CRT_x86 (Version: 1.00.0000)
NetLimiter 3 (Version: 3.0.0.11)
Notepad++ (Version: 6.5.5)
NVIDIA PhysX (Version: 9.09.0814)
Outlast (Version: 1)
Path of Exile
PDF Settings CS6 (Version: 11.0)
ph (Version: 1.0.0)
PunkBuster Services (Version: 0.986)
Raptr
Realtek Ethernet Controller Driver (Version: 7.65.1025.2012)
Realtek High Definition Audio Driver (Version: 3.44)
Sniper Elite V2
Steam
TechPowerUp GPU-Z
The Stanley Parable
TSEV Skyrim LE (Version: 2.0.0.0)
WhoCrashed 5.01
Windows Live ID Sign-in Assistant (Version: 6.500.3165.0)
WinMerge 2.14.0 (Version: 2.14.0)
WinRAR 4.00 (64-bit) (Version: 4.00.0)

========================= Memory info: ===================================

Percentage of memory in use: 43%
Total physical RAM: 8174.12 MB
Available physical RAM: 4645.38 MB
Total Pagefile: 16346.43 MB
Available Pagefile: 12427.69 MB
Total Virtual: 4095.88 MB
Available Virtual: 3965.82 MB

========================= Partitions: =====================================

1 Drive c: () (Fixed) (Total:931.41 GB) (Free:606.22 GB) NTFS
2 Drive f: (Sniper Elite V2) (CDROM) (Total:5.13 GB) (Free:0 GB) CDFS

========================= Users: ========================================

User accounts for \\LUCAS-PC

Administrator            Guest                    Lucas                    


**** End of log ****

Speccy
 

YYBsBEK.png

 

Maybe my motherboard is a bit hot? Here's my refrigeration scheme

7tTCV7w.gif

PS: The CPU cooler came that way stock


Edited by lucasbceo, 13 April 2014 - 03:02 PM.


#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,287 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:55 PM

Posted 13 April 2014 - 04:48 PM

Please...read the instructions for posting a snapshot using Speccy...and post the link/URL for the snapshot.  You are not asked to paste in any graphics on the Speccy instructions.  Thanks :).

 

Louis


Edited by hamluis, 13 April 2014 - 04:49 PM.


#5 lucasbceo

lucasbceo
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:02:55 AM

Posted 13 April 2014 - 05:58 PM

I'm sorry, here it is

 

http://speccy.piriform.com/results/KWpGx7rbn27rRahMAXkYItY

 

== EDIT ==

 

Just got another BSOD - MEMORY_MANAGEMENT

 

== EDIT 2 ==

 

Two hours later, IRQL_NOT_LESS_OR_EQUAL

 

== Edit 3 ==

 

And yet another MEMORY_MANAGEMENT, and life goes on.

 

I have tried to use the Driver Verifier, but after I set it up and reboot the PC, Windows loses video when booting and won't return (right after it passes the black screen that says "Starting Windows"), I had to enter Safe Mode and return to a previous restoration point I've made before enabling Driver Verifier.


Edited by lucasbceo, 13 April 2014 - 11:25 PM.


#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,287 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:55 PM

Posted 14 April 2014 - 09:12 AM

You say this is a "new" system...did you put it together?

 

Do you have a valid license for the Windows version installed?

 

Method used to install Windows?

 

No AV, no firewall...both disabled.

 

Louis



#7 lucasbceo

lucasbceo
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:02:55 AM

Posted 16 April 2014 - 09:53 AM

I've bought this system from a guy who has a hardware store, he said the pieces are brand new, assembled from different lots of hardwares that eventually got spared

 

I have a valid license for WIndows, installed it using the DVD. I have removed the DVD driver in the process of debugging the BSOD

 

I've heard cases of windows updates causing BSOD, so I disabled it. I don't like Windows Firewall, never used it.

 

But thanks for asking, I understand why you did it.

 

By the way, I'm almost sure that my memories are somewhat incompatible with AMD processor

 

My memory is running at 1067Mhz, it's original frequency is 1600Mhz. My motherboard only allows this frequency by O.C. When I O.C'd the memory to 1600mhz it BSOD every 5 minutes

 

Memory P/N: OCZ3G1600LV4GK



#8 hamluis

hamluis

    Moderator


  • Moderator
  • 56,287 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:55 PM

Posted 16 April 2014 - 12:09 PM

Looking at the board and the specs...there is no problem.  You have the same CPU/board that I do...I have DDR3 10700 RAM, while you have 12800.  Both are compatible with the board.

 

No such thing as RAM incompatibility with CPU...it's the motherboard that determines compatibility for each.

 

You should stop fooling with changing the clocking of the RAM/board...the system should run fine if you do.  Go back to the board defaults and your errors should go away, unless you have a bad module.  The RAM should automatically default to the lower clock speed allowed by the motherboard...I'm no technician or expert of any sort, but that's always been my understanding of how it works.  No need to adjust clock speed on the board.

 

It's normal for overclocking to cause system problems and instability, IMO.  Don't do it :).

 

The default clock speed for that board is 1333...with that RAM, that's where I would adjust (if I adjusted).

 

Moving topic to Internal Hardware where the more knowledgeable can give you solid information.

 

Louis



#9 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:55 PM

Posted 16 April 2014 - 07:36 PM

Well your issues are definitely memory specific. According to speccy you have a 2x4 configuration. The trouble is that they may have been installed mismatched. They are all the same brand type but not all memory sticks are the same. We need to determine if they was bought all 4 together or if in 2 seperate pairs. You need to open the case and pull all the memory out. Look at the serial numbers of each memory module. Typically a set of 4 would have some serial number but last digits would be something like 001 002 003 004 etc. If they are seperate pairs then the numbers would be 001 002 next pair could be something different like 033 034. It doesn't matter if you have all 4 matching or two pair as long as they both are in dual channel. You just need to pair them into the slots. So for two dual memory kits you would put in the black slots 001 & 002. In the Blue/white colored slots 033 & 034. Same goes for the 4 kit. Black 001 & 002. Blue/White 003 & 004. Go into bios and set the memory timings to 1333 and 8-8-8-24. 1.5volts.



#10 lucasbceo

lucasbceo
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:02:55 AM

Posted 18 April 2014 - 11:30 PM

@technonymous

 

That's exactly it!!!

 

The dual channel memories were pairing with the wrong serials! Inverted it and didn't get BSOD ever since!!

Even got the Memory to work at 1600Mhz (it's original frequency) instead of 1066Mhz. When I did that before I was getting BSOD every 5 min.



#11 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:55 PM

Posted 19 April 2014 - 08:20 PM

Glad to here it. :)



#12 lucasbceo

lucasbceo
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:02:55 AM

Posted 19 April 2014 - 08:42 PM

@technonymous What do you think about this? http://www.tomshardware.com/answers/id-2110482/crash-bsod.html#xtor=EPR-8809

#13 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:55 PM

Posted 19 April 2014 - 09:29 PM

It's probably the same type of scenario. Memory mismatch, memory timings, memory set on 1600 instead of 1333. Some AMD cpu's will not run 1600 you have to go by what the cpu spec sheets say about the memory supported. In some cases the motherboard doesn't support the ram. With building a system you want to read up on the QVL (Qualified Vender List) This will list all of the memory modules that have been tested by the manufacturer of the motherboard. Sometimes a 2x4 configuration is just not listed at all as it throws in extra issue's as well. Generally lower ram modules of 512, 1024, 2048 will run much faster timings and this can also throw the system off.

 

Generally populating all the slots in the system causes the system to have to relax the timings on that fast timings memory. It all depends on the archtitecture of the motherboard as well and how well it's power plant (if you will) can deliver voltages to all the memory modules and get a faster timings. Some lower grade cheaper motherboards will have issues on that alone. With faster ram and over clocking is concerned, generally you want to only populate only one dual channel. You will gain the performance of the dual channel, but also retain the headroom required for the overclock. It also depends on the cpu and if it's multiplier is unlocked. It's best to overclock by raising the multipler than to overclock the bus. Overclocking the bus will force the ram to run higher thus creating instability, also it overclocks the bus of the video card as well thus creating bsod's in the video card while gaming. Generally you want ram that can handle higher clocks as well as the cpu. Some more expensive motherboards are designed to handle that big overclocking. Motherboards with quad channel setup with dual memory slots of both sides of the cpu and of course the power plant to make everything stable.

 

Along with this a good PSU needs to be used that can deliver the voltages needed and can recover quickly with on demand power fluctuations. If a PSU has problems with delivering watts under heavy load bsod happens. Voltage drops across the system bsod happens. I have seen brand new cosairs right out of the box was a lemon. It doesn't matter brand names it's just that day it got passed. This is a issue in itself when costs go down so does quality as corners are cut and many units will get a pass when they shouldn't have. It's a science it really is to get all this to work properly. System builders have to take everything into consideration. The general rule of thumb is never cheap out lol especially on the motheboard, PSU. Those are what makes up the foundation of the entire system. If your foundation is bad then the whole thing collapses.

 

~Technonymous


Edited by technonymous, 19 April 2014 - 09:32 PM.


#14 lucasbceo

lucasbceo
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:02:55 AM

Posted 19 April 2014 - 10:03 PM

@Technonymous

 

Makes perfect sense. My motherboard and PSU are the weakest things in my build.

 

I'm doing these changes:

 

Cooler Master Extreme Power Plus 600w => Corsair 750W Modular
Asus M5A78L LE => Asus Crosshair V Formula

 

This PSU is known to be weak. It's rated 600W but reviews showed it can hold something like 450W, it's one of the worst PSU ever.

 

This motherboard is weak too. I have a HD 7850 Core Edition 2GB, a FX-8120 (wich I intend to overclock) and 4x 2GB DDR3 1600Mhz


Edited by lucasbceo, 19 April 2014 - 10:06 PM.


#15 technonymous

technonymous

  • Members
  • 2,516 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:55 PM

Posted 20 April 2014 - 12:54 AM

What the PSU says and what it can do are two different things. That is why generally everyone flocks to a PSU brand name known to work well. However, every brand will have it's batch of bad units. A good review place to check out is..http://www.jonnyguru.com/index.php They really break it down and bench test it under load. They go into technical details why it fails etc and they give opinions overall on it and thumbs up approvals.

 

I can't stress how important it is to read these types of websites because you never know what you're buying. I lost count how many times I bought myself or for other clients and as soon as you get it, you find out it's a lemon or generally doesn't do what it says it does. It's also hard to trust onboard things such as sound, nic, video. I came across this one build I did and the onboard nic was garbage had a ( ! ) in the device manager that couldn't be resolved no matter what. A after market had to be bought in it's place. This happened a few times with sound boards as well. One just screamed a god awful hiss static at full volume. I tested it on the motherboard headers as well. Apparenlty it was a short on the board itself I had to disable it in the system bios and again had to replace it with a after market sound card. Even a cheap sound blaster card is 10 times better than the onboard sound you get. You gotta remember they are just banging these things out the door and sometimes the robots building these boards get out of spec and need a retool/adjustment. With the ongoing competition many get out the door with flaws. It's definitely worth it to put extra money into a board proven to work from fellow users on forums.


Edited by technonymous, 20 April 2014 - 12:55 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users