The faulting ntdll.dll module might indicate a problem with an out-of-date driver for a graphics card or network adapter. AngryJackal reported here that a driver upgrade for his Bigfoot/Atheros network adapter resolved a conflict with NAV 21.x.
I'm not certain, but I think ntdll.dll is a NVIDIA file. Do you have a NVIDIA graphics card or run NVIDIA Network Access Manager on your computer? Other network monitoring software (e.g., Asus Network iControl, Applian Network Monitor) is known to cause conflicts with NIS 21.x on some Asus computers - see lancea's post here.
RickNelson1 reported here that a BSOD problem was solved by wiping remnants of an old McAfee AV installation off his computer. Have you ever had any AV software other than NIS running in real-time protection mode on your system?
------------ MS Windows Vista Home Premium 32-bit SP2 * Firefox 25.0.1 * IE 9.0 * NIS 2013 v. 20.4.0.40 HP Pavilion dv6835ca, Intel Core2Duo CPU T5550 @ 1.83 GHz, 3.0 GB RAM, NVIDIA GeForce 8400M GS
Thanks a quick google search for " ntdll.dll Win 7 " is a MS file usually related to a curropt user profile / Non MS App / Outlook
I do think that Norton Utilities is wiping a few of my AMD Vid drivers out though, as well as it's on latest bug problem that happened just before/same time as this NIS update.
Will keep looking.
My other BSOD was my ram was at a new setting I was testing out.
To anyone else still experiencing BSODs on your computer, information from your Windows blue screen memory dumps can be extracted using NirSoft's BlueScreenViewand often provides valuable information about the specific file or process causing the BSOD. I've posted instructions here for collecting and posting diagnostic logs of BSOD minidumps in this forum.
Kudos to delphinium for initially providing the link to this utility.
------------ MS Windows Vista Home Premium 32-bit SP2 * Firefox 25.0.1 * IE 9.0 * NIS 2013 v. 20.4.0.40 HP Pavilion dv6835ca, Intel Core2Duo CPU T5550 @ 1.83 GHz, 3.0 GB RAM, NVIDIA GeForce 8400M GS
Thanks a quick google search for " ntdll.dll Win 7 " is a MS file usually related to a curropt user profile / Non MS App / Outlook
I do think that Norton Utilities is wiping a few of my AMD Vid drivers out though, as well as it's on latest bug problem that happened just before/same time as this NIS update.
Will keep looking.
My other BSOD was my ram was at a new setting I was testing out.
Happy bug hunting.......
Although I understand that the problem seems to have started with the Norton update; Considering that we are talking about a RamPage (nice MB, BTW) and an OC'd GPU (for starters)...
I'd presume that there are probably other various OC tweaks "in play" here.
Purely for test purposes, have you tried temporarily returning all OC "customized settings" to their factory "safe clock" defaults to determine if any of them correlate to the BSOD problem?
Both MOB's are Asus Republic Of Gamers board's which are tuned to best possible performance out of the board/chip/ram/vid
at factory settings. So with a little bit of research to find what can be changed with out pumping voltage it is minor tweaks that run stable. i7-960 is a hice chip as it is. The other chip is unlocked so I am getting what intel gave me along with stock ROG board.
The BSOD re ram settings was prior to NIS BSOD and settings were adjusted back on the Rampage to stable positions when
had the NIS BSOD.
The Vid card is factory OC'd and I am not about to play with what works fine as it is.
Since I have had no BSOD since the NIS BSOD I would say with confidence that am at all stable settings.
With that i find that to revert to factory settings with these boards are still reverting to a optimized default as that is the only other F10 and save setting can use.
But regardless splitting hairs here.
Oh and not really a novice poster just a new account as I was Norton beta testing in 04,05,06,07,08