Tech Support banner

Status
Not open for further replies.
1 - 20 of 26 Posts

·
Registered
Joined
·
186 Posts
Discussion Starter #1
Greetings, folks. I've been having a few problems on my computer here, and I thought I might ask for help on a good looking forum. I'm somewhat computer savvy, I know where to find certain bits of information on my PC, but it's difficult finding how to fix anything on Vista, for me at any rate.

So, here's my current problems. First of all, when attempting to watch a video in full screen, such as from Youtube, or when playing certain games that have cinematic sequences, such as Warcraft III, the screen goes blank. I still have audio, I just can't see anything. In the case of Warcraft, I still had subtitles.

My other problem is pertaining to the use of a Joystick with the game Mech Warrior 4. While all the testing I have done with the joystick in the installation screen shows that it should work properly, it doesn't seem to work on the game.

I'm not sure what all information I have will be of use, but here's my specs; I am using a Dell XPS XPS_420, with Windows Vista Home Premium, service pack 1. Sorry if that's not enough information, just let me know if I need to dig around for more, and thank you all for any replies.
 

·
Registered
Joined
·
186 Posts
Discussion Starter #2
Re: Various Vista Problems

Could somebody at least reply to call me on this if I did something wrong? On top of these problems I'm starting to get connection errors as well, which my searching has whittled down to being Vista's fault... I understand there's probably alot of demand for help here, but could anybody at least say something like, 'Hey, we'll help you out in a week or so'?
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts
Re: Various Vista Problems

Hi -

I assure you that you did nothing wrong. We are all volunteers and unfortunately some threads get by without a response. My apologies to you.

Let me get system info from you and I will take a look when I can. Please follow THESE instructions. Attach the resulting zip files to your next post.

Any ? - please let me know.

Regards. . .

jcgriff2

.
 

·
Registered
Joined
·
186 Posts
Discussion Starter #5
Re: Various Vista Problems

Awesome; thank you guys so much! I appreciate the help, and I'll check that stuff out soon.
 

·
Awesom-O 4000
Joined
·
1,241 Posts
Re: Various Vista Problems

I wonder if maybe you just need a graphics card update. Have you check for updates for the video card?

Also do what jcgriff2 requested.
 

·
Registered
Joined
·
186 Posts
Discussion Starter #7 (Edited)
Re: Various Vista Problems

Hey; I did the suggested thing for getting the System info, and here it is.

Also, thanks for the idea, Rex, but I'm afraid it didn't work; unless I happened to update my video drivers wrong, which I may have.

Edit; forgot to get the HTML file, pardon. Also, hope your family matters are going well, Griff.
 

Attachments

·
Registered
Joined
·
186 Posts
Discussion Starter #8
Re: Various Vista Problems

Hey... just giving this a bump, since it's been a couple weeks now. Thanks in advance folks.
 

·
Registered
Joined
·
186 Posts
Discussion Starter #9
Re: Various Vista Problems

Hey, uh... just giving this another bump... pardon the continuation, has been another couple of weeks, and I really do need some help with these things.
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts
Re: Various Vista Problems

Hi -

1st items that I noticed were audio and

Code:
           Description: Speakers / Headphones (SigmaTel High Definition Audio CODEC)
       Driver Name: stwrt.sys
         Driver Version: 6.10.5511.0000 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 9/12/2007 03:40:48, 326656 bytes
I also noticed quite a few KBs listed -
Code:
     Device Name: Gaming Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC221
        FF Driver: n/a

      Device Name: Gaming Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC221
        FF Driver: n/a

      Device Name: G15 Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC222
        FF Driver: n/a
And more KB - and mice -
Code:
PS/2 Devices
------------
+ HID Keyboard Device
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 1/19/2008 00:49:17, 15872 bytes
| Driver: kbdclass.sys, 1/19/2008 02:41:52, 35384 bytes
| 
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC221
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 1/19/2008 00:49:17, 15872 bytes
| Driver: kbdclass.sys, 1/19/2008 02:41:52, 35384 bytes
| 
+ HID Keyboard Device
| Vendor/Product ID: 0x046D, 0xC222
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 1/19/2008 00:49:17, 15872 bytes
| Driver: kbdclass.sys, 1/19/2008 02:41:52, 35384 bytes
| 
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 1/19/2008 00:49:18, 54784 bytes
| Driver: kbdclass.sys, 1/19/2008 02:41:52, 35384 bytes
| 
+ HID-compliant mouse
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouhid.sys, 1/19/2008 00:49:16, 15872 bytes
| Driver: mouclass.sys, 1/19/2008 02:41:52, 34360 bytes
| 
+ HID-compliant mouse
| Vendor/Product ID: 0x046D, 0xC043
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouhid.sys, 1/19/2008 00:49:16, 15872 bytes
| Driver: mouclass.sys, 1/19/2008 02:41:52, 34360 bytes
| 
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 1/19/2008 02:42:19, 54328 bytes
| Driver: sermouse.sys, 1/19/2008 00:49:16, 19968 bytes
| Driver: mouclass.sys, 1/19/2008 02:41:52, 34360 bytes
Go into Device Manager and 1st un-install all of the KBs. You'll need the mouse to restart. Then do the same with the mice - un-install ALL in devmgmt.msc - use KB CTRL-ALT-DEL to get to logon screen then restart.

Your Intel NIC is from 2007 - update it -
Code:
 Name: Intel(R) 82566DC-2 Gigabit Network Connection
Device ID: PCI\VEN_8086&DEV_294C&SUBSYS_02151028&REV_02\3&172E68DD&1&C8
   Driver: C:\Windows\system32\DRIVERS\e1e6032.sys, 9.08.0020.0000 (English), 9/12/2007 03:44:34, 228224 bytes
   Driver: C:\Windows\system32\Prounstl.exe, 9.01.0001.0000 (English), 9/12/2007 03:44:40, 154496 bytes
   Driver: C:\Windows\system32\e1e6032.din, 9/12/2007 03:44:34, 2689 bytes
   Driver: C:\Windows\system32\NicCo6.dll, 2.00.0001.0000 (English), 9/12/2007 03:44:38, 28536 bytes
   Driver: C:\Windows\system32\NicInE6.dll, 9.08.0001.0000 (English), 9/12/2007 03:44:40, 39288 bytes
   Driver: C:\Windows\system32\e1000msg.dll, 9.07.0000.0000 (English), 9/12/2007 03:44:34, 179048 bytes
See if any there is any improvement after the above items are implemented.

