BSOD playing Aion, "REFERENCE BY POINTER" and "IRQL NOT LESS OR EQUAL"

[Mokrab]

BSOD playing Aion, "REFERENCE BY POINTER" and "IRQL NOT LESS OR EQUAL"

Hello, i've been having this problem for a week now, tried to fix it but no luck what so ever. So i got tired and i am looking for your assistance on this matter.
Every time I play Aion online, in about 10-30mins i get a blue screen saying "REFERENCE BY POINTER" or "IRQL NOT LESS OR EQUAL", tried many methods that were stated on the forums of different sites but no luck... that is why i am attaching my BSOD information and hoping for you assistance. Thank you in advance.
PS: When I play Aion, and the PC restarts (caused by BSOD) most of the time the minidump isn't created and sometimes it doesn't go into the BSOD it just restarts, but i know the problem is the BSOD.

I have Windows 7 Ultimate x86(32bit)
It's the original installed OS on my system (OEM)
I've had this computer for ~4years, drivers always up to date and i reisntalled my Windows yesterday.
Attaching the Zip file with the information required which was on BSOD posting instructions post.

 

[zigzag3143]

No DMPS included in upload try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Mokrab]

Thank you for the reply.

I am currently in Safe Mode (with networking), but when i go into the minidump folder, its empty. in my C:\Windows i can only find Memory.dmp file and the minidump folder, but when i get the BSOD the minidump isn't created.

As u said:
To ensure minidumps are enabled:
Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

I already had that option enabled, but even so the minidump wasn't created.
I'll attach the system information as u asked but how can I get the minidump? should I wait for another BSOD? and what if it doesn't create a minidump yet again?

 

[Mokrab]

I just got a blue screen again... REFERENCE BY POINTER.
STOP:0x00000018(0x0000000,0x85598900,0x00000002,0x878c001)

Went into the minidump folder and nothing was there, the minidump file wasn't creater even when the BSOD accured it said that is saved the information or something like that.

 

[Mokrab]

New error accured...

Driver IRQL not less or equal
Stop:0x000000D1(0x3F793A77,0x000000FF,0x00000008,0x3F793A77)

at the end of the BSOD it says "Physical memory dump complete", but no minidump created...
then i went and checked that the "Small Dump Directory" where there should be %systemroot%\Minidump typed in.. it was empty.., tried typing it again but... after pressing "ok", went back in and its empty again. It appears that the directory isn't saving, what should i do?

 

[zigzag3143]

I just got a blue screen again... REFERENCE BY POINTER.
STOP:0x00000018(0x0000000,0x85598900,0x00000002,0x878c001)

Went into the minidump folder and nothing was there, the minidump file wasn't creater even when the BSOD accured it said that is saved the information or something like that.

We need the DMP. If minidump is empty you can load memory.dmp on to a file sharing service. Post a link to it in your next post.

 

[Mokrab]

https://rapidshare.com/files/2165912203/MEMORY.DMP
This is my Memory.DMP

 

[zigzag3143]

https://rapidshare.com/files/2165912203/MEMORY.DMP
This is my Memory.DMP

Sorry but that one was corrupt and far too small to be a complete memory.dmp Memory DMP is about the same size as the amount of ram you have.

If you cant generate DMP files lets take a look at the event viewer log



For dumps to be produced. . .
▪ Page file must be on OS drive
▪ Page file base allocation size must be > than installed physical RAM
▪ Windows Error Reporting (WER) system service should be set to MANUAL
▪ Set page file to system managed, OS drive

Set System Crash/ Recovery Settings to "Kernel Memory Dump" - this will produce. . .
--> a Full Kernel Memory Dump - c:\windows\memory.dmp
--> a Mini Kernel dump c:\windows\minidump

The Full Kernel is overwritten each BSOD; a new mini kernel dump is created w/ different name for each BSOD


Please provide us with your Event Viewer administrative logs by following these steps:


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

 

[Mokrab]

I just got a BSOD and a minidump was created here is the link to it.
https://rapidshare.com/files/2311512717/043012-12916-01.dmp

PS: viewing with blue screen viewer It showed me that the problems were: atarop:sys, hal.dll and ntoskrnl.exe Here's also the event viewer.

 

[Mokrab]

Is the minidump corrupted? or is it fine?

 

[zigzag3143]

I just got a BSOD and a minidump was created here is the link to it.
https://rapidshare.com/files/2311512717/043012-12916-01.dmp

PS: viewing with blue screen viewer It showed me that the problems were: atarop:sys, hal.dll and ntoskrnl.exe Here's also the event viewer.

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

 

[Mokrab]

This is what i got from the malware detector that you suggested.
.

 

[zigzag3143]

This is what i got from the malware detector that you suggested.
.

Good news, no infection.

Now we wait for the next crash and please upload the DMP.

 

[Mokrab]

This is what i got from the malware detector that you suggested.
.

Good news, no infection.

Now we wait for the next crash and please upload the DMP.

The problem is that I had a few of those crashes earlyer and one of them was a new one "page fault in nonpaged are" when the blue screen finished writing the information, after the restart the minidump wasn't created, i would like to know a solution for that or the cause of it.

 

[zigzag3143]

This is what i got from the malware detector that you suggested.
.

Good news, no infection.

Now we wait for the next crash and please upload the DMP.

The problem is that I had a few of those crashes earlyer and one of them was a new one "page fault in nonpaged are" when the blue screen finished writing the information, after the restart the minidump wasn't created, i would like to know a solution for that or the cause of it.

Page fault in non paged area" has about 14 specific causes. The only way we can tell is with the dmps

 

[Mokrab]

Got another DMP

 

[JMH]

Stop 0x124 is a hardware error

If you are overclocking try resetting your processor to standard settings and see if that helps.

If you continue to get BSOD here are some more things you may want to consider.

This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try
Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions.
Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Mokrab]

How do i check if im overclocking? i don't understand the meaning of "overclocking" correctly and how should I restore the default setting? I am sorry if this sounded very "newbish"

 

[JMH]

If you don't know what overclocking is, it {usually} means you have not altered any thing - which from a BSOD perspective is a good idea.
The purpose of overclocking is to increase the operating speed of given hardware.

FYI

Overclocking - Wikipedia, the free encyclopedia

 

[Mokrab]

Did all the tests above, everything went fine without any errors...
When i checked the minidump with Blue Screen viewer hal.dll and ntoskrnl.exe was at fault. I think whats making these BSODs is my Graphic card (Nvidia Geforce GTS250), so im buying a new one which is MSI NVIDIA GeForce GT 440

PS: Is my new Graphic card better then older one? Cause i'm not really good at comparing... Thanks

BTW I'm still getting the BSOD on Aion, but when i change my Graphic card i'll inform you if i get any BSODs and if it's fixed