Help with Bsod please!!

Jonathan_King · 03 Aug 2010

Comodo should be uninstalled completely, and the Windows Firewall reset.

Open an elevated command prompt and enter NETSH FIREWALL RESET.

Code:

cmdguard.sys Fri Jun 04 05:58:07 2010
cmdhlp.sys   Tue Jun 01 13:43:12 2010

If the crashes continue, enable driver verifier: Driver Verifier - Enable and Disable

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 18:22:12.353 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:47.789
BugCheck 1A, {41790, fffffa80012d4550, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug  2 18:19:22.744 2010 (UTC - 4:00)
System Uptime: 0 days 3:00:44.180
BugCheck 1A, {41790, fffffa800130ff50, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a08 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

jpwwong · 04 Aug 2010

Hi again,

I've reinstalled my windows, with nothing on it, and I got 3 BSOD tonight. Can you help me please to see what's causing it?

I'm suspecting that since I have nothing on my system, its pointing to a faulty hardware? I've passed memtest which ran overnight. I am using 2 old IDE HDD at the moment, could that be a cause of it?

Thanks again.

Tews · 04 Aug 2010

The dmp(s) point to ntkrpamp.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. Enable driver verifier ....

Here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

jpwwong · 04 Aug 2010

Ok i've enabled driver verifier, and i'll post up any dumps if the system crashes. If it doesnt crash after 36 hrs,what does that exactly mean? Also, can I check if I have correctly enabled the verifier?

If I suspect there is something wrong physically with the motherboard, or the graphics card, is there anyway I can test it? Will either cause BSOD?

Thanks.

Tews · 04 Aug 2010

Its possible, but lets see what driver verifier turns up..

jpwwong · 04 Aug 2010

At the risk of sounding stupid, by not selecting window drivers, does it mean that all windows drivers will never cause BSODs?

Also, once enabled, can I re-run the exe file and add more drivers for testing?

Tews · 04 Aug 2010

Dont exclude anything, you want all of the drivers tested... Dont worry about how long it takes, you want driver verifier to stress all of the drivers ....

jpwwong · 04 Aug 2010

Hi

Dumps after verifier was enabled. Hope it tells you something!

Thanks

jpwwong · 05 Aug 2010

Someone help please!

Jonathan_King · 05 Aug 2010

Sorry, I was busy yesterday.

Please update your outdated Realtek network drivers:

Code:

RtNdPt60.sys Sun Jul 19 22:27:32 2009

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug  3 21:29:12.440 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:49.876
BugCheck 1A, {41790, fffffa8001327050, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