• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

serious problem with BSODs

B

browncoat

n00b
Joined
Dec 3, 2008
Messages
7
OK so lately I've been getting quite a few blue screens. They were: IRQ_LESS_THAN_OR_EQUAL, Memory Management and Corrupt PFN List. All resources I looked at pointed to problems with the memory. SO I ran 8 passes of memtest with each of my sticks and all passed with 0 errors. I thought it might be a driver issue so I reformatted and installed XP Pro (was using Vista x64 before).

Then today I got ANOTHER blue screen.

The only thing I can think of is problems with the Nvidia 182.08 driver. It was shortly after I installed the latest driver that I started getting BSODs in Vista and these were the same drivers iI installed in XP.

Any ideas?? Help please...:confused:
 
I'm running 2x2GB of Crucial Ballistix Tracer DDR2 800

stock speed and voltage since I'm running the FSB at 400 and Multi at 9 for my 3.6GHz overclock.

As an update, I have had no BSOD since downgrading my nvidia drivers to version 178.24 from the most recent 182.08

Thanks for the assistance by the way
 
Hello I'm having the same problems as you. I was getting the IRQ not less then or equal and now I'm getting the PFN list corrupt. These issues are coming out of the blue. I also have the 2x 2gig DDR2 800 Crucial Tracer RAM. My system was rock solid for months now and now I'm all the sudden getting blue screens.

Running memtest did not produce any errors. Should I order some different RAM? Crucial is absolute shit.

I'm running nvidia 182.20 (lastest drivers) on a MSI k9a2 Platinum with a corsair 1 kw psu. Xp 64 bit btw too.
 
Last edited:
Like I said the computer has been running great for a while. I did not change thing when this happened. After reformatting and reinstalling windows the error changed from the irq not less then or equal to the corrupt pfn list. Also when I was trying to reinstall windows the installation was telling me it couldn't read some of the files on the disk and to retry. Specifically when it's loading the device drivers and you're still at the all blue screen.

Dump file:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000008d,
Arg2: 000000000015f4d5
Arg3: 0000000020000000
Arg4: fffff68000003089

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


BUGCHECK_STR: 0x4E_8d

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800010a3546 to fffff8000102e890

STACK_TEXT:
fffffadf`9000fc78 fffff800`010a3546 : 00000000`0000004e 00000000`0000008d 00000000`0015f4d5 00000000`20000000 : nt!CmpDelayCloseWorker+0xa7
fffffadf`9000fc80 00000000`0000004e : 00000000`0000008d 00000000`0015f4d5 00000000`20000000 fffff680`00003089 : nt!MmUnlockPagableImageSection+0x2c6
fffffadf`9000fc88 00000000`0000008d : 00000000`0015f4d5 00000000`20000000 fffff680`00003089 00000000`00000000 : 0x4e
fffffadf`9000fc90 00000000`0015f4d5 : 00000000`20000000 fffff680`00003089 00000000`00000000 00000000`00000000 : 0x8d
fffffadf`9000fc98 00000000`20000000 : fffff680`00003089 00000000`00000000 00000000`00000000 00000000`00000000 : 0x15f4d5
fffffadf`9000fca0 fffff680`00003089 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x20000000
fffffadf`9000fca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000007`00000005 : 0xfffff680`00003089


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpDelayCloseWorker+a7
fffff800`0102e890 48894c2408 mov qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpDelayCloseWorker+a7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 49c237fa

FAILURE_BUCKET_ID: X64_0x4E_8d_nt!CmpDelayCloseWorker+a7

BUCKET_ID: X64_0x4E_8d_nt!CmpDelayCloseWorker+a7

Followup: MachineOwner
---------
 
When I had this problem (I'll try to find the thread) it was my memory voltage needed to be increased.

memtest86 and memtest86+ would test overnight clean, but games would BSOD. I screwed around with all kinds of driver changes, pulling hardware etc.. and they all changed the issue but nothing solved it until I bumped my memory voltage another 0.1V

I don't want to assume to know everything about your DIMMs, mobo, timings and clock rates, but if you have headroom without damaging anything give it a try. I have OCZ Platinum rev.2 4x1GB DDR2-800.

I found my thread here.
 
Surly73 said:
When I had this problem (I'll try to find the thread) it was my memory voltage needed to be increased.

memtest86 and memtest86+ would test overnight clean, but games would BSOD. I screwed around with all kinds of driver changes, pulling hardware etc.. and they all changed the issue but nothing solved it until I bumped my memory voltage another 0.1V

I don't want to assume to know everything about your DIMMs, mobo, timings and clock rates, but if you have headroom without damaging anything give it a try. I have OCZ Platinum rev.2 4x1GB DDR2-800.

I found my thread here.
Click to expand...



MOFO!!! It crashed as I was typing it a response about how wonderful it was and it didn't crash while i was sleeping. IRQ_Not_Less_Than_or_Equal. Fuck it i'm swapping the ram out. I've always been wary of the crucial RAM. Upping the voltage by .1V did not work. Upon reboot after the above BSOD it quickly reboots with another BSOD. I can't even boot into safe mood. I have to completely power the system down in order to get windows back. Remember this system was running 24/7 with zero problems for a months. Again no errors in Memtest but this has to be a RAM problem.
 
Last edited:
Surly73 said:
When I had this problem (I'll try to find the thread) it was my memory voltage needed to be increased.

memtest86 and memtest86+ would test overnight clean, but games would BSOD. I screwed around with all kinds of driver changes, pulling hardware etc.. and they all changed the issue but nothing solved it until I bumped my memory voltage another 0.1V

I don't want to assume to know everything about your DIMMs, mobo, timings and clock rates, but if you have headroom without damaging anything give it a try. I have OCZ Platinum rev.2 4x1GB DDR2-800.

I found my thread here.
Click to expand...


I have some nice OCZ Reaper heading my way now. The same ram i've been using in my main rig for 7 months without a problem.
 
Last edited:
You must log in or register to reply here.
Back
Top