FNG Can't Solve Bluescreen Issues

DDK · 20 Jul 2010

Hi All,

I am getting regular BSOD's on my Win 7 system. I was getting them in Vista too, but with a conversion to 7 I figured I'd get the OS switch done before I dealt with it. Unfortunately, with the OS swap done I'm realizing I'm over my head dealing with it. I don't know what to do next, hoping you guys can help.

I have the Windows7_BSOD_jcgriff2 folder & the PERFMON zipped up and attached.

The computer was built by a tech I know a couple years ago. Everything is that old.

1GB Kingston Ram (was running 2G but they are not matched. memtest came back ok so I tried using just one, then just the other, hoping to solve it with no luck).
Dual Core Pentium D 2.8G
Win 7 Pro 32 bit
NVidia GeForce 8400 GS vid card
WD 150G SATA drive
Dual display setup

If I left anything out, it may be in my user profile, or just ask and I'll do my best to answer. Any help on this would be greatly appreciated.

Thanks,

-ddk

edit: Thanks for TEWS for pointing out I screwed up adding the dmp files in the BSOD info zip. The perfmon html should still be there, and I'm adding the dmp files to this original post as well as post 3. Sorry for the screw up.

Tews · 20 Jul 2010

Unfortunately there were no .dmp files included... check your c:/windows/minidump folder and zip up any .dmp files and upload them....

DDK · 20 Jul 2010

Sorry about that! They should all be included in the attached zip.

DDK · 20 Jul 2010

So I tried to make some sense of my performance check, since the other dmps don't make any sense to me.

Here's what I got:

1) PS/2 Keyboard is not configured properly, and won't be available until the issue is resolved. That's odd, because I'm using the keyboard to type this - seems to work fine?

2) Security can't find my AV. I'm using AVG. Not a big deal, since I'm pretty sure that's not the issue.

3) The "CPU" rating for the system is poor and may be the cause of performance problems. Reducing the number of open applications may improve system performance. Check for unnecessary startup applications and disable those that are not required.
-It's a dual core 2.8G, isn't that plenty? It doesn't seem to top out based on the gadget on my desktop. Could this be my issue?

4) The "Graphics" rating for the system is poor and may be the cause of performance problems. Disabling Desktop Composition or reducing screen resolution may improve graphical performance. If the problem continues the display adapter may need an updated driver or may need to be upgraded.
-Nvidia GeForce 8400 256M not enough? I'm not gaming with it. Could this be the problem?

5) The "Disk" rating for the system is poor and may be the cause of performance problems. Reducing the number of open applications may improve system performance. Ensure the disk has adequate free space and is defragmented. Check for unnecessary startup applications and disable those that are not required. If the problem continues the disk may need to be upgraded.
-I have 76.5G pf 97.6G free on my primary partition, and 45.5 of 51.2 free on my secondary. OS is on the primary. Install is clean from formatting and partitioning yesterday. WD SATA drive.

6) The "Memory" rating for the system is very poor and may be the cause for performance issues. Reducing the number of open applications may improve system performance. Check for unnecessary startup applications and disable those that are not required. If the problem continues the me
-So more memory? That was in the works for eventually anyway, but if I have to end up upgrading the mobo/CPU I don't want to waste $ on memory that won't switch to the new stuff. Thoughts?

7) The average disk queue length is 1.012. The disk may be at its maximum transfer capacity due to throughput and disk seeks
-I don't even know what this means, to be perfectly honest.

Am I looking in the right direction here? I'm more than willing to do my legwork and help myself, I just seem to be out of my league and over my head here.

Thanks for any input.

Jonathan_King · 20 Jul 2010

It appears to be caused by hardware. That is further supported by the fact that the BSODs were in Vista too.

See this article on your bugcheck 124: Stop 0x124 - what it means and what to try

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Test your hard drive: HD Diagnostic

Try this free stress test: Free Software - GIMPS

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 Dumps:

Code:


Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jul 20 13:12:29.443 2010 (UTC - 4:00)
System Uptime: 0 days 10:49:36.083
BugCheck 1000008E, {c0000005, 928fe17d, ac540c40, 0}
Probably caused by : win32k.sys ( win32k!GreIsRendering+30 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  aim.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jul 20 14:14:01.661 2010 (UTC - 4:00)
System Uptime: 0 days 1:00:57.301
BugCheck 100000BE, {937b6323, 10b50021, 9c6ef2dc, b}
Probably caused by : memory_corruption
BUGCHECK_STR:  0xBE
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jul 20 01:27:18.588 2010 (UTC - 4:00)
System Uptime: 0 days 0:55:39.245
BugCheck 1000008E, {c0000005, 91afad86, 9b06faec, 0}
Probably caused by : HdAudio.sys ( HdAudio!CAzMixertopoMiniport::`vftable'+2 )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  audiodg.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jul 20 02:21:51.212 2010 (UTC - 4:00)
System Uptime: 0 days 0:48:56.853
BugCheck 1000007F, {8, 807c4750, 0, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  SearchFilterHo
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jul 20 00:31:04.489 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:16.129
BugCheck 1000007F, {8, 807c4750, 0, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jul 20 14:24:55.233 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:19.874
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Jul 19 23:06:28.937 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:12.578
BugCheck 124, {0, 853608fc, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System

DDK · 20 Jul 2010

Thanks so much for the reply.

One thing I forgot to mention is that I did run a memory diag a few weeks ago, when it was BSODing w/ Vista. I ran that overnight and got no errors.

I ran a HD test as soon as you posted up to try it. That came back as a "pass" also.

Seems the main thing left is the GIMPS test. It's been stress testing for a while now. The first time I tried it I was doing other things also (trying to reply to your post being one) and it BSOD'd on me. I fired it back up and tried again, and it's been going well so far.

Not really sure what's next, if this doesn't spring any errors I guess I'm back at a loss. At this point I'm half tempted to just replace the mobo, CPU & memory since it could all stand to be upgraded anyway but...

1) I work from home, so that's a frustrating work week.
2) That's not fixing my problem, it's just part swapping, and I don't like doing things like that on principle.
3) That may not even solve the problem!

**Capt.Jack Sparrow** · 20 Jul 2010

Hello,

The build in Memory Diagnostic won't help. Download the Memtest86+ and run atleast 6 passes.

- Captain

DDK · 21 Jul 2010

Thanks for the help guys. I passed the overnight mem test, and the GIMPS test. Not sure where to go next, but I'm still getting bluescreens today. If anything, they're more common. Maybe swap the RAM anyway as a next step? Could it be the video card?

Jonathan_King · 21 Jul 2010

How long did you run Prime95 for?

Go ahead and swap out hardware if you have access to it.

DDK · 21 Jul 2010

Jonathan_King said:

How long did you run Prime95 for?

Go ahead and swap out hardware if you have access to it.

I ran Prime 95 for about 6 hours. It said if it's going to error it'll usually do it pretty quick, so I figured that was sufficient? I also wanted to get the memtest going before I went to bed.

I don't have access to hardware, so that's going to get expensive fairly quickly. That's also why if I have to, I'd like input on where to start. Memory isn't a big deal because it's cheap and I need more anyway - anything else is just wasted $ if it doesn't fix the problem.