Memory Management BSOD - No memtest errors - Please help :(

Toggle sidebar Toggle sidebar
B

Bennis

Distinguished
Sep 19, 2011
21
0
18,510
Hey guys,

I have been having infrequent BSOD maybe once a week, but sometimes upto three times a day. It is always memory management!

I have ran memtest for some 30 hours last week and had zero errors whatsoever. Just had another BSOD today so am asking for some assistance.

I have ensured all sticks are seated properly.

My specs worth mentioning, if you have any other hardware requests I can find them out:

Windows 7 64-bit
Intel i5 4670K
Corsair Vengeance Pro CMY32GX3M4A1600C9 32GB DDR3
Asrock Z87 Extreme 4 E80-38009400748
Nvidia GTX760
OS is installed on a 120gb SSD

Nothing is overclocked or changed in the BIOS, i slapped it togethor years ago and have this BSOD on and off ever since. But I have finally had enough of it!


One thing I have noticed, is that tabs in google chrome will crash almost always preceeding the BSOD. So when I see the tabs crash, and crash upon refreshing, I know the BSOD is usually coming.

I don't know a great deal about diagnostics myself, but if told what to do I am pretty capable of following instructions!

Attached is the dump file from the latest BSOD, if that is any help. I could not figure out for the life of me how to upload a file here, so I have uploaded it to a free host website. Heres the link

http://

P.s. pressing "check for solution" on the recovery screen does absolutely nothing whatsoever...

Any help would be great,

Cheers,
Ben
 
Solution
Ironsounds
Hello... Typically running 4 sticks of RAM will require slight MB voltage increases to them, and is set in the BIO's (saved&exit). Look and see what the Voltage is currently set for them there.
Since you DON't mind following some Directions... The Event Viewer and screen IMG's posted from there, is what I Like and work best with for BSOD errors... so an IMG posting site will work best.

APPs Calls can cause them... and OS Calls can cause them... and hardware can cause them... We need to fix/look at them in that order first.

1) Do you have any RED or Yellow marks in your Control panel-Device manager?
2) kernel 41 errors mean the OS was not properly shut down... either by You OR the hardware.

Here is the Windows Event Viewer debug...
Sort by date Sort by votes
D

Daniel Woodward

Reputable
Jul 31, 2014
87
0
4,660
Couple of ideas for you to try.

1. Double check RAM frequencies in BIOS, sometimes motherboards will get their guesses as to what RAM timings and frequencies it should be running at default. Ensure this is within the specification for your ram.

2. Try using only two of the four sticks and see if that helps the issue. It could be possible that your processor has a weak memory controller and doesn't like being in command of 32 Gigs worth of RAM. If this fixes your issue I wouldn't be surprised as you said it has been doing this the entire time you have had the machine. Whilst this isn't a fix it does point you in the direction of the fault.

Other than that, the only other thing I would say is that if you have access to anymore RAM (wouldn't recommend buying more, just if you have it lying around) ensure that it is DDR3 and 1333-1600Mhz and try that in the system. Otherwise Im not sure.

Hope this helps. :)
 
Upvote 0 Downvote
Ironsounds

Ironsounds

Champion
Jul 31, 2011
10,403
4
56,960
Hello... Typically running 4 sticks of RAM will require slight MB voltage increases to them, and is set in the BIO's (saved&exit). Look and see what the Voltage is currently set for them there.
Since you DON't mind following some Directions... The Event Viewer and screen IMG's posted from there, is what I Like and work best with for BSOD errors... so an IMG posting site will work best.

APPs Calls can cause them... and OS Calls can cause them... and hardware can cause them... We need to fix/look at them in that order first.

1) Do you have any RED or Yellow marks in your Control panel-Device manager?
2) kernel 41 errors mean the OS was not properly shut down... either by You OR the hardware.

Here is the Windows Event Viewer debug screen.

You NEED to be logged on as administrator to the OS...

let's see what the OS is reporting as the error... Right click computer-manage-System Tools-Event Viewer-Windows logs-system.... Click on the "RED" "Critical" errors, for more information... and files/drivers/Apps, comments/suggestions/information, General/Details associated with them B )

Expanding Window panes and Posting screen images from here will help me, help you faster... But copy and posting text will work too B )
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom