Irq_not_less bsod :(

[Jj1nN]

Hello.

(I don't know how to disable automatic system reboot in windows 7)

So I only memorized some of the blue screen info:

IRQ_NOT_LESS_OR_EQUAL

I know i have an other thread open on the forum, but somehow i get less BSOD's now.. i think i reinstalled some drivers not sure.

I would appreciate if someone would look at the attached files, thanks in advance


System Manufacturer/Model Number
N/A
OS
Windows 7 Ultimate x64
CPU
AMD PHENOMII 955 (4x3.2GHZ)
Motherboard
MSI 770-C45
Memory
4GB 1333MHZ DDR3, GEIL
Graphics Card(s)
GEFORCE GTX470
Sound Card
7.1 SURROUND SOUND
Monitor(s) Displays
Acer P225HQ
Screen Resolution
1600:900
Hard Drives
1000GB SATAII WD 7200RPM
PSU
750W psu,17DB

 

[Jj1nN]

I think it constains two .dmp files.

 

[Tews]

I'm having a look now ...

 

[Tews]

Ok .. Your first .dmp file point to ntkrnlmp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.

However, your second .dmp file is blaming your video card driver (nvlddmkm.sys). Completly remove this driver with DriverSweeper, then download the latest driver from Nvidias' support page...

Based on your other thread, I suspect your video card... Let us know how it goes after updating the driver...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002d080c5, fffff8800757c090, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDpcInterrupt+1b5 )

Followup: MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffe4801adb959c, 2, 1, fffff88013f507cd}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+f97cd )

Followup: MachineOwner
---------

 

[Jj1nN]

Ok thanks a lot i will do it now, and get back to you to let you know

 

[Jj1nN]

Ok so far i have not encountered a problem running the program that caused the BSOD. Can't call it fixed yet, need more time

I did experience a BSOD in another program :/

 

[Jonathan_King]

Hello,

Could you please follow the BSOD Posting Instructions again?

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Jj1nN]

Sorry for the delay, i have encountered several BSODs since last time... (even after cleaning drivers/reinstalling)

attached the dumps.

I don't know if i should make a new post or just update this (chose the update part)

 

[Jonathan_King]

Hmm...I wonder if SPTD is the cause. Please remove Daemon Tools Lite, and then remove SPTD itself. Use this tool: http://www.duplexsecure.com/download/SPTDinst-v174-x64.exe

The bugchecks are all over the place, so I suspect it is either SPTD or hardware.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 25 11:44:29.952 2010 (UTC - 4:00)
System Uptime: 0 days 0:45:15.747
BugCheck 3B, {c000001d, fffff88013e0724a, fffff88004354a40, 0}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 23 17:12:15.684 2010 (UTC - 4:00)
System Uptime: 0 days 0:34:05.479
BugCheck 18, {fffffa8003a01570, fffffa8006d2db70, 1, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+463ba )
BUGCHECK_STR:  0x18
PROCESS_NAME:  Arcania.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 23 16:37:41.367 2010 (UTC - 4:00)
System Uptime: 0 days 0:43:56.162
BugCheck 3B, {c0000005, fffff80002ef6ca5, fffff88008322630, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  PSANHost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 23 15:53:18.989 2010 (UTC - 4:00)
System Uptime: 0 days 1:24:40.409
BugCheck 24, {c08a2, 0, 0, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
BUGCHECK_STR:  0x24
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 23 08:02:00.870 2010 (UTC - 4:00)
System Uptime: 0 days 2:08:48.665
BugCheck 109, {a3a039d8971b54e9, b3b7465ee999922f, fffff88002fde5c0, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 22 13:05:38.948 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:14.369
BugCheck 124, {0, fffffa80049cf8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

 

[Jj1nN]

Thanks i will do as you said, and report back

(just had a freeze btw)

 

[Jj1nN]

Well no BSOD's so far. So it might have worked

But i will not close thread yet, giving it some more time.

Thanks for the help.

 

[Jonathan_King]

46 BSODs / 22 days ~ 2 BSODs every day.

You're doing very well so far, compared to your average, but of course this thread will always remain open, so you can update it if need be.

Happy computing!

 

[Jj1nN]

Oh noes, back with more BSODs :/

attached zip.

 

[Jonathan_King]

Test your RAM: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Test your hard drive too, using this tool: | Seagate

I just noticed your Atheros NIC drivers are old:

L1C62x64.sys Wed Apr 01 01:09:17 2009 (49D2F6FD)

Install these updated ones: Atheros Communications

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  1 16:19:21.609 2010 (UTC - 4:00)
System Uptime: 0 days 2:06:01.404
BugCheck 1000007E, {ffffffffc0000005, fffff88014badffb, fffff88002e2f698, fffff88002e2ef00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  1 11:40:54.384 2010 (UTC - 4:00)
System Uptime: 0 days 0:37:40.179
BugCheck 3B, {c0000005, fffff88001005141, fffff880073fc950, 0}
Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkMulti+51 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

 

[Jj1nN]

Sorry

Sorry for the delay of 127 days

I did a memtest (using memory stick) and used the seagate tool to test my hd. 0 errors.

However i have a bunch of new dumps if you don't mind. (actually only 2)

thanks again.

 

[Jj1nN]

30 minutes after posting in the forum i got one more, this time while playing "minecraft"

attached the dump.

 

[Jonathan_King]

Hello again, welcome back!

I'll just explain the dumps, that will give you your conclusion. The latest dump blames hardware outright, but mentions that the nVidia display drivers were somehow related. The middle dump blames hardware again, with a specific bugcheck that means hardware failure. The third dump doesn't blame anything of consequence, but shows that dwm.exe (the Windows graphics effects process) was "on top" at the time of the crash.

As you can see, this is most likely a physical hardware issue, specifically video card. Before going out and purchasing new hardware, though, give the drivers an update:

nvlddmkm.sys         Fri Jul 09 17:15:58 2010 (4C37918E)

New drivers can be found here: NVIDIA DRIVERS 266.58 WHQL

If that doesn't help, you might as well just run a couple of diagnostics just to make sure. I recommend the Blend and Small FFTs Prime95 tests, and 7 passes of Memtest86 overnight.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  8 15:25:13.563 2011 (UTC - 5:00)
System Uptime: 0 days 0:42:02.968
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( nvlddmkm+f97cd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Mar  7 15:24:28.546 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:11.341
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Mar  7 15:21:30.577 2011 (UTC - 5:00)
System Uptime: 0 days 3:09:55.998
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 )
BUGCHECK_STR:  0xc4_91
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4904
SystemProductName = MS-7599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[DeanP]

You are getting STOP 0x124 error - see this: http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Jj1nN]

When i download and install those drivers. I see a black box around the actual screen area.

If i change resolution, said box becomes smaller/larger, this forces me to use max resolution. (this is actually why i downgraded the driver again months ago, since some programs run using a specific resolution, thus creating the black border)

It is described here. Don't know if there is a fix?
Low resolution always stretched to full screen - NVIDIA Forums <- specially the last angry post.

 

[Jonathan_King]

I suggest you keep the new drivers for a time, until you determine whether they have solved the problem or not. If do, feel free to play around with different versions; there are many driver releases between July 2010 and March 2011!