Memory again!!?!?!?!?

Youngie1337

New member
I got my RAM back and still just got 4 BSOD for IRQL_NOT_LESS_NOR_EQUAL and some other one. I had this with my old RAM which was faulty, I think it may be the memory banks. I have done memtest and no errors. Really weird actually.

Any ideas?

EDIT:

Q6600

NOCTUA

XMS2 4-4-4-12

PSU OCZ 750w

ASUS P5Q PRO

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47e26c50

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

9c86695c

FAULTING_IP:

nt+cf1df

805a61df 89b83c020000 mov dword ptr [eax+23Ch],edi

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 805a64b0 to 805a61df

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

aa564d30 805a64b0 0000007c 010bffd0 010bfeec nt+0xcf1df

aa564d4c 8054161c 0000007c 010bffd0 010bfeec nt+0xcf4b0

aa564d64 7c90e4f4 badb0d00 010bfed0 00000000 nt+0x6a61c

aa564d68 badb0d00 010bfed0 00000000 00000000 0x7c90e4f4

aa564d6c 010bfed0 00000000 00000000 00000000 0xbadb0d00

aa564d70 00000000 00000000 00000000 00000000 0x10bfed0

STACK_COMMAND: kb

FOLLOWUP_IP:

nt+cf1df

805a61df 89b83c020000 mov dword ptr [eax+23Ch],edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+cf1df

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
 
name='soapsupah' said:
maybe the problem is with your mobo? have any other to try the ram sticks?

Nope I don't, which is the main problem lol. The mobo is only a few months old same as the other hardware. Apparently it has something to do with drivers accessing invalid or parts of the memory without permission.

Impossible to pinpoint tbh.
 
name='VonBlade' said:
When are you getting the BSOD?

Are you sure you've got the right amount of volts?

Yep, this is with stock, I tried to make sure and yep all good. Now OC no crash just yet, will only do it randomly.
 
Get some cooling on the ram?? Check its not your cpu, run Prime95 etc..

I had a similar problem, and it was when my ram got to hot :(
 
name='Luigi' said:
Get some cooling on the ram?? Check its not your cpu, run Prime95 etc..

I had a similar problem, and it was when my ram got to hot :(

I have no cooling on the RAM, I have 1 fan which is pulling air out at the back. CPU is fine, temps are around 26c right now. I haven't got any other fans to put in. I will get some when I can.

I'm gonna try some debug tools. This might be something to do with my dual boot lol, I did it using notepad.

name='nepas' said:
Nvidia problems??

Using ATI.
 
IRQ issues can be casued by two PCI devices trying to use the same referance.

Have you dissabled all the on board devices? Serial/com ports, FDD contolers, un-used sound devices, ethernet controlers etc.
 
name='Ham' said:
IRQ issues can be casued by two PCI devices trying to use the same referance.

Have you dissabled all the on board devices? Serial/com ports, FDD contolers, un-used sound devices, ethernet controlers etc.

Ahh, never thought of that, I have just PCI 4870 nothing else, I use all onboard.

Will give it a shot now, cheers for the tip.

EDIT:

Just done that, booted up much faster for some reason.
 
name='Youngie1337' said:
EDIT:

Just done that, booted up much faster for some reason.

It does cause BIOS does less checks :)

Could it be that the overclock you've done has made it like that? Or was there an error in your ram from before you overclocked? Try running at default settings and see if the same error occurs.
 
name='moogle' said:
It does cause BIOS does less checks :)

Could it be that the overclock you've done has made it like that? Or was there an error in your ram from before you overclocked? Try running at default settings and see if the same error occurs.

Before overclock Moogle, haven't had one since I posted. I have updated all drivers etc.
 
name='Youngie1337' said:
Before overclock Moogle, haven't had one since I posted. I have updated all drivers etc.

Ahh okay, was just thinking if you were running the ram above the rated speed that's why :)
 
name='moogle' said:
Ahh okay, was just thinking if you were running the ram above the rated speed that's why :)

Ha, nah I had the exact same problem, I had some faulty RAM sent it back and got all new! Then I get the same BSOD lol, seems to be working fine now *fingers crossed*.

Reading from the error dumps and stuff, seems like the sound drivers, updated them last night.
 
Back
Top