Regards. . .

jcgriff2

.
 

·
Registered
Joined
·
186 Posts
Discussion Starter #11
Re: Various Vista Problems

Hey; I did as you recommended, and the only thing that has changed is my keyboard screen (G15, used for checking stats in certain games, changing tracks on media players, etc., if you didn't know) is no longer working at all, save that it has a Logitech splash screen. Currently I'm looking to see if I have a disk for it, as I don't recall if it needed to be installed or not.

At any rate, that's what's happened thus far; any ideas?
 

·
Administrator, Manager, Microsoft Support, Acting
Joined
·
34,376 Posts
Re: Various Vista Problems

Hi -

Your Event Viewer logs tell a story of continuous problems since your system had its initial boot ~ January 24, 2008. There were 1,000s of application crashes and at least 1 BSOD. Here is a sampling of what I saw - scroll through them and to the right. Look for 0xc0000005 and type 5. These codes mean that an app failed because of an access violation.
Code:
[font=lucida console]
44/29/2009       9:59    AppError        wmplayer.exe,   version 11.0.6001.7004, time    stamp   0x49472063,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
4/29/2009       2:46    AppError        SC.exe, version 1.0.2.0,        time    stamp   0x49e46256,     faulting        module  SC.exe, version 1.0.2.0,        time    stamp   0x49e46256,     exception       code    0xc000000d,
4/29/2009       2:46    WERCON  FaultBkt        536100115,      [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     0

Problem        signature:
&#x00
4/27/2009       10:06   AppError        wmplayer.exe,   version 11.0.6001.7004, time    stamp   0x49472063,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
4/25/2009       13:53   WERCON  FaultBkt        1165590133,     type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
4/25/2009       12:02   AppError        wmplayer.exe,   version 11.0.6001.7004, time    stamp   0x49472063,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
4/21/2009       21:23   WERCON  FaultBkt        498108691,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
4/9/2009        20:20   AppHanggoogleearth.exe  version 5.0.11337.1968  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
4/9/2009        20:20   WERCON  FaultBkt        459652564,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
4/9/2009        20:15   WERCON  FaultBkt        456429236,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
4/9/2009        17:15   WERCON  FaultBkt        163094189,      [color=red]type 5[/color]
Event  Name:   CLR20r3
Response:        None
Cab Id:     0

Problem        signature:&#x00
4/9/2009        17:14   WERCON  FaultBkt        163094189,      [color=red]type 5[/color]
Event  Name:   CLR20r3
Response:        None
Cab Id:     0

Problem        signature:&#x00
4/5/2009        3:42    WERCON  FaultBkt        189584682,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
3/30/2009       22:26   WERCON  FaultBkt        186132981,      [color=red]type 5[/color]
Event  Name:   PnPGenericDriverFound
Response:  None
Cab Id:     0

Problem        signatu
3/28/2009       5:33    AppHangfirefox.exe      version 1.9.0.3334      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/28/2009       5:33    WERCON  FaultBkt        495991328,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
3/27/2009       23:27   WERCON  FaultBkt        473855672,      [color=red]type 5[/color]
Event  Name:   A1AntiVirus
Response:    None
Cab Id:     0

Problem        signature:&#x00
3/27/2009       23:27   WERCON  FaultBkt        473855672,      [color=red]type 5[/color]
Event  Name:   A1AntiVirus
Response:    None
Cab Id:     0

Problem        signature:&#x00
3/23/2009       19:46   AppHangfirefox.exe      version 1.9.0.3334      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/23/2009       19:46   WERCON  FaultBkt        498231126,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
3/23/2009       17:02   AppError        StarshipTycoon.exe,     version 1.0.0.0,        time    stamp   0x444d3a17,     faulting        module  StarshipTycoon.exe,     version 1.0.0.0,        time    stamp   0x444d3a17,     exception       code    0xc0000
3/22/2009       8:44    AppError        StarshipTycoon.exe,     version 1.0.0.0,        time    stamp   0x444d3a17,     faulting        module  StarshipTycoon.exe,     version 1.0.0.0,        time    stamp   0x444d3a17,     exception code [color=red]0xc0000005[/color]
3/15/2009       8:05    WERCON  FaultBkt        782055190,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
3/15/2009       8:04    AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.5.0,        time    stamp   0x4828f985,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
3/4/2009        4:42    AppHangfirefox.exe      version 1.9.0.3306      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/2/2009        19:57   AppError        NBJ.exe,        version 1.2.0.61,       time    stamp   0x434bf58b,     faulting        module  AdvrCntr.dll,   version 1.2.12.2315,    time    stamp   0x446e00c7,     exception code [color=red]0xc0000005[/color]00005[/color],
3/2/2009        19:57   WERCON  FaultBkt        316844832,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
3/2/2009        19:57   WERCON  FaultBkt        385691097,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
3/2/2009        6:12    AppHangfirefox.exe      version 1.9.0.3306      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/2/2009        6:12    WERCON  FaultBkt        463062223,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
3/1/2009        22:02   AppHangiexplore.exe     version 7.0.6001.18000  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/1/2009        22:02   WERCON  FaultBkt        299552587,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
3/1/2009        22:01   AppHangiexplore.exe     version 7.0.6001.18000  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/1/2009        22:01   WERCON  FaultBkt        320083374,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
3/1/2009        21:58   AppHangiexplore.exe     version 7.0.6001.18000  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/1/2009        21:58   WERCON  FaultBkt        224438472,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
2/25/2009       7:49    AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/21/2009       20:14   WERCON  FaultBkt        1123396486,     type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/21/2009       20:13   AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/20/2009       20:52   AppError        Sins    Developer.exe,  version 1.1.0.0,        time    stamp   0x492482ee,     faulting        module  Sins    Developer.exe,  version 1.1.0.0,        time    stamp   0x492482ee,     exception
2/20/2009       20:07   WERCON  FaultBkt        387526585,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
2/20/2009       20:04   AppError        Sins    Developer.exe,  version 1.1.0.0,        time    stamp   0x492482ee,     faulting        module  fmod.dll,       version 6.0.6001.18000, time    stamp   0x4791a7a6,     exception       code
2/20/2009       20:03   AppError        Sins    Developer.exe,  version 1.1.0.0,        time    stamp   0x492482ee,     faulting        module  fmod.dll,       version 6.0.6001.18000, time    stamp   0x4791a7a6,     exception       code
2/20/2009       20:02   AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/20/2009       20:02   WERCON  FaultBkt        1123396486,     type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/20/2009       20:01   AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/20/2009       20:01   AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/19/2009       21:27   WERCON  FaultBkt        376615861,      [color=red]type 5[/color]
Event  Name:   A1Sharing
Response:      None
Cab Id:     0

Problem        signature:&#x00
2/17/2009       8:07    AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/17/2009       4:34    AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/17/2009       4:34    WERCON  FaultBkt        1123396486,     type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/16/2009       5:48    AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/16/2009       4:37    AppError        Sins    of      a       Solar   Empire.exe,     version 1.1.3.0,        time    stamp   0x4980f116,     faulting        module  Sins    of      a       Solar   Empire.exe,
2/16/2009       4:37    WERCON  FaultBkt        1125640527,     type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/16/2009       3:39    WERCON  FaultBkt        1123396486,     type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/15/2009       6:46    WERCON  FaultBkt        1051121304,     type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/12/2009       13:56   WERCON  FaultBkt        25319269,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
2/9/2009        20:13   AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.5.0,        time    stamp   0x4828f985,     faulting        module  Sins    of      a       Solar   Empire.exe,
2/9/2009        20:13   WERCON  FaultBkt        995376148,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/8/2009        21:11   AppError        Sins_DEVELOPER.exe,     version 1.0.4.1,        time    stamp   0x482e3445,     faulting        module  Sins_DEVELOPER.exe,     version 1.0.4.1,        time    stamp   0x482e3445,     exception code [color=red]0xc0000005[/color]
2/8/2009        2:46    AppError        Sins_DEVELOPER.exe,     version 1.0.4.1,        time    stamp   0x482e3445,     faulting        module  Sins_DEVELOPER.exe,     version 1.0.4.1,        time    stamp   0x482e3445,     exception code [color=red]0xc0000005[/color]
2/6/2009        21:16   AppError        Sins_DEVELOPER.exe,     version 1.0.4.1,        time    stamp   0x482e3445,     faulting        module  Sins_DEVELOPER.exe,     version 1.0.4.1,        time    stamp   0x482e3445,     exception code [color=red]0xc0000005[/color]
2/6/2009        21:16   WERCON  FaultBkt        859667412,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/6/2009        6:06    WERCON  FaultBkt        448729681,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
2/6/2009        4:13    AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.5.0,        time    stamp   0x4828f985,     faulting        module  kernel32.dll,   version 6.0.6001.18000, time    stamp
2/5/2009        9:14    AppError        game.dat,       version 2.1.2614.37001, time    stamp   0x460da09e,     faulting        module  game.dat,       version 2.1.2614.37001, time    stamp   0x460da09e,     exception code [color=red]0xc0000005[/color]00005[/color],
2/5/2009        9:14    WERCON  FaultBkt        603781831,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/5/2009        9:13    WERCON  FaultBkt        603781831,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
2/5/2009        9:12    AppError        game.dat,       version 2.1.2614.37001, time    stamp   0x460da09e,     faulting        module  game.dat,       version 2.1.2614.37001, time    stamp   0x460da09e,     exception code [color=red]0xc0000005[/color]00005[/color],
2/2/2009        10:07   AppError        game.dat,       version 2.1.2614.37001, time    stamp   0x460da09e,     faulting        module  game.dat,       version 2.1.2614.37001, time    stamp   0x460da09e,     exception code [color=red]0xc0000005[/color]00005[/color],
1/31/2009       2:50    WERCON  FaultBkt        47472882,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
1/30/2009       8:25    WERCON  FaultBkt        9927949,        [color=red]type 5[/color]
Event  Name:   ApphelpSoftBlock
Response:       None
Cab Id:     0

Problem        signatu
1/29/2009       7:33    AppHangSims2EP8.exe     version 1.16.0.179      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
1/28/2009       14:30   AppHangSims2EP8.exe     version 1.16.0.179      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
1/27/2009       19:07   WERCON  FaultBkt        324250712,      [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     0

Problem        signature:
&#x00
10/27/2008      11:37WERCON     FaultBkt        598854563,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/27/2008      11:37AppError   Antwar.exe,     version 1.9.6.0,        time    stamp   0x2a425e19,     faulting        module  kernel32.dll,   version 6.0.6000.20608, time    stamp   0x465cf04b,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/27/2008      11:37AppError   Antwar.exe,     version 1.9.6.0,        time    stamp   0x2a425e19,     faulting        module  kernel32.dll,   version 6.0.6000.20608, time    stamp   0x465cf04b,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/27/2008      11:37AppError   antwar.exe,     version 1.9.6.0,        time    stamp   0x2a425e19,     faulting        module  kernel32.dll,   version 6.0.6000.20608, time    stamp   0x465cf04b,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/27/2008      11:35AppError   antwar.exe,     version 1.9.6.0,        time    stamp   0x2a425e19,     faulting        module  kernel32.dll,   version 6.0.6000.20608, time    stamp   0x465cf04b,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/27/2008      11:34WERCON     FaultBkt        598854563,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/27/2008      11:34AppError   antwar.exe,     version 1.9.6.0,        time    stamp   0x2a425e19,     faulting        module  kernel32.dll,   version 6.0.6000.20608, time    stamp   0x465cf04b,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/27/2008      11:34AppError   antwar.exe,     version 1.9.6.0,        time    stamp   0x2a425e19,     faulting        module  kernel32.dll,   version 6.0.6000.20608, time    stamp   0x465cf04b,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/27/2008      11:34AppError   antwar.exe,     version 1.9.6.0,        time    stamp   0x2a425e19,     faulting        module  kernel32.dll,   version 6.0.6000.20608, time    stamp   0x465cf04b,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/27/2008      5:20    AppError        CoD2SP_s.exe,   version 0.0.0.0,        time    stamp   0x00564544,     faulting        module  mss32.dll,      version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
10/27/2008      5:17    AppError        CoD2SP_s.exe,   version 0.0.0.0,        time    stamp   0x00564544,     faulting        module  mss32.dll,      version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
10/27/2008      5:06    WERCON  FaultBkt        5606589,        [color=red]type 5[/color]
Event  Name:   ApphelpHardBlock
Response:       http://oca.microsoft.com/resredir.aspx?SID=2274&iBucketTable=5&iBucket=5606589
&
10/27/2008      4:02    AppError        CoD2SP_s.exe,   version 0.0.0.0,        time    stamp   0x00564544,     faulting        module  mss32.dll,      version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
10/27/2008      4:02    WERCON  FaultBkt        347068082,      type    1
Event  Name:   APPCRASH
Response:       http://oca.microsoft.com/resredir.aspx?SID=9608&iBucketTable=1&iBucket=347068082
Cab     Id:    
10/25/2008      4:25    WERCON  FaultBkt        11913137,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
10/24/2008      21:03WERCON     FaultBkt        9097491,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/24/2008      20:56WERCON     FaultBkt        8171443,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/22/2008      23:10AppError   wmplayer.exe,   version 11.0.6000.6344, time    stamp   0x46e221bb,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/22/2008      10:49WERCON     FaultBkt        328463405,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/22/2008      10:42WERCON     FaultBkt        12447494,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/21/2008      4:09    WERCON  FaultBkt        977974911,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/21/2008      4:08    AppError        Profiler.exe,   version 2.6.0.37,       time    stamp   0x3d1aeec2,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/21/2008      3:18    WERCON  FaultBkt        371161381,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/21/2008      3:17    AppError        IDriver.exe,    version 8.0.0.123,      time    stamp   0x3d99b27a,     faulting        module  ntdll.dll,      version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception code [color=red]0xc0000005[/color]00005[/color],
10/21/2008      3:15    WERCON  FaultBkt        12447494,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/18/2008      5:00    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      5:00    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      5:00    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      5:00    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      5:00    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      4:59    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      4:58    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      0:25    WERCON  FaultBkt        328463405,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/18/2008      0:25    WERCON  FaultBkt        328463405,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/18/2008      0:24    WERCON  FaultBkt        328463405,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/18/2008      0:24    WERCON  FaultBkt        328463405,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/18/2008      0:24    WERCON  FaultBkt        328463405,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/18/2008      0:07    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
10/18/2008      0:07    WERCON  FaultBkt        345484752,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/17/2008      18:39WERCON     FaultBkt        345928319,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/17/2008      18:39AppError   DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/17/2008      18:35WERCON     FaultBkt        346090261,      type    1
Event  Name:   APPCRASH
Response:       http://oca.microsoft.com/resredir.aspx?SID=2570&iBucketTable=1&iBucket=346090261
Cab     Id:    
10/17/2008      18:35AppError   DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/17/2008      18:34WERCON     FaultBkt        347299490,      type    1
Event  Name:   APPCRASH
Response:       http://oca.microsoft.com/resredir.aspx?SID=2570&iBucketTable=1&iBucket=347299490
Cab     Id:    
10/17/2008      18:32WERCON     FaultBkt        346014269,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/17/2008      18:32AppError   DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/17/2008      18:32AppError   DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/17/2008      17:00WERCON     FaultBkt        8090646,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/17/2008      17:00WERCON     FaultBkt        494253473,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/17/2008      17:00AppError   DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/17/2008      16:59AppError   StarCraft.exe,  version 1.15.1.1,       time    stamp   0x469c04e9,     faulting        module  storm.dll,      version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,     fault
10/14/2008      18:35WERCON     FaultBkt        284555997,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
10/13/2008      22:38WERCON     FaultBkt        371161381,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/13/2008      22:38AppError   IDriver.exe,    version 8.0.0.123,      time    stamp   0x3d99b27a,     faulting        module  ntdll.dll,      version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/11/2008      15:08WERCON     FaultBkt        315993832,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
10/11/2008      13:26AppError   NBJ.exe,        version 1.2.0.61,       time    stamp   0x434bf58b,     faulting        module  AdvrCntr.dll,   version 1.2.12.2315,    time    stamp   0x446e00c7,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/11/2008      13:25WERCON     FaultBkt        0x7E_dxgkrnl!DxgkCddSetGammaRamp+f1,    type    0
Event  Name:   BlueScreen
Response:     http://oca.microsoft.com/resredir.aspx?sid=10&FailureId=0x7E_dxgkrnl!DxgkCddSetGammaRam
10/10/2008      10:01AppError   LGDCore.exe,    version 1.2.218.0,      time    stamp   0x440cc666,     faulting        module  LGDCore.exe,    version 1.2.218.0,      time    stamp   0x440cc666,     exception code [color=red]0xc0000005[/color]00005[/color],  fault
10/9/2008       20:50   WERCON  FaultBkt        300198893,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
10/9/2008       4:57    WERCON  FaultBkt        10,     [color=red]type 5[/color]
Event  Name:   NetworkDiagnosticsFramework
Response:    None
Cab Id:     0

Problem        signatu
10/9/2008       4:57    WERCON  FaultBkt        960888856,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
10/6/2008       14:29   AppError        Civ4Warlords.exe,       version 2.1.3.0,        time    stamp   0x464b927a,     faulting        module  MSVCR71.dll,    version 7.10.3052.4,    time    stamp   0x3e561eac,     exception code [color=red]0xc0000005[/color]00005[/c
10/6/2008       14:28   AppError        Civilization4.exe,      version 1.6.1.1841,     time    stamp   0x442bfe09,     faulting        module  binkw32.dll,    version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
10/6/2008       14:28   WERCON  FaultBkt        350236459,      type    1
Event  Name:   APPCRASH
Response:       http://oca.microsoft.com/resredir.aspx?SID=9608&iBucketTable=1&iBucket=350236459
Cab     Id:    
10/4/2008       0:41    WERCON  FaultBkt        116047181,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/4/2008       0:40    WERCON  FaultBkt        8090646,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/3/2008       1:40    WERCON  FaultBkt        269523703,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
10/2/2008       14:01   AppError        SporeApp.exe,   version 1.1.0.338,      time    stamp   0x00000000,     faulting        module  d3d9.dll,       version 6.0.6000.16386, time    stamp   0x4549bcc1,     exception code [color=red]0xc0000005[/color]00005[/color],
10/2/2008       1:38    AppError        SporeApp.exe,   version 1.1.0.338,      time    stamp   0x00000000,     faulting        module  d3d9.dll,       version 6.0.6000.16386, time    stamp   0x4549bcc1,     exception code [color=red]0xc0000005[/color]00005[/color],
10/1/2008       19:49   AppError        SporeApp.exe,   version 1.1.0.338,      time    stamp   0x00000000,     faulting        module  d3d9.dll,       version 6.0.6000.16386, time    stamp   0x4549bcc1,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       23:27   AppError        SporeApp.exe,   version 1.1.0.338,      time    stamp   0x00000000,     faulting        module  d3d9.dll,       version 6.0.6000.16386, time    stamp   0x4549bcc1,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       23:27   WERCON  FaultBkt        912423990,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/30/2008       20:00   AppError        SporeApp.exe,   version 1.1.0.338,      time    stamp   0x00000000,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       20:00   WERCON  FaultBkt        343866188,      [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     0

Problem        signature:
&#x00
9/30/2008       18:17   AppError        update2.exe,    version 1.0.0.0,        time    stamp   0x48ccc0e2,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:17   AppError        Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     faulting        module  Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:17   WERCON  FaultBkt        343789781,      [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     0

Problem        signature:
&#x00
9/30/2008       18:17   WERCON  FaultBkt        923727728,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/30/2008       18:12   AppError        update2.exe,    version 1.0.0.0,        time    stamp   0x48ccc0e2,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:12   AppError        Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     faulting        module  Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:12   WERCON  FaultBkt        343786071,      [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     0

Problem        signature:
&#x00
9/30/2008       18:12   WERCON  FaultBkt        923727728,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/30/2008       18:10   AppError        update2.exe,    version 1.0.0.0,        time    stamp   0x48ccc0e2,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:10   AppError        Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     faulting        module  Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:09   AppError        Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     faulting        module  Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:09   AppError        Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     faulting        module  Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:09   WERCON  FaultBkt        923727728,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/30/2008       18:09   WERCON  FaultBkt        923727728,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/30/2008       18:09   WERCON  FaultBkt        923727728,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/30/2008       18:09   WERCON  FaultBkt        331515069,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/30/2008       18:08   AppError        Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     faulting        module  Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:08   AppError        Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     faulting        module  Server.exe,     version 0.0.0.0,        time    stamp   0x48c81565,     exception code [color=red]0xc0000005[/color]00005[/color],
9/30/2008       18:08   WERCON  FaultBkt        923727728,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/30/2008       11:13   WERCON  FaultBkt        296197899,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/29/2008       15:59   AppHangSims2EP8.exe     version 1.16.0.179      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/29/2008       15:59   WERCON  FaultBkt        315868544,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/29/2008       15:52   AppHangSims2EP8.exe     version 1.16.0.179      stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/29/2008       15:52   WERCON  FaultBkt        315868544,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/29/2008       14:31   WERCON  FaultBkt        293596081,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
9/29/2008       14:12   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       14:09   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       14:07   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       14:06   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       14:06   WERCON  FaultBkt        10004662,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/29/2008       14:06   WERCON  FaultBkt        3678275,        [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     0

Problem        signature:
&#x00
9/29/2008       14:02   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       14:02   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       14:02   WERCON  FaultBkt        3678275,        [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     0

Problem        signature:
&#x00
9/29/2008       13:59   WERCON  FaultBkt        10384855,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/29/2008       13:40   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       13:39   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       13:36   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       13:36   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       13:36   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       13:36   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       13:36   WERCON  FaultBkt        10004662,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/29/2008       13:36   WERCON  FaultBkt        3678275,        [color=red]type 5[/color]
Event  Name:   BEX
Response:    None
Cab Id:     515450239

Problem        signature:&#x00
9/29/2008       13:35   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/29/2008       13:35   WERCON  FaultBkt        10384855,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/29/2008       13:34   AppError        swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     faulting        module  swkotor.exe,    version 1.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/28/2008       20:14   WERCON  FaultBkt        328604078,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/27/2008       16:11   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       16:08   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       16:06   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       16:06   WERCON  FaultBkt        901024544,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/27/2008       15:45   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       14:32   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       14:31   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       14:31   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       14:30   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       14:28   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       14:28   WERCON  FaultBkt        901024544,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/27/2008       14:24   WERCON  FaultBkt        901024544,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/27/2008       14:23   AppError        PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     faulting        module  PackageInstaller.exe,   version 1.16.0.179,     time    stamp   0x488b2b3f,     exception code [color=red]0xc0000005[/color]
9/27/2008       14:23   WERCON  FaultBkt        315440998,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/27/2008       13:59   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/27/2008       13:59   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/27/2008       13:59   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/27/2008       13:06   WERCON  FaultBkt        341044144,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/27/2008       13:06   WERCON  FaultBkt        126969522,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/23/2008       1:00    WERCON  FaultBkt        7988771,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/22/2008       17:32   WERCON  FaultBkt        95248792,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
9/22/2008       16:23   AppHangMagicISO.exe     version 5.4.0.251       stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/22/2008       16:23   WERCON  FaultBkt        337149941,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/21/2008       8:11    WERCON  FaultBkt        356515025,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/21/2008       8:10    AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/19/2008       17:46   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/19/2008       17:45   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/19/2008       17:36   WERCON  FaultBkt        81067151,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/19/2008       17:19   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/19/2008       17:18   WERCON  FaultBkt        167451127,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/19/2008       15:47   WERCON  FaultBkt        268872855,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/19/2008       12:49   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/19/2008       12:49   WERCON  FaultBkt        356515025,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/19/2008       12:05   AppError        swfoc.exe,      version 1.0.0.0,        time    stamp   0x4575fb3b,     faulting        module  swfoc.exe,      version 1.0.0.0,        time    stamp   0x4575fb3b,     exception code [color=red]0xc0000005[/color]00005[/color],
9/19/2008       11:26   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/19/2008       8:26    AppError        wmplayer.exe,   version 11.0.6000.6344, time    stamp   0x46e221bb,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception       code    0xc000001d,
9/19/2008       1:47    WERCON  FaultBkt        282721718,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/19/2008       1:44    AppError        LGDCore.exe,    version 1.2.218.0,      time    stamp   0x440cc666,     faulting        module  LGDCore.exe,    version 1.2.218.0,      time    stamp   0x440cc666,     exception code [color=red]0xc0000005[/color]00005[/color],
9/18/2008       17:05   AppHangexplorer.exe     version 6.0.6000.16549  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/18/2008       17:04   WERCON  FaultBkt        92257003,       [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/18/2008       17:02   AppHangExplorer.EXE     version 6.0.6000.16549  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/18/2008       17:02   WERCON  FaultBkt        92257003,       [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/18/2008       16:43   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       16:31   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       16:31   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       16:31   WERCON  FaultBkt        356515025,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/18/2008       16:22   WERCON  FaultBkt        356515025,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/18/2008       16:20   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       16:14   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       16:12   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       16:10   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       16:09   WERCON  FaultBkt        8147418,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/18/2008       15:42   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       15:42   WERCON  FaultBkt        356515025,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/18/2008       15:40   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       15:40   AppError        SWRepublicCommando.exe, version 0.0.0.0,        time    stamp   0x00000000,     faulting        module  gamespymgr.dll, version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception       code    0xc0000135,
9/18/2008       15:40   WERCON  FaultBkt        356515025,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/18/2008       15:39   WERCON  FaultBkt        166375858,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/17/2008       17:36   WERCON  FaultBkt        304601881,      [color=red]type 5[/color]
Event  Name:   A1Sharing
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/17/2008       12:48   AppError        wmplayer.exe,   version 11.0.6000.6344, time    stamp   0x46e221bb,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
9/17/2008       12:48   WERCON  FaultBkt        931921462,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/17/2008       9:12    WERCON  FaultBkt        8631927,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/16/2008       22:19   AppError        PackageInstaller.exe,   version 1.6.0.277,      time    stamp   0x45f1f35e,     faulting        module  PackageInstaller.exe,   version 1.6.0.277,      time    stamp   0x45f1f35e,     exception code [color=red]0xc0000005[/color]
9/16/2008       22:19   WERCON  FaultBkt        400246651,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/16/2008       22:16   WERCON  FaultBkt        24065186,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/16/2008       22:16   WERCON  FaultBkt        24065186,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/15/2008       16:02   AppError        swfoc.exe,      version 1.0.0.0,        time    stamp   0x4575fb3b,     faulting        module  d3d9.dll,       version 6.0.6000.16386, time    stamp   0x4549bcc1,     exception code [color=red]0xc0000005[/color]00005[/color],
9/15/2008       2:17    AppError        swfoc.exe,      version 1.0.0.0,        time    stamp   0x4575fb3b,     faulting        module  swfoc.exe,      version 1.0.0.0,        time    stamp   0x4575fb3b,     exception code [color=red]0xc0000005[/color]00005[/color],
9/15/2008       2:17    WERCON  FaultBkt        380200772,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/14/2008       14:40   AppError        focupdate1_1.exe,       version 1.0.1.3,        time    stamp   0x456e183b,     faulting        module  focupdate1_1.exe,       version 1.0.1.3,        time    stamp   0x456e183b,     exception code [color=red]0xc0000005[/color]
9/14/2008       14:40   WERCON  FaultBkt        361456214,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/14/2008       1:23    WERCON  FaultBkt        313001310,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
9/14/2008       0:39    WERCON  FaultBkt        264624606,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/14/2008       0:24    WERCON  FaultBkt        261971194,      [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/12/2008       21:18   AppError        swfoc.exe,      version 1.0.0.0,        time    stamp   0x4575fb3b,     faulting        module  swfoc.exe,      version 1.0.0.0,        time    stamp   0x4575fb3b,     exception code [color=red]0xc0000005[/color]00005[/color],
9/12/2008       21:18   WERCON  FaultBkt        432496721,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/11/2008       9:20    AppError        iexplore.exe,   version 7.0.6000.16711, time    stamp   0x486445ce,     faulting        module  mshtml.dll,     version 7.0.6000.16711, time    stamp   0x48646405,     exception code [color=red]0xc0000005[/color]00005[/color],
9/11/2008       9:20    WERCON  FaultBkt        882585428,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/11/2008       0:31    WERCON  FaultBkt        11679774,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
9/10/2008       10:09   WERCON  FaultBkt        11759458,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
9/9/2008        17:28   WERCON  FaultBkt        325954686,      [color=red]type 5[/color]
Event  Name:   AVSubmit
Response:       None
Cab Id:     508561091

Problem        signatu
9/8/2008        3:45    WERCON  FaultBkt        56291011,       [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
9/8/2008        3:23    AppHangiexplore.exe     version 7.0.6000.16711  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/8/2008        3:23    WERCON  FaultBkt        304839703,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/8/2008        3:20    AppError        regsvr32.exe,   version 6.0.6000.16386, time    stamp   0x4549b3c7,     faulting        module  ntdll.dll,      version 6.0.6000.16386, time    stamp   0x4549bdc9,     exception code [color=red]0xc0000005[/color]00005[/color],
9/8/2008        3:20    WERCON  FaultBkt        362073930,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
9/7/2008        13:15   AppHangWMCodec_updates.exe      version 1.0.0.1 stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/7/2008        13:15   WERCON  FaultBkt        325002596,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/7/2008        13:13   AppHang2.exe    version 0.0.0.0 stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
9/7/2008        13:13   WERCON  FaultBkt        323466714,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
9/6/2008        17:24   WERCON  FaultBkt        385691097,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
8/31/2008       21:07   AppError        focupdate1_1.exe,       version 1.0.1.3,        time    stamp   0x456e183b,     faulting        module  focupdate1_1.exe,       version 1.0.1.3,        time    stamp   0x456e183b,     exception code [color=red]0xc0000005[/color]
8/31/2008       21:07   WERCON  FaultBkt        361456214,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
8/29/2008       19:45   AppHangSins     of      a       Solar   Empire.exe      version 1.0.5.0 stopped interacting     with    Windows and     was     closed. To      see     if      more
8/29/2008       19:45   WERCON  FaultBkt        247575541,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
8/27/2008       21:05   AppHangExplorer.EXE     version 6.0.6000.16549  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
8/26/2008       15:44   WERCON  FaultBkt        12058509,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
8/25/2008       19:58   AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.5.0,        time    stamp   0x4828f985,     faulting        module  Sins    of      a       Solar   Empire.exe,
8/25/2008       19:58   WERCON  FaultBkt        770392579,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
8/25/2008       19:55   AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.5.0,        time    stamp   0x4828f985,     faulting        module  Sins    of      a       Solar   Empire.exe,
8/25/2008       19:55   WERCON  FaultBkt        770392579,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
8/25/2008       16:31   WERCON  FaultBkt        11825068,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
8/25/2008       16:06   WERCON  FaultBkt        8716933,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
8/25/2008       16:05   WERCON  FaultBkt        5603960,        [color=red]type 5[/color]
Event  Name:   ApphelpSoftBlock
Response:       http://oca.microsoft.com/resredir.aspx?SID=2781&iBucketTable=5&iBucket=5603960&Cab=D5E8
8/17/2008       1:01    AppHangSins     of      a       Solar   Empire.exe      version 1.0.5.0 stopped interacting     with    Windows and     was     closed. To      see     if      more
8/17/2008       1:01    WERCON  FaultBkt        250549898,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
8/12/2008       13:34   WERCON  FaultBkt        12106702,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
8/11/2008       17:01   AppError        NBJ.exe,        version 1.2.0.61,       time    stamp   0x434bf58b,     faulting        module  AdvrCntr.dll,   version 1.2.12.2315,    time    stamp   0x446e00c7,     exception code [color=red]0xc0000005[/color]00005[/color],
8/9/2008        7:31    WERCON  FaultBkt        276814561,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
8/8/2008        7:07    WERCON  FaultBkt        8265292,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
8/6/2008        7:07    WERCON  FaultBkt        8265292,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
8/4/2008        19:14   WERCON  FaultBkt        187591189,      [color=red]type 5[/color]
Event  Name:   PnPGenericDriverFound
Response:  None
Cab Id:     0

Problem        signatu
7/22/2008       7:01    WERCON  FaultBkt        8265292,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
7/22/2008       6:07    AppHangexplorer.exe     version 6.0.6000.16549  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
7/22/2008       6:07    WERCON  FaultBkt        91510491,       [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
7/22/2008       3:49    AppHangExplorer.EXE     version 6.0.6000.16549  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
7/22/2008       3:49    WERCON  FaultBkt        91510491,       [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
7/21/2008       5:54    AppError        iexplore.exe,   version 7.0.6000.16681, time    stamp   0x48113d17,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
7/21/2008       5:54    WERCON  FaultBkt        785464315,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
7/20/2008       22:43   WERCON  FaultBkt        346763336,      type    1
Event  Name:   APPCRASH
Response:       http://oca.microsoft.com/resredir.aspx?SID=2570&iBucketTable=1&iBucket=346763336
Cab     Id:    
7/20/2008       22:42   AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
7/14/2008       6:31    WERCON  FaultBkt        8265292,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
7/6/2008        7:25    WERCON  FaultBkt        8171590,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
7/1/2008        14:33   WERCON  FaultBkt        12023912,       [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
6/27/2008       3:55    WERCON  FaultBkt        562478443,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
6/27/2008       3:54    AppError        msnmsgr.exe,    version 8.5.1302.1018,  time    stamp   0x4717a53b,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
6/27/2008       3:52    AppError        msnmsgr.exe,    version 8.5.1302.1018,  time    stamp   0x4717a53b,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
6/26/2008       17:25   AppError        msnmsgr.exe,    version 8.5.1302.1018,  time    stamp   0x4717a53b,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
6/26/2008       17:25   WERCON  FaultBkt        587404486,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
6/25/2008       10:20   AppError        msnmsgr.exe,    version 8.5.1302.1018,  time    stamp   0x4717a53b,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
6/25/2008       10:20   WERCON  FaultBkt        562092584,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
6/25/2008       10:19   AppError        msnmsgr.exe,    version 8.5.1302.1018,  time    stamp   0x4717a53b,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
6/25/2008       10:19   WERCON  FaultBkt        574297136,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
6/24/2008       7:23    WERCON  FaultBkt        8422807,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
6/21/2008       21:41   WERCON  FaultBkt        187591189,      [color=red]type 5[/color]
Event  Name:   PnPGenericDriverFound
Response:  None
Cab Id:     0

Problem        signatu
6/13/2008       7:20    WERCON  FaultBkt        8168213,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
6/12/2008       10:56   AppError        Ventrilo.exe,   version 3.0.1.0,        time    stamp   0x473f5606,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
6/12/2008       10:56   WERCON  FaultBkt        571061920,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
6/11/2008       20:52   AppHangiexplore.exe     version 7.0.6000.16643  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
6/11/2008       20:52   WERCON  FaultBkt        211605043,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
6/10/2008       1:36    AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.4.0,        time    stamp   0x47fc2506,     faulting        module  Sins    of      a       Solar   Empire.exe,
6/9/2008        3:52    AppError        iexplore.exe,   version 7.0.6000.16643, time    stamp   0x47bce1b0,     faulting        module  Flash9d.ocx,    version 9.0.47.0,       time    stamp   0x466daac0,     exception code [color=red]0xc0000005[/color]00005[/color],
6/9/2008        3:52    WERCON  FaultBkt        689011875,      type    1
Event  Name:   APPCRASH
Response:       http://oca.microsoft.com/resredir.aspx?SID=2349&iBucketTable=1&iBucket=689011875
Cab     Id:    
6/6/2008        19:28   WERCON  FaultBkt        228347563,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
6/4/2008        7:27    WERCON  FaultBkt        8168213,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
6/1/2008        6:56    AppError        wmplayer.exe,   version 11.0.6000.6344, time    stamp   0x46e221bb,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
6/1/2008        6:56    WERCON  FaultBkt        585186291,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
5/27/2008       17:20   AppError        LGDCore.exe,    version 1.2.218.0,      time    stamp   0x440cc666,     faulting        module  LGDCore.exe,    version 1.2.218.0,      time    stamp   0x440cc666,     exception code [color=red]0xc0000005[/color]00005[/color],
5/22/2008       19:26   AppHangiexplore.exe     version 7.0.6000.16643  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
5/22/2008       18:27   AppHangiexplore.exe     version 7.0.6000.16643  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
5/22/2008       18:27   WERCON  FaultBkt        211346962,      [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
5/14/2008       6:59    WERCON  FaultBkt        8168213,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
5/8/2008        0:01    AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.4.0,        time    stamp   0x47fc2506,     faulting        module  Sins    of      a       Solar   Empire.exe,
5/6/2008        12:56   WERCON  FaultBkt        343718045,      type    1
Event  Name:   APPCRASH
Response:       http://oca.microsoft.com/resredir.aspx?SID=2570&iBucketTable=1&iBucket=343718045
Cab     Id:    
5/6/2008        12:55   AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
5/2/2008        6:53    WERCON  FaultBkt        8168213,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
5/1/2008        20:53   AppError        Sins    of      a       Solar   Empire.exe,     version 1.0.4.0,        time    stamp   0x47fc2506,     faulting        module  Sins    of      a       Solar   Empire.exe,
5/1/2008        20:53   WERCON  FaultBkt        718015965,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
4/30/2008       6:53    WERCON  FaultBkt        8168213,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
4/15/2008       17:09   WERCON  FaultBkt        181837692,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
4/12/2008       7:14    WERCON  FaultBkt        8168213,        [color=red]type 5[/color]
Event  Name:   MpTelemetry
Response:    None
Cab Id:     0

Problem        signature:&#x00
4/10/2008       9:44    WERCON  FaultBkt        346125662,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
4/10/2008       9:43    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
4/10/2008       9:43    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
4/10/2008       9:43    WERCON  FaultBkt        343774943,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
4/10/2008       9:43    WERCON  FaultBkt        343319423,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
4/10/2008       9:42    AppError        DllHost.exe,    version 6.0.6000.16386, time    stamp   0x4549b14e,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
4/3/2008        21:29   AppError        ProfilerU.exe,  version 4.3.3.2059,     time    stamp   0x4354f9cd,     faulting        module  unknown,        version 0.0.0.0,        time    stamp   0x00000000,     exception code [color=red]0xc0000005[/color]00005[/color],
4/3/2008        21:29   WERCON  FaultBkt        709216978,      type    1
Event  Name:   APPCRASH
Response:       None
Cab Id:     0

Problem        signature:
P1:  
3/31/2008       2:39    AppHangExplorer.EXE     version 6.0.6000.16549  stopped interacting     with    Windows and     was     closed. To      see     if      more    information     about   the     problem
3/31/2008       2:38    WERCON  FaultBkt        91893597,       [color=red]type 5[/color]
Event  Name:   AppHangB1
Response:      None
Cab Id:     0

Problem        signature:&#x00
3/30/2008       21:55   WERCON  FaultBkt        127976949,      [color=red]type 5[/color]
Event  Name:   RADAR_PRE_LEAK_32
Response:      None
Cab Id:     0

Problem        signatu
3/30/2008       21:36   WERCON  FaultBkt        8456108,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
3/30/2008       21:29   WERCON  FaultBkt        7988771,        [color=red]type 5[/color]
Event  Name:   PCA2
Response:   None
Cab Id:     0

Problem        signature:
&#x00
[/font]
SCROLL TO THE RIGHT


I often see the 0xc..5 exception codes associated with a 3rd party firewall included in an Internet Security program. I found an old installation of Norton Internet Security and Windows Live One Care.

I noticed this driver that I was unable to find out much about -
Code:
TSHWMDTCP    TSHWMDTCP              TSHWMDTCP              File System   Manual     Stopped    OK         FALSE       FALSE        0          4,096      0     
 3/7/2007 1:56:38 AM    
\??\C:\Program Files\Intel\IntelDH\Intel Media S 4,096
Then entries like this -
Code:
The application (StarForce Protection, from vendor StarForce) has the
 following problem: The installed StarForce Protection driver is not compatible
 with this version of Windows and will be disabled.  Applications that require 
this driver will not function properly without a patch.

And the mouse - drivers from 2005 -
Code:
Saitek Magic Bus	No	SAITEK MAGIC BUS	5.5.0.82	11/3/2005	Saitek	oem44.inf	Not Available	ROOT\SAITEK_MAGIC_BUS\0000
Saitek Magic Keyboard	No	SAITEK MAGIC BUS	5.5.0.82	11/3/2005	Saitek	oem44.inf	Not Available	SAITEKMAGICBUS\SAITEKKEYBOARD\1&A2CA95B&0&0000
Saitek Magic Mouse	No	SAITEK MAGIC BUS	5.5.0.82	11/3/2005	Saitek	oem44.inf	Not Available	SAITEKMAGICBUS\SAITEKMOUSE\1&A2CA95B&0&0000

I can say without hesitation that if this were my system, I would re-install vista and start fresh. I suggest that you do the same. I noticed a recovery partition - 15GB drive d: should be it. Be sure to back up all personal files. I would leave the P2P app off the to-do list in the future.

Regards. . .

jcgriff2

.
 

·
Registered
Joined
·
186 Posts
Discussion Starter #13
Re: Various Vista Problems

Righto... pardon the resurrection of my thread, but I've finally got my computer working again, and have decided to enlist the help of this forum again.

Updates since my last problem, my hard-drive had some sort of catastrophic failure, and we couldn't get it working until we wiped it clean from another computer. I'm trying to install XP now, but I can't seem to manage it. Despite having a completely clean hard-drive, the only thing I can install on it seems to be Vista, which is not logical; I have read multiple accounts of people switching the exact computer I have to XP. So, in short, I would like some help with my specific problem, if I could get any.

Many thanks in advance!
 

·
Microsoft-Team Manager , Hardware - Team Manager
Joined
·
68,454 Posts
Re: Various Vista Problems

Hi is the hdd your trying to install ide or sata if sata you may need a driver to be installed,the F6 option during install of xp
 

·
Registered
Joined
·
186 Posts
Discussion Starter #15
Re: Various Vista Problems

I'm fairly certain it's SATA, though how would I check to be certain?

And assuming it is, what driver do I need installed? I assume I need to put said driver on an external disk or hard drive?
 

·
Microsoft-Team Manager , Hardware - Team Manager
Joined
·
68,454 Posts
Re: Various Vista Problems

Hi check out the makers site and see what is available for your machine you may need to use a floppy or disc
 

·
Registered
Joined
·
186 Posts
Discussion Starter #17
Re: Various Vista Problems

Alright, so, I downloaded that driver onto a CD disk. I've tried a couple of things, but I can't seem to get it to do anything in the boot up- unless I have an OS disk in the drive, it tells me the BOOTMGR is missing. I don't have two disk drives on this computer, so I'm a bit limited.

During the bootup for XP though, when asked to press F6 I did so, and I did get further in the process than usual- I was asked if I had a separate disk for something or other (I can replicate it if needed), but putting the disk in didn't seem to let me use it. I got to the end of the process after continuing, and it said 'Setup is starting windows' and then I got a blue screen that informed me Windows had shut down to prevent system damage.

I'm using a Windows XP Professional SP1 disk, just so it's known.
 

·
Registered
Joined
·
186 Posts
Discussion Starter #19
Re: Various Vista Problems

The drivers asked for when I get the F6 prompt are for SCSI or RAID drivers, which I don't believe are on the disk- this can easily be remedied of course, but, when I press F6, I don't get any sort of additional prompt until much later in the installation, when it asks me if I want to find additional floppy drives etc, which I have none of. Inserting the disk at this point doesn't seem to have any effect.
 

·
Registered
Joined
·
1 Posts
Re: Various Vista Problems

I don't think you need to press F6 for SATA drives. Like you stated above, F6 is for SCSCI or RAID drives. I'm running 64bit Vista and didn't have a problem getting it to recognize my SATA drives without drivers.

How about updating ur motherboard's BIOS?
 
1 - 20 of 26 Posts
Status
Not open for further replies.
Top