Memory Problems?

Inn3rs3lf

Expert Member
Joined
Mar 18, 2010
Messages
2,336
Reaction score
193
Location
Johannesburg, South Africa
Hi there all. So I have been troubleshhoting my BSOD's and I am getting nowhere. I have updated all drivers for all hardware and my pc still randomly shuts down. Sometimes with a BSOD and sometimes just a restart. Its irritating me beyond belief. Its a brand new build. Ok well, 2 months, done by myself. Im almost certain its a memory problem. Windows performance monitor shows no signs of any problems with the memory, and my memory diagnostics doesnt run. lol. I am using Win 7 32-bit. None of my pc repair options work actually. But anyway, here is the debuglog.txt. Not sure if anyone out there knows how to decipher this?

MODULE_NAME: nt

FAULTING_MODULE: 8343b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt+69c1e
834a4c1e f00fba2807 lock bts dword ptr [eax],7

TRAP_FRAME: 8f31cae4 -- (.trap 0xffffffff8f31cae4)
.trap 0xffffffff8f31cae4
ErrCode = 00000000
eax=88257a00 ebx=00000000 ecx=8f300120 edx=00000001 esi=8e6ffc34 edi=88257a00
eip=834a4c1e esp=8f31cb58 ebp=8f31cb64 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt+0x69c1e:
834a4c1e f00fba2807 lock bts dword ptr [eax],7 ds:0023:88257a00=00040001
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 834a856e to 834a4c1e

FAILED_INSTRUCTION_ADDRESS:
nt+69c1e
834a4c1e f00fba2807 lock bts dword ptr [eax],7

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8f31cb64 834a856e 8e6ffc1c 8f31cba4 8f300120 nt+0x69c1e
8f31cb80 834a4fd9 00000000 00000000 8f301a80 nt+0x6d56e
8f31cc68 834a4eae 8f300120 8f31cca8 00000000 nt+0x69fd9
8f31ccdc 834a320e 0003b380 87ae5030 8f305800 nt+0x69eae
8f31cd20 834a3038 00000000 0000000e ffffffff nt+0x6820e
8f31cd24 00000000 0000000e ffffffff ffffffff nt+0x68038


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+69c1e
834a4c1e f00fba2807 lock bts dword ptr [eax],7

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+69c1e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


ANything else you need? Im sure the normal restart is from overheating memory? Its std though, not overclocked.
 
I'd suggest that you run memtest x86.
If it passed, make sure that your BIOS is up to date. I've had issues where my Asus P7H55D-M Evo would just randomly switch off completely when the PC was idling and a BIOS update fixed that problem.
 
I'd suggest that you run memtest x86.
If it passed, make sure that your BIOS is up to date. I've had issues where my Asus P7H55D-M Evo would just randomly switch off completely when the PC was idling and a BIOS update fixed that problem.

Busy running it now. Been going for an hour and no errors so far. Updated all drivers...chipset drivers and have the latest bios. Motherboard is an intel DH55TC. Any known problems with them? I haven't seen anything online to be honest.
 
I have found that in general, especially after you have elimated the most obvious: it's either your power supply or your mother board.
 
I just find it weird that its different BSOD error codes and sometimes it just reboots. Went through four passes with memtest and no errors. Event viewer gives no signs of faults except the kernel shutdown error. This be getting tricky.
 
Try Prime95 (http://www.mersenne.org/freesoft/), blend testing with single sticks of RAM at a time, and then in pairs, etc.

I had a problem with an original Intel P55 chipset board whereby Memtest86+ would pass fine, but the machine would randomly reboot. Eventually narrowed it down to the board not liking the brand of RAM I was using (even though Memtest passed fine, Prime95 failed when I had the sticks in a certain config).

Swapped to a different brand of memory (Kingston) and the problem went away.
 
Thanks mal1ce. Will give it a try tonight. Did you get any BSODs? Or was it just randomly rebooting?

I find the pc reboots when idle and when I try and execute a program or open a folder etc.
 
Lol. Basically you set it to use max memory, and then do between 5 - 15 passes. 5 is for a quick check, 15 is more thorough. If it passes then your CPU + memory is fine, if it fails then one of the two is not fine. All those numbers is spews out is basically the result of the calculations it does. If they are all the same then you pass, if any one is different to another, you fail.
 
No. For memory tests memtest is far superior. For memory and CPU you could use prime95, though intelburntest is better and faster

I no longer trust memtest, it's useless. I had a similar problem a few years ago and memtest and some other utilities said the ram was a-OK. Micro-Scope Diagnostic Suite however said otherwise.

I you want to properly test your ram (& other components) I suggest you run Micro-Scope Diagnostic Suite (software only version). Use your imagination on how to obtain it ;) Test one stick at a time so you don't get confused about which one is the faulty one.
 
I no longer trust memtest, it's useless. I had a similar problem a few years ago and memtest and some other utilities said the ram was a-OK. Micro-Scope Diagnostic Suite however said otherwise.

I you want to properly test your ram (& other components) I suggest you run Micro-Scope Diagnostic Suite (software only version). Use your imagination on how to obtain it ;) Test one stick at a time so you don't get confused about which one is the faulty one.

Its far from useless, thats a "bit" of an exaggeration you have there. A PC of mine was randomly kicking me out of games, with the occasional reboot. Prime95 (blend test) would run for an hour no problem so I was confused. But as soon as I got into memtest it gave me errors in the first pass. And you can (legally :p) get it for free. Only after that did I find intelburntest which is now my goto guy for stability checks, since its much faster.
 
+1 to what ponder said

spent about a full week totally wasting my time due to memtest not being able to pick up a faulty kingston stick

nuff said
 
spent about a full week totally wasting my time due to memtest not being able to pick up a faulty kingston stick

nuff said

Lol, after weeks of battling and not finding the problem as everything tested ok I purchased a new PC. About two months later I came across MicroScope and ran it, a few hours later the culprit memory stick (Transcend) was found. That PC is still running today.

Nothing like wasting your time with kuk utils/tools.
 
Top
Sign up to the MyBroadband newsletter
X