Random BSODs

[Yerfdog]

Newly (3 months) home built PC. Experiencing BSODs randomly, usually overnight. Only scheduled task overnight is AVGFREE scan. This morning, had "Windows Desktop Manager has quit working" message.

Have run memtest with no errors. Have verified signed drivers. Verified latest MB drivers. Any help is greatly appreciated.

Two minidumps attached.

Thanks!

 

[zigzag3143]

Newly (3 months) home built PC. Experiencing BSODs randomly, usually overnight. Only scheduled task overnight is AVGFREE scan. This morning, had "Windows Desktop Manager has quit working" message.

Have run memtest with no errors. Have verified signed drivers. Verified latest MB drivers. Any help is greatly appreciated.

Two minidumps attached.

Thanks!

These were caused by two different things. First your avgfree AV, and then your nbagent.exe (nero backup)

Both have history with causing BSOD's

I would remove both and replace with microsof security essentials, and some other cd burning utility.

Let us know if you need help

Ken

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 09:14:38.644 2010 (GMT-4)
System Uptime: 1 days 15:39:37.361
BugCheck 1A, {41201, fffff680003a15f8, 9130000034ffc847, fffffa80068dc010}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  NBAgent.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 18 02:00:58.406 2010 (GMT-4)
System Uptime: 1 days 13:23:10.091
BugCheck 50, {fffff8a00d9e8000, 0, fffff80002c6a430, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42877 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  avgcsrva.exe

 

[Yerfdog]

Ken, thanks so much. I was planning on going with MSE, and had considered getting rid of Nero as well, as it has been suspect in the past.

How did you come up with those? I had used WinDbg, but came up with nothing definitive?

Again, thanks. My BSODs are typically at least a week apart, so it may be a while before I report back (hopefully).

Thanks!

 

[zigzag3143]

Ken, thanks so much. I was planning on going with MSE, and had considered getting rid of Nero as well, as it has been suspect in the past.

How did you come up with those? I had used WinDbg, but came up with nothing definitive?

Again, thanks. My BSODs are typically at least a week apart, so it may be a while before I report back (hopefully).

Thanks!

You probably ran the basic modules like (!analyze -v). You can also examine the memory stack to see what is loaded at the crashing address. they even show as the process listed below.

Anyway good luck

Ken

 

[Yerfdog]

Ken, thanks so much. I was planning on going with MSE, and had considered getting rid of Nero as well, as it has been suspect in the past.

How did you come up with those? I had used WinDbg, but came up with nothing definitive?

Again, thanks. My BSODs are typically at least a week apart, so it may be a while before I report back (hopefully).

Thanks!

You probably ran the basic modules like (!analyze -v). You can also examine the memory stack to see what is loaded at the crashing address. they even show as the process listed below.

Anyway good luck

Ken

I did just that. Thanks!

 

[usasma]

Don't forget to turn Driver Verifier off (Delete existing settings)!

Good luck!

 

[Yerfdog]

Will do. Thanks!

 

[Yerfdog]

It was clear for over a week, made it through weekly overnight tasks, and this morning, once again, rebooted from blue screen.

Attached is the single minidmp, zipped. AVG is gone, Nero is gone, Microsoft Security Essentials is installed.

 

[usasma]

From my page here: BSOD Index - STOP 0x109
The usual causes are:
- Device driver (unlikely as you ran Driver Verifier previously and it didn't pick it up)
- Developer set a breakpoint without attaching (you'd know that someone was developing code on your system)
- Hardware failure (memory is most likely).

So, as the hardware is the most likely issue, let's try some diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

If the above tests pass, then try these tests (it'll stress test the other memory in your system - video and CPU/mobo):

Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: http://www.mersenne.org/freesoft/

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Summary of the BSOD:

Debug session time: Tue Jun  1 05:59:17.625 2010 (GMT-4)
System Uptime: 3 days 11:08:00.622
BugCheck 109, {a3a039d89d2d3659, b3b7465eefab487b, fffff88000d80d60, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System

 

[Yerfdog]

Thank you for responding quickly - I was out all day....

I have done Memtest for many passes, with no issues. I have done HD testing and diagnostics on all drives with no issues. Both of these were completed before my first round of contacting SevenForums a week or so ago when the first two issues arose.

I am currently doing online school (BS/IT - software engineering). I am currently in a Java class, and have the JDK and NetBeans installed - I have been creating code, albeit at this time it is merely mortgage calculators and such - nothing too in depth. Is there anything I could have done in the course of using (or installing)the JDK or the JRE that could have caused the problem?

Also, twice now I have dealt with (I believe it is) Super Anti Spyware, though I do not know how it was contracted. The first time was about three weeks ago - it was cleaned quite thoroughly, and the second was after I first contacted these forums. Again, it would appear it was thoroughly cleaned (Rootkill, MalwareByte, etc.).

In the meantime, I will run the HW diagnostics as recommended, perform the online Malware checks, and the free online stress tests. I will post back with the results.

Thanks!

 

[usasma]

No, you'd have to establish breakpoints in the process of debugging the code - and it doesn't sound like you've done any of that.

Incomplete cleaning of the malware may have caused issues also. I'd suggest running several of the online scans to ensure that everything is gone.

Good luck!

 

[Yerfdog]

FurMark - no problems, max GPU temp 72c. No hiccups.
Running Prime 95 now.

 

[Yerfdog]

Ran 4 or 5 online malware scanners, per instructions (no malware). Prime95 no errors. Re-ran Memtest for multiple passes - no errors. Ran HD diagnostics again, no problems. Any other suggestions?

 

[usasma]

Run Memtest overnight,
Run Prime95 for a minimum of 12 hours
If still no errors, we'll go back in and look for driver issues.