Faulting application name: svchost.exe_SysMain

[meandm]

So, I've been having this problem that's been pissing me off to no end. After countless hours of searching for someone with the same problem and having no luck, I turn to these forums for help. Hopefully you guys can succeed where I have failed over and over.

My rope is 10 feet long, and I am just inches from throwing my computer around like a monkey. Which would not be good on a nice gaming computer... not nice at all.

So here's what's going on. I've learned that it's a Superfetch process, so I've gotten that far... but how to fix my problem is another story.

Here's the data:

Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
 
Faulting module name: sysmain.dll, version: 6.1.7600.16385, time stamp: 0x4a5be07e
 
Exception code: 0xc0000005
 
Fault offset: 0x000000000004ed8b
 
Faulting process id: 0x1880
 
Faulting application start time: 0x01cc312f7183d97e
 
Faulting application path: C:\Windows\System32\svchost.exe
 
Faulting module path: c:\windows\system32\sysmain.dll
 
Report Id: a2638cf6-9d25-11e0-8f1b-001d7d0759a8
 
------------------------------------------------------------------------------------------------------------------
 
- System 
 
- Provider 
 
[ Name] Application Error 
 
- EventID 1000 
 
[ Qualifiers] 0 
 
Level 2 
 
Task 100 
 
Keywords 0x80000000000000 
 
- TimeCreated 
 
[ SystemTime] 2011-06-22T23:16:19.000000000Z 
 
EventRecordID 7436 
 
Channel Application 
 
Computer FTW 
 
Security 
 
 
- EventData 
 
svchost.exe_SysMain 
6.1.7600.16385 
4a5bc3c1 
sysmain.dll 
6.1.7600.16385 
4a5be07e 
c0000005 
000000000004ed8b 
1880 
01cc312f7183d97e 
C:\Windows\System32\svchost.exe 
c:\windows\system32\sysmain.dll 
a2638cf6-9d25-11e0-8f1b-001d7d0759a8

No idea what I'm looking at here

 

[Wallonn7]

Hi meandm and welcome to SF!
Follow Blue Screen of Death (BSOD) Posting Instructions guidelines.
It helps us to help you.
Let us know when you're ready.

 

[meandm]

It's not a BSOD though =/

 

[Wallonn7]

It's not a BSOD though =/

Well, "BSOD Dump & System File Collection app" gathers information that will help us give you more precise answers to solve your problem...

 

[meandm]

Here's everything that BSOD thing wanted... I'm not sure how it is going to help diagnose the problem though... Something I don't know about maybe, learn something everyday!

 

[meandm]

Is that enough? Do you guys want more? I'd really like to get it solved, so if you guys need anything else let me know please.

 

[Wallonn7]

Hi...
Between April and 22 May were 16 dump files ...
Well, run Memtest86+ at least for 8 passes.

Bugcheck

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0321d000 PsLoadedModuleList = 0xfffff800`0345ae50
Debug session time: Wed Jun 22 19:26:58.387 2011 (UTC - 3:00)
System Uptime: 0 days 17:37:35.166
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000044718, d80000017aaca867, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31eb2 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)

===========================================

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03206000 PsLoadedModuleList = 0xfffff800`03443e50
Debug session time: Mon Jun 20 10:19:11.266 2011 (UTC - 3:00)
System Uptime: 3 days 2:47:59.045
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600003fb99, fffff8800b329fd0, 0}

Probably caused by : win32k.sys ( win32k!RGNOBJ::bCopy+29 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)


===========================================

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a0e50
Debug session time: Tue Jun 21 02:36:19.067 2011 (UTC - 3:00)
System Uptime: 0 days 16:15:47.847
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 73b3b, 2, 73b03}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)

Let us know the results.

 

[meandm]

Ok, so I'm at 5 passes and no errors, I had to stop the process to use my computer for work. I'll run it again later when I have the time.

 

[meandm]

8 passes, 0 errors.

Now what? =(

 

[Wallonn7]

Hi...
Please update these drivers:

timntr   timntr.sys   Wed Aug 29 09:38:23 [COLOR=Red][B]2007 [/B][/COLOR]
snapman  snapman.sys  Thu Nov 22 06:19:33 [COLOR=Red][B]2007[/B][/COLOR]
tifsfilt tifsfilt.sys Wed Aug 29 09:37:29 [COLOR=Red][B]2007[/B][/COLOR]
scmndisp scmndisp.sys Wed Jan 17 05:48:03 [B][COLOR=Red]2007[/COLOR][/B]

The first three are Acronis True Image drivers. If you can not upgrade to the latest version, I suggest you uninstall the program in order to avoid inconveniences. The other is a netgear driver.

Then enable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, 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).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.