New RAM, still getting BSODs

Eevie

Posts: 10   +0
Hi guys,

Hope someone can help me here. I bought my pc a year ago and I never had any problems with it untill January. I was getting random bsod's with the 1a error code. I tested my RAM (2 x 2GB) with memtest and found out it was defect. So I got new RAM and it was fine for a while, but then the bsod's came back again. I took out one of the RAM modules and the bsod's stopped untill last week. I tested the module that is in my pc now and I found no errors. Formatting doesn't help either.
There is something wrong in the hardware I guess but I don't know where to look.
I added the minidump file of a bsod I got this morning.
 

Attachments

  • 040411-78437-01.zip
    18.7 KB · Views: 2
040411-78437-01.dmp
4-4-2011 10:49:48
PAGE_FAULT_IN_NONPAGED_AREA
0x00000050
fffff800`00a717d3
00000000`00000008
fffff800`00a717d3
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+66580
NT Kernel & System
 
Got another one:

BCCode: a
BCP1: 00000000000064E9
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002AB571A
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Again caused by ntoskrnl.exe
 
BCCode: d1
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880017C31B0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

caused by atikmdag.sys, ntoskrnl.exe and rdyboost.sys.

What is the ntoskrnl.exe about? Seems to cause most bsod.
 
IRQL_NOT_LESS_OR_EQUAL

BCCode: a
BCP1: 0000000000000080
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002B0FE12
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
 
Find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?
 
Yes, both 1.5 V.

Here are the last two minidumps I got.
 

Attachments

  • Minidump.zip
    36.3 KB · Views: 1
If formating doesn't help thyen it is most likely hardware. The thing is the dumps point out that there is a significant problem but nothing definitive was cited.

Have you ever run a harddrive diagnostics before?
 
I checked my harddisk for errors but couldn't find any. I got a weird bsod today, it says DRIVER_PORTION_MUST_BE_NON_PAGED with code D3 and was caused by amdsbs.sys.
 
Thanks!
The first link says: To begin debugging, use a kernel debugger to get a stack trace. I have no idea what a kernel debugger is.

In the second one the person deleted the driver but I don't think I can do that with amdsbs.sys.

Do you mean the error reports in windows after a crash? I do get those.
 
So sorry Eevie for my delayed response. We want those error reports (if you haven't already received help).

How to find and post your Minidump Files:

My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

It is these files that we need (not the folder). Attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip; if you only have one or two you don’t need to zip them, just attach as is. Please do us a favor and don’t Zip each one individually.
 
Thanks for your help but I have send the computer back to the shop, they think it's my motherboard. Will get a replacement this week!
 
Thanks for your help but I have send the computer back to the shop, they think it's my motherboard. Will get a replacement this week!

Please let us know what they find and what the the final resolve is. Thanks.
 
Back