Windows 7: 200+ bsod

deeptrouble · 18 Aug 2010

Here we go. Im having loads of BSODs and no skills dealing with them. Ive attached the recommende debug files. My perfmon is written in Danish. If it is completely nonsense let me know what to translate. Thanks. Virtual beer is rewarded for any help!

deeptrouble · 18 Aug 2010

I tried to install MSE. Unfortuneately it cannot update to get the newest definitions. It says im unable to get updates because my windows update client is not functioning.

Sounds like deep trouble to me..

Lemur · 18 Aug 2010

I'm seeing memory corruption. You may want to try new memory to see if this resolves your problems. Fortsat god dag!

Jonathan_King · 18 Aug 2010

While bad RAM is possible, I suspect it is software-related.

I wonder if AVG is causing the issue. Please remove it with this tool: http://download.avg.com/filedir/util...removerx64.exe

Replace it with MSE: http://www.microsoft.com/security_essentials

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

Post back the new dump files, if you get more BSODs: http://www.sevenforums.com/tutorials...en-forums.html

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Aug 16 20:00:17.761 2010 (UTC - 4:00)
System Uptime: 0 days 11:35:54.900
BugCheck 1A, {41287, 4ec200000080, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  AdobeARM.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 17 13:07:15.215 2010 (UTC - 4:00)
System Uptime: 0 days 0:26:19.355
BugCheck D1, {fffff84802cc1cd7, 2, 8, fffff84802cc1cd7}
Probably caused by : win32k.sys ( win32k!memmove+d2 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 18 09:01:11.609 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:40.637
BugCheck 50, {fffffa7fffffffea, 0, fffff80002eb0deb, 7}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 18 09:49:00.282 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:12.437
BugCheck 1E, {ffffffffc0000005, fffff80002ede095, 0, ffffffffffffffff}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 18 09:17:05.001 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:03.156
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42be5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  avgcsrva.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 18 09:23:57.814 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:19.969
*** WARNING: Unable to verify timestamp for grmnusb.sys
*** ERROR: Module load completed but symbols could not be loaded for grmnusb.sys
BugCheck 1000007E, {ffffffffc0000005, fffff880059fc351, fffff880035703a8, fffff8800356fc10}
Probably caused by : grmnusb.sys ( grmnusb+5351 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

deeptrouble · 18 Aug 2010

Hello guys. Thanks for helping me.

I dont believe i got a HW problem. Memtest86 has never spotted any problem despite 24h runs. neither has the BIOS program that tests RAM.

I had problems removing AVG9. The suggested tool just stalled when looking for a file. I tried the standard way of removing AVG, but it stalled when I asked it to remove user settings as well. When I choose just to uninstall but preserve the setting AVG got uninstalled.

As mentioned earlier I tried MSE, but it has trouble updating its malware definitions. It is caused by a nonworking windows update service. I cant use the regular windows update either.

When I want to close down the computer it has 14 updates ready for installation, but the computer shuts down while processing the first update.

Havent seen af BSOD since my AVG removal. I also used the other removal tool for sptd.sys.

Thanks so far.

Jonathan_King · 18 Aug 2010

You're welcome.

You may try running the AVG removal tool in Safe Mode.

MSE is the best free anti-virus (in my opinion), but Avast is also good. MSE is the only free AV I haven't seen cause problems, but go ahead and try Avast.

avast! - Download Free Antivirus Software or Internet Security

deeptrouble · 18 Aug 2010

Well I got another BSOD :-(

I think im gonna stay with MSE, I just need it to fix my update service again..

Jonathan_King · 18 Aug 2010

Remove AVG: http://download.avg.com/filedir/util...removerx64.exe

Remove Daemon Tools Lite, and then remove SPTD: DuplexSecure - Downloads

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 18 09:49:00.282 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:12.437
BugCheck 1E, {ffffffffc0000005, fffff80002ede095, 0, ffffffffffffffff}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Aug 18 09:01:11.609 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:40.637
BugCheck 50, {fffffa7fffffffea, 0, fffff80002eb0deb, 7}
Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

deeptrouble · 18 Aug 2010

Hello Jonathan.

I already did those steps.

Does it still show up in the newest BSOD?

Jonathan_King · 18 Aug 2010

Yes, as far as I can see.

Tell you what. Delete all the dump files in C:\Minidump, and if you get another BSOD, follow the BSOD Posting Instructions again.

Windows 7: 200+ bsod

200+ bsod problems?