Bsod irql_not_less_or_equal

If you understand these dumps see the attached 7z of the dmp file.

Top line

IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffa9d`d00a37e0 00000000`00000002 00000000`00000001 fffff800`02cbef00 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\081911-16988-01.dmp 4 15 7601 262,144

Windows 64

Any clues on what is causing this?
 

Attachments

  • 081911-16988-01.7z
    15.3 KB · Views: 2
What is your computer's complete specifications ?

This dump cited memory corruption as reason for the crash. Please download memtest, and run 10-12 passes on each RAM module separately.
 
System Specs

intel i3 2100
Gigabyte GAHH67MAUSB-B3
Corsair 8GB 2x4 D3 1333 C9
Thermalake TA V4 Case
Antec Ea650 Grenn 650w atx psu
Samsung oem sam 22x sata dvdrw
1 TB Seagate 3.5" sata 7200RPM
win 7 64 home premium

will run suggested mem check + windows memcheck and boot from usb and ubuntu memtest86
 
Still getting same BSOD

Windows and memtest86 find no problems with memory
Boot into Safe Mode,
Start Office Word, Excel, PowerPoint, Aceess,
Firefox, Ultraedit, etc no BSOD after 6 hours

PCMark basic benchmarks - passed

=============
Playing music with MediaMonkey, I can reliably reproduce BSOD within a period of 1 to 3 hours.
Latest minidump attached

=============
SWAGs

Audio setup

My system is using this, instead of Intel Audio on chip.
Audio Driver for Intel Desktop Board
Product Detected Realtek High Definition Audio
Current Driver Installed 6.0.1.6307
ALC889

I do not see a way to switch to Intel High Definition Audio
Award Modular bios v6.00PG BIOS settings

-> Azalia = auto gives me realtek, = disabled no audio

Is this normal
mcupdate_GenuineIntel.dll fffff880`00c4b000 fffff880`00c9a000 0x0004f000 0x4ce7c737 11/20/2010 9:03:51 AM
 

Attachments

  • 082111-19359-01.7z
    16 KB · Views: 4
Again memory corruption is what caused your crash.

I would suggest you to run your system on one RAM Module for a while and see how your system behaves. Sometimes memtest is unable to find any issues with RAM even when they are there.
 
Back