[jab123]

I receive the IRQ_NOT_LESS_OR_EQUAL errors randomly, they happen every day or two. In specific, 0x0A comes up the most following D1 on occasion and even less so for the 050 error. I would upload the .dmp files found in Minidump, but GTG's attachment uploader prohibits them. I believe the blue screens really started around the time where I got my memory stable at its specified speed via the BIOS settings as well as having a large Windows Update. I've ran Memtest before, and the memory was a problem prior to this one and I discard the notion that the culprit is memory here...I suppose I could be wrong though. I suspect it to be a driver issue...but, I don't know which driver is causing the bsod's. I've updated my graphics card driver (not the latest, but its fairly new) and the audio driver.

Specs:
Antec 900
Q9500
Zalman 9300AT w/ AS5
GA-EP45-UD3P
Mushkin 996599 1066 DDR2
WD Caviar Black 1TB
GTX 260 Core 216
Antec TP 750w
Vista x64 Premium

[Advertisements]

Hello jab123...

How much RAM do you have installed and what voltage do you have it running on?

wannabe1

[wannabe1]

Hello jab123...

How much RAM do you have installed and what voltage do you have it running on?

wannabe1

[jab123]

i have 4GB with a MCH voltage stable at 0.95V.

[Broni]

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

[jab123]

K, uploaded the .txt file.

By the way, this PC is new.

Attached Files

•  bsod.txt   17.75KB   211 downloads

Edited by jab123, 22 September 2009 - 11:03 PM.

[Broni]

==================================================
Dump File : Mini090909-01.dmp
Crash Time : 9/9/2009 9:20:05 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`00125639
Parameter 3 : fffffa60`084c5040
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c5639
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini090909-02.dmp
Crash Time : 9/9/2009 5:54:24 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000047
Parameter 2 : fffff800`01ce71b4
Parameter 3 : fffffa80`047af8b0
Parameter 4 : fffffa80`02167c30
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+80cc6
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini090909-03.dmp
Crash Time : 9/9/2009 6:08:23 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000047
Parameter 2 : fffff800`01ecd1b4
Parameter 3 : fffffa80`061fe501
Parameter 4 : fffffa80`00000001
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+13e050
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini090909-04.dmp
Crash Time : 9/9/2009 8:41:24 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`01eb74cf
Parameter 3 : fffffa60`0638be80
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini091009-01.dmp
Crash Time : 9/10/2009 7:49:55 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`e54dcc38
Parameter 2 : 00000000`0000000c
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`01e9ae6d
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini091009-02.dmp
Crash Time : 9/10/2009 8:51:12 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`0000888a
Parameter 2 : fffff680`0000b2e8
Parameter 3 : fffff680`00024828
Parameter 4 : fffffa80`01553340
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini091109-01.dmp
Crash Time : 9/11/2009 6:21:47 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000047
Parameter 2 : fffff800`01e961b4
Parameter 3 : fffffa80`0731cc60
Parameter 4 : fffffa80`042d13e0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini091809-01.dmp
Crash Time : 9/18/2009 9:43:53 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`01eba146
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`000083ae
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini091809-02.dmp
Crash Time : 9/18/2009 11:20:56 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`18410040
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa60`052ba86f
Caused By Driver : vsdatant.sys
Caused By Address : vsdatant.sys+486f
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini091809-03.dmp
Crash Time : 9/18/2009 11:53:42 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`1f6ebba8
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`01ee1421
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini091909-01.dmp
Crash Time : 9/19/2009 11:34:52 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005100
Parameter 2 : fffff6fc`4007c968
Parameter 3 : 00000000`00000004
Parameter 4 : 00000000`00000020
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini092009-01.dmp
Crash Time : 9/20/2009 11:54:11 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`03003510
Parameter 2 : 00000000`0000000c
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`01e6b1fc
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+1f86
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini092009-02.dmp
Crash Time : 9/20/2009 5:50:10 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`01eb5146
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : cmdguard.sys
Caused By Address : cmdguard.sys+e521
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini092109-01.dmp
Crash Time : 9/21/2009 9:49:54 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`0cf1e1c8
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`01eb6fee
Caused By Driver : pci.sys
Caused By Address : pci.sys+c5c41c8
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

==================================================
Dump File : Mini092209-01.dmp
Crash Time : 9/22/2009 9:34:04 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`3fa09898
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`01ee4421
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a450
File Description :
Product Name :
Company :
File Version :
Processor : x64
==================================================

[Broni]

I suspect, you have some RAM problem....

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[jab123]

I have a bootable iso of memtest 2.11 I've ran both sticks before for an hour and memtest displayed two passes. I'm likely to be too busy during the day for the rest of the week to sort out if my RAM is faulty, so I'll probably get around to memtest sometime this weekend. I'd rather not run it overnight because I can't sleep with the LED's and the fans on lol.

[Broni]

Since you have 2 sticks of RAM...

A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A