Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: Oogly50 on August 14, 2007, 03:10:30 PM

Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 14, 2007, 03:10:30 PM
Okay... for 2 months or so, I have kept getting a blue screen after playing ANY game online.  I tried updating my video driver...  which didn't help.

But recently, I noticed something that said.

the following file is corrupt (or something along those lines): USBPORT.EXE (or SYS)  

So I'm wondering, and I'm pretty sure, that the problem is with my USB PORT?

If so, what's wrong with it?  Do I need to smash it?  because, believe me, I will.  



Thanks in advance for anybody who helps me with this :(  :aok  :huh :cry :rolleyes: :(
Title: Re: BSOD (blue screen of despair)
Post by: Wes14 on August 14, 2007, 07:56:22 PM
Quote
Originally posted by Oogly50
USBPORT.EXE (or SYS)


you mean USBPORT.SYS or SYS.EXE?

cause i dont think the usb port runs as a EXE file(or a SYS file).. might want to run a good virus scan or something if its what i think it is.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 14, 2007, 08:15:56 PM
that's what I do...  about once every week.  

And yea, whatever you said.  USBPORT.SYS

Why, what do you think it is?







Actually, I usually run spyware scans...  what would you reccomend as a free decent virus scanner?
Title: BSOD (blue screen of despair)
Post by: Scca on August 15, 2007, 07:03:23 AM
Quote
Originally posted by Oogly50
that's what I do...  about once every week.  

And yea, whatever you said.  USBPORT.SYS

Why, what do you think it is?







Actually, I usually run spyware scans...  what would you reccomend as a free decent virus scanner?

I use AVG free edition for anti virus.  It's free, works and is better than some of the big names (norton for one).

For spyware try Spybot, for ad ware try AdAware.  Both are free and do a good job.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 09:23:12 AM
lol!  just found out I had AVG free edition and I already used ad-aware for ad ware.

I have a few tracking cookies, but other than that my ad ware search came up clean.  Along with my virus search.  

As for spybot...  I'll try it out.  

I'll edit this post when I'm done.

EDIT: Scan done running, 60 something threats, all fixed...  should I attempt aces high?
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 11:00:56 AM
okay, so I played aces high again after running the scans.

I got the blue screen, however, I took the 10 minutes to write down EVERYTHING it said.  

Here it goes :mad:



A problem has been detected and windows has been shut down to prevent damage.

Check to be sure you have adequate disk space.  If a driver is identified in the stop message, disable the driver or check with the manufacturer for driver updates.  Try changing video adapters.  

Check with your hardware vendor for any BIOS updates.  Disable BIOS memory options such as caching or shadowing.  

Tecnical info:

*** STOP: 0x0000007E   (xc0000005, 0xEE59E078, 0xEE669BA8, 0xEE6698A4)

*** kmiersys - Adress EE59Eo78 base at EE59f 000, datestamp448fod31



I have updated my video driver, and by disk space, would this mean RAM?  if so, my RAm is only 256, which, for a long while... I believed was the problem.    

thanks in advance... again :aok
Title: BSOD (blue screen of despair)
Post by: Krusty on August 15, 2007, 11:39:33 AM
I think we're going to need a DXDIAG report. List the first 1/3 or so (all the hardware) for us, if you can.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 11:42:03 AM
------------------
System Information
------------------
Time of this report: 7/24/2007, 15:03:44
       Machine name: FAMILY
   Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
           Language: English (Regional Setting: English)
System Manufacturer: VIA Technologies, Inc.
       System Model: KM266PRO-8235
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: AMD Athlon(tm) XP 2800+,  MMX,  3DNow, ~2.1GHz
             Memory: 256MB RAM
          Page File: 247MB used, 356MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.2180 32bit Unicode

------------
DxDiag Notes
------------
  DirectX Files Tab: No problems found.
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
          Music Tab: No problems found.
          Input Tab: No problems found.
        Network Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (n/a)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
        Card name: SAPPHIRE RADEON 9200SE ATLANTIS 128MB
     Manufacturer: ATI Technologies Inc.
        Chip type: RADEON 9200 SE AGP (0x5964)
         DAC type: Internal DAC(500MHz)
       Device Key: Enum\PCI\VEN_1002&DEV_5964&SUBSYS_7C26174B&REV_01
   Display Memory: 128.0 MB
     Current Mode: 1152 x 864 (16 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: ati2dvag.dll
   Driver Version: 6.14.0010.6476 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 8/25/2004 13:29:04, 209408 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: ati2mtag.sys
    Mini VDD Date: 8/25/2004 13:28:46, 787456 bytes
Device Identifier: {D7B71EE2-1A24-11CF-B76D-2C5CA0C2CB35}
        Vendor ID: 0x1002
        Device ID: 0x5964
        SubSys ID: 0x7C26174B
      Revision ID: 0x0001
      Revision ID: 0x0001
      Video Accel: ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
         Registry: OK
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled
DDraw Test Result: Not run
 D3D7 Test Result: Not run
 D3D8 Test Result: Not run
 D3D9 Test Result: Not run

-------------
Sound Devices
-------------
            Description: Vinyl AC'97 Audio (WAVE)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1106&DEV_3059&SUBSYS_417016F3&REV_50
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: vinyl97.sys
         Driver Version: 6.14.0001.4070 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 9/6/2004 16:01:56, 161536 bytes
            Other Files:
        Driver Provider: VIA Technologies, Inc.
         HW Accel Level: Basic
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 8000, 96000
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 11:44:41 AM
---------------------
Sound Capture Devices
---------------------
            Description: Vinyl AC'97 Audio (WAVE)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: vinyl97.sys
         Driver Version: 6.14.0001.4070 (English)
      Driver Attributes: Final Retail
          Date and Size: 9/6/2004 16:01:56, 161536 bytes
              Cap Flags: 0x41
           Format Flags: 0xFFF

-----------
DirectMusic
-----------
        DLS Path: C:\WINDOWS\system32\drivers\gm.dls
     DLS Version: 1.00.0016.0002
    Acceleration: n/a
           Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
                  Vinyl AC'97 Audio (WAVE), Software (Kernel Mode), Output, DLS, Internal
                  Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
        Registry: OK
     Test Result: Not run

-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Gateway USB Hub Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x0443, 0x002E
        FF Driver: n/a

      Device Name: Gateway USB Hub Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x0443, 0x002E
        FF Driver: n/a

      Device Name: Gateway USB Hub Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x0443, 0x002E
        FF Driver: n/a

      Device Name: 3-axis, 4-button joystick
         Attached: 0
    Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0108
        FF Driver: n/a

      Device Name: Logitech Extreme 3D
         Attached: 1
    Controller ID: 0x1
Vendor/Product ID: 0x046D, 0xC215
        FF Driver: n/a

Poll w/ Interrupt: No
         Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x1106, 0x3038
| Matching Device ID: usb\root_hub
| Lower Filters: vulfntrs
| Service: usbhub
| Driver: usbhub.sys, 8/4/2004 01:08:42, 57600 bytes
| Driver: usbd.sys, 8/29/2002 12:00:00, 4736 bytes

----------------
Gameport Devices
----------------
+ PCI bus
| Matching Device ID: *pnp0a03
| Service: pci
| Driver: pci.sys, 8/4/2004 01:07:46, 68224 bytes
|
+-+ Standard Game Port
| | Matching Device ID: *pnpb02f
| | Service: gameenum
| | Driver: gameenum.sys, 8/4/2004 01:08:22, 10624 bytes
| |
| +-+ 3-axis, 4-button joystick
| | | Vendor/Product ID: 0x045E, 0x0108
| | | Matching Device ID: gameport\vid_045e&pid_0108
| | | Service: hidgame
| | | Driver: hidclass.sys, 8/4/2004 01:08:20, 36224 bytes
| | | Driver: hidparse.sys, 8/4/2004 01:08:16, 24960 bytes
| | | Driver: hid.dll, 8/4/2004 02:56:42, 20992 bytes
| | | Driver: hidgame.sys, 8/17/2001 14:02:32, 8576 bytes
| | |
| | +-+ HID-compliant game controller
| | | | Vendor/Product ID: 0x045E, 0x0108
| | | | Matching Device ID: hid_device_system_game

------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x0443, 0x002E
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 8/4/2004 00:58:34, 14848 bytes
| Driver: kbdclass.sys, 8/4/2004 00:58:32, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 03:01:08, 40840 bytes
| Driver: kbdclass.sys, 8/4/2004 00:58:32, 24576 bytes
|
+ HID-compliant Wheel Mouse
| Vendor/Product ID: 0x046D, 0xC03F
| Matching Device ID: hid\vid_046d&pid_c03f
| Upper Filters: LMouFlt2
| Lower Filters: LHidFlt2
| Service: mouhid
| Driver: mouhid.sys, 8/17/2001 13:48:00, 12160 bytes
| Driver: mouclass.sys, 8/4/2004 00:58:32, 23040 bytes
| Driver: LHidFlt2.Sys, 11/7/2003 03:50:00, 25502 bytes
| Driver: LMouFlt2.Sys, 11/7/2003 03:50:00, 70798 bytes
| Driver: Logi_MwX.Exe, 11/7/2003 03:50:00, 19968 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 03:01:08, 40840 bytes
| Driver: mouclass.sys, 8/4/2004 00:58:32, 23040 bytes

----------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)

DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK

-------------------
DirectPlay Adapters
-------------------
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 Serial Service Provider: COM2
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -

-----------------------
DirectPlay Voice Codecs
-----------------------
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s

-------------------------
DirectPlay Lobbyable Apps
-------------------------

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 7.4 GB
Total Space: 38.2 GB
File System: FAT32
      Model: n/a

      Drive: D:
      Model: LITE-ON LTR-24102B
     Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/4/2004 00:59:52, 49536 bytes
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 11:46:08 AM
--------------
System Devices
--------------
     Name: VIA CPU to AGP Controller
Device ID: PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_00\3&61AAA01&0&08
   Driver: n/a

     Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1106&DEV_3205&SUBSYS_00000000&REV_00\3&61AAA01&0&00
   Driver: n/a

     Name: PCI standard ISA bridge
Device ID: PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61AAA01&0&88
   Driver: C:\WINDOWS\system32\DRIVERS\isapnp.sys, 5.01.2600.0000 (English), 8/29/2002 12:00:00, 35840 bytes

     Name: VIA USB 2.0 Enhanced Host Controller
Device ID: PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_82\3&61AAA01&0&83
   Driver: C:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 26624 bytes
   Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 142976 bytes
   Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:46, 74240 bytes
   Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 57600 bytes
   Driver: C:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:42, 7168 bytes

     Name: VIA Rhine II Fast Ethernet Adapter
Device ID: PCI\VEN_1106&DEV_3065&SUBSYS_01021106&REV_74\3&61AAA01&0&90
   Driver: C:\WINDOWS\system32\DRIVERS\fetnd5bv.sys, 3.43.0000.0428 (English), 1/28/2005 13:57:52, 42496 bytes
   Driver: C:\WINDOWS\system32\vuins32.dll, 1.04.0000.0009 (English), 9/17/2004 17:37:42, 61440 bytes

     Name: Vinyl AC'97 Codec Combo Driver (WDM)
Device ID: PCI\VEN_1106&DEV_3059&SUBSYS_417016F3&REV_50\3&61AAA01&0&8D
   Driver: C:\WINDOWS\system32\ksuser.dll, 5.03.2600.2180 (English), 8/4/2004 02:56:42, 4096 bytes
   Driver: C:\WINDOWS\system32\ksproxy.ax, 5.03.2600.2180 (English), 8/4/2004 02:56:58, 130048 bytes
   Driver: C:\WINDOWS\system32\drivers\ks.sys, 5.03.2600.2180 (English), 8/4/2004 01:15:22, 140928 bytes
   Driver: C:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.2180 (English), 8/4/2004 01:07:58, 60288 bytes
   Driver: C:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.2180 (English), 8/4/2004 01:15:50, 145792 bytes
   Driver: C:\WINDOWS\system32\drivers\stream.sys, 5.03.2600.2180 (English), 8/4/2004 01:08:02, 48640 bytes
   Driver: C:\WINDOWS\system32\wdmaud.drv, 5.01.2600.2180 (English), 8/4/2004 02:56:58, 23552 bytes
   Driver: C:\WINDOWS\system32\drivers\vinyl97.sys, 6.14.0001.4070 (English), 9/6/2004 16:01:56, 161536 bytes

     Name: VIA Rev 5 or later USB Universal Host Controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_80\3&61AAA01&0&82
   Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 20480 bytes
   Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 142976 bytes
   Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:46, 74240 bytes
   Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 57600 bytes

     Name: VIA Rev 5 or later USB Universal Host Controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_80\3&61AAA01&0&81
   Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 20480 bytes
   Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 142976 bytes
   Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:46, 74240 bytes
   Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 57600 bytes

     Name: VIA Rev 5 or later USB Universal Host Controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_80\3&61AAA01&0&80
   Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:38, 20480 bytes
   Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 142976 bytes
   Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 02:56:46, 74240 bytes
   Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/4/2004 01:08:42, 57600 bytes

     Name: VIA Bus Master IDE Controller
Device ID: PCI\VEN_1106&DEV_0571&SUBSYS_05711106&REV_06\3&61AAA01&0&89
   Driver: C:\WINDOWS\system32\DRIVERS\viaide.sys, 1.00.0001.0001 (English), 8/4/2004 00:59:42, 5376 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (English), 8/4/2004 00:59:42, 25088 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/4/2004 00:59:42, 95360 bytes

     Name: SAPPHIRE RADEON 9200SE ATLANTIS 128MB - Secondary
Device ID: PCI\VEN_1002&DEV_5D44&SUBSYS_7C27174B&REV_01\4&1FEB96E4&0&0108
   Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6476 (English), 8/25/2004 13:28:46, 787456 bytes
   Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6476 (English), 8/25/2004 13:29:04, 209408 bytes
   Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0252 (English), 8/25/2004 13:10:20, 237568 bytes
   Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2494 (English), 8/25/2004 13:27:08, 65536 bytes
   Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0257 (English), 8/25/2004 13:25:56, 2239328 bytes
   Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0001.0029 (English), 8/25/2004 13:15:16, 476928 bytes
   Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0005 (English), 8/25/2004 13:26:32, 81920 bytes
   Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4100 (English), 8/25/2004 13:12:10, 17408 bytes
   Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/8/2001 21:01:04, 24064 bytes
   Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4105 (English), 8/25/2004 13:26:56, 389120 bytes
   Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4105 (English), 8/25/2004 13:27:00, 86016 bytes
   Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2491 (English), 8/25/2004 13:27:18, 126976 bytes
   Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0010 (English), 8/25/2004 13:27:12, 102400 bytes
   Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2494 (English), 8/25/2004 13:27:04, 30720 bytes
   Driver: C:\WINDOWS\system32\ATIDEMGR.dll, 1.00.1698.24059 (English), 8/25/2004 14:22:08, 151552 bytes
   Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.4582 (English), 8/25/2004 13:48:12, 6508544 bytes
   Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4003 (English), 8/25/2004 14:40:02, 294912 bytes

     Name: SAPPHIRE RADEON 9200SE ATLANTIS 128MB
Device ID: PCI\VEN_1002&DEV_5964&SUBSYS_7C26174B&REV_01\4&1FEB96E4&0&0008
   Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6476 (English), 8/25/2004 13:28:46, 787456 bytes
   Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6476 (English), 8/25/2004 13:29:04, 209408 bytes
   Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0252 (English), 8/25/2004 13:10:20, 237568 bytes
   Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2494 (English), 8/25/2004 13:27:08, 65536 bytes
   Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0257 (English), 8/25/2004 13:25:56, 2239328 bytes
   Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0001.0029 (English), 8/25/2004 13:15:16, 476928 bytes
   Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0005 (English), 8/25/2004 13:26:32, 81920 bytes
   Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4100 (English), 8/25/2004 13:12:10, 17408 bytes
   Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/8/2001 21:01:04, 24064 bytes
   Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4105 (English), 8/25/2004 13:26:56, 389120 bytes
   Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4105 (English), 8/25/2004 13:27:00, 86016 bytes
   Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2491 (English), 8/25/2004 13:27:18, 126976 bytes
   Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0010 (English), 8/25/2004 13:27:12, 102400 bytes
   Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2494 (English), 8/25/2004 13:27:04, 30720 bytes
   Driver: C:\WINDOWS\system32\ATIDEMGR.dll, 1.00.1698.24059 (English), 8/25/2004 14:22:08, 151552 bytes
   Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.4582 (English), 8/25/2004 13:48:12, 6508544 bytes
   Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4003 (English), 8/25/2004 14:40:02, 294912 bytes
Title: BSOD (blue screen of despair)
Post by: Krusty on August 15, 2007, 11:59:09 AM
Everything below "DirectPlay" you don't need (just for future reference).

So, AH actually runs on that machine? (*whistle*)

I ran "kmiersys" through google (and about 4 other search engines) but didn't turn up anything. Are you sure you got that part right?
Title: BSOD (blue screen of despair)
Post by: Krusty on August 15, 2007, 12:10:57 PM
After doing some google searching on the usbport.sys BSOD, it might be bad RAM.


Download memtest, put it on a floppy, and then boot the floppy (it doesn't load the OS then). Run the RAM test and leave it on for a few hours (leave it on overnight when you go to sleep if you can) and then check for errors.

EDIT: Here's one example where the same problem was caused by faulty RAM:
http://www.techspot.com/vb/topic43186.html
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 12:20:38 PM
No, I'm not sure I got that part right...  :D   My handwriting sucks, and I misspelled it wrong when I wrote it down, so I'm trying to figure out whatever I crossed out... I can't remember if it was a letter I put over it, or an awkwardly shaped x... :(   school's gonna' kill me.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 01:04:57 PM
I don't have any floppy disks...
Title: BSOD (blue screen of despair)
Post by: Krusty on August 15, 2007, 02:02:08 PM
Well pick one up somewhere. Something old will work. Borrow one from a friend. Or work. Or school. You just need to be able to format the disk, and you can format it again when you're done (to return it as an empty disk)
Title: BSOD (blue screen of despair)
Post by: StarOfAfrica2 on August 15, 2007, 02:21:35 PM
Try this link for your STOP error

http://support.microsoft.com/kb/330182/

Granted this doesnt apply your problem exactly, but I'd bet its similar.  Since you didn't just install Windows, I'd bet on bad memory.  Still, you can rule out your other hardware by running the DxDiagnostic tests.  I noticed you didnt run any of the tests.  It will tell if your video or sound drivers are causing lockups if you run the tests.  If one or the other fails, you found your culprit.

Edit

Either that or your hard drive is full.  How much space do you have on your hard drive?
Title: BSOD (blue screen of despair)
Post by: Krusty on August 15, 2007, 02:29:38 PM
No, before it got to that, Windows would slow down, and pop up a warning "System low on resources, run disk cleaner now?" (I've had that happen before, MOST annoying)
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 03:41:38 PM
I'll try what you told me in a second star of africa.  

CAUSE
This issue may occur if a system thread generates an exception that the error handler does not catch. This may occur if one or more of the following conditions exist:
•   If this issue occurs after the first restart during Windows Setup, or after Setup is finished, the computer may not have sufficient hard disk space to run Windows.
•   If this issue occurs after the first restart during Windows Setup, or after Setup is complete, the computer BIOS may be incompatible with Windows.  <--- long after this and the above.  
•   Incompatible video adapter drivers. <---- NO, because I was getting this problem before I updated my driver.
•   DAMAGED RAM  <----- THIS COULD BE IT
•   A damaged device driver or system service.
•   If the issue is associated with the Win32k.sys file, it may be caused by a third-party remote control program. <----  don't think so.
Title: BSOD (blue screen of despair)
Post by: StarOfAfrica2 on August 15, 2007, 03:42:09 PM
Might if Windows is using a dynamic size for whatever they call virtual memory now.  It would be fine at startup and under normal usage, but might try to increase it during certain applications and get a STOP error.  Or if part of the hard drive is bad and nothing can write to it but Windows still shows it as available.

My money is still on bad RAM.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 04:00:13 PM
OKAY, testing the direct X stuff.

I tested my direct draw.  I saw what looked like an optical illusion, then it asked me if I had seen these rectangle things.  I GUESS I did.  Because I considered the lines for the optical illusion looking thing to be rectangles.  It looked like, a cone/pyramid thing.  I also saw the bouncing white box in the small black square.  And then it went to full screen.  I saw the bouncing white box, but it wasn't going all the way to the top corners of the screen.  I said yes anyway.  

As for my test 3D thing.  I saw, what looked like a big hase... when it got done, it was a box with the direct x logo on it.  It asked me if I saw it spinning...  I GUESS I saw it spinning, it was moving really fast.  :rolleyes:

As for the sound thing... I heard a rainforesty sound, over and over again.  After I was done with that, a little box came up and said.  'Your sound card does not support hardware buffering.  Sounds will only playback from software buffers.  
(hmmm... need a new sound card?)  

for the music thing... I heard all of them the same, and it was some kind of jazz/funk thing.  Kind of like what you would use for an early morning soap Oprah or talk show.  :D

Looks like that's about it, i also tested my Microphone... I didn't know I sounded like I did :huh   :cry   anyway.  Tell me what you think.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 15, 2007, 07:18:58 PM
OKAY... so...  Should I try adding RAM to my computard?
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 16, 2007, 11:02:29 AM
I got to play for a good 15 minutes today before I got the blue screen again.  :(

This time it said

The problem seems to be caused by the following file: kmixer.SYS  PAGE_FAULT_IN_NON_PAGED_AREA

:huh

 It also said everything else.
Title: BSOD (blue screen of despair)
Post by: The Fugitive on August 16, 2007, 11:21:52 AM
I did a google search for what you typed, and got this as one of the top 5 responces.....

Hello to everyone who is searching for helpful information on the
BlueScreens and PAGE_FAULT_IN_NONPAGED_AREA Errors:

I had a lot of fun ;-) with lots of blue screens with sometimes a hint
at kmixer.sys and / or even nv4_disp.dll or so.

My CPU is a 2500+ at 3200+ and in combination with my old Geforce 2
GTS it was all great. Then I bought a new graphics-card and boom: i
was getting blue screens again and again. o.k. logical i changed the
graphics card with 3 other models, all geforce 5900 or 5900 XT with
extra power connection.

I did bios - updates,i did updates on everything, i bought ram-coolers
for my graphics card and for my normal rams. I did grab the net for
any information that could be helpful.

#############################
In SHORT: IT WAS THE VCORE FOR THE CPU, THAT WAS TO LOW.
#############################
(in the new combination with the graphics card)

(to solve it that did cost me about 1 weeks and I am a technician)


IN FACT INSUFFICANT POWER SUPPLY MAY BE THE SOURCE OF MANY PROBLEMS
OUT THERE. Think about it.

some keywords: PAGE_FAULT_IN_NONPAGED_AREA nv4_disp kmixer.sys Blue
Screen bluescreen BSOD hangs freezes freezing freeze especially
playing games 3D Nvidia 5900 5900XT


You may want to find out what size power supply you have.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 16, 2007, 11:24:16 AM
how would I do that?
Title: BSOD (blue screen of despair)
Post by: Irwink! on August 16, 2007, 11:49:28 AM
Quote
Originally posted by Oogly50
how would I do that?
 

Open the computer case and look at the label on the power supply. They all have labels with the power specifications listed.
Title: BSOD (blue screen of despair)
Post by: wabbit on August 16, 2007, 04:06:58 PM
When you look at the power supply check the max amps for the 12v legs. The
newer vid cards require a hefty load capability. Not sure about intergrated chips,
but suspect amps would be the source, unless you have a real low power supply, like a 250watt supply.

My 6800 and 7800 require a minumum of 20amps for the 12v legs. You'd have to check with the mtb manufacturer's tech support to see if there's any minimum for your system. For a 5x series I would guess 12 to 14 amps should be fine, but check with your mtb manufacturer just to be sure


If you can't see any info tag on the side of the power supply, post the brand and model number here, and I'll see if I can find anything out on it fer ya.


Wabbit
Morals & Manners Officer
Whitey's Buccaneers
5th Army Air Corps
Title: BSOD (blue screen of despair)
Post by: Krusty on August 17, 2007, 12:44:55 PM
I'm gonna go ahead and say "Naaaaahhh" (that is, I wouldn't think that's the problem, if it were my PC)

You should be able to read the voltages on the core (either from BIOS screen or from a hardware probe utility program). That'd be the easiest way to figure out if the core is getting enough juice. Way back when my old PSU was failing (stupid piece of junk!) it was severely under-volting my CPU, and it showed in all the probe utilities, and in my BIOS screen.


Might be easier to check that than try to explain the intricacies of PSU power distribution and sticker-reading ;)
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 24, 2007, 11:36:25 AM
okay... so, like I had mentioned earlier.  I got it on every game I played.

Today, I played a game called blockland.  Fun game...  Online.  And then... and then....  I got the blue screen again!  :cry

but this time... it said something a little bit different.

It had the usual mumbo-jumbo.  But in technical information It said :

***STOP: 6x000000BE (0x0067c804, 0x05F4B025, 0xFA00DE88, 0x0000000A)

***USBPORT.SYS-Adress F9970E7B base at F9965000 datestamp 41107d62

And, here's some things that I have learned SO FAR.

1. I have very little RAM (256)  

2. It happens to every online game I play.

3. It only happens online... I could play aceshigh 2 offline for days on end, with no bluescreen.

4. MY internet works fine...

5. I run spyware, adware, and virus scans every week.  But still hasn't fixed the problem.  

6. My video driver likes to un-install itself occasionally.  Usually after I scan.

7. Sometimes, when I'm playing a game, it shuts down, and on my monitor, blinding flashes of color fill my monitor.  EVERYWHERE.  My computer then slowly recovers.  20% of the time this happens, my driver uninstalls during the process.




As for what YOU said krusty.  how would I check my BIOS.  My blue screen keeps yelling at me too... but I dont know where i would go searching for it.  


IF you guys manage to fix this problem...  I will...  be very very happy!  

Thanks in advance :aok
Title: BSOD (blue screen of despair)
Post by: Irwink! on August 24, 2007, 12:28:32 PM
When you boot up your computer usually you have a black screen with white text listing various things like bios version and other system information. While that's happening there's usually a message near the bottom of the screen to "press F1 to enter setup" or something like that. That's what you need to do to enter the bios area. The message and the opportunity to hit F1 or whatever key it tells you isn't onscreen very long so you have to act fast.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 24, 2007, 09:07:11 PM
Okay...  I tried looking for that screen.  Couldn't find it, instead a couple of other screens popped up.

The first one was simply one that showed computer temp for about... 2 seconds.  I pressed f1 during this and nothing happened.  Next came a screen that in the top left corner... said:

Invalid BOOT.INI File
booting from C:\windows\


And then that disk check screen came up... which usually comes up after every blue screen.  If you want to know what it was...  I can tell you.

Heck, I'll just tell you now.

It said all the usual silly stuff about what it was doing, and said that the type of the file system is FAT32

Volume Serial Number is 1BOC-5B36






ALSO.  A system configuration utility pops up every time I start my computer. Under general everything is checked.  

But when I go to BOOT.INI  Nothing is checked.  When I click one something... the utility locks up, and then I can't close it.  After that, something comes up in the center of my screen saying.  DrWattson DeBug reporter has encountered a problem.

I DON'T EVEN HAVE THIS PROGRAM... I don't know what it is!  My computer is so messed up!!!  All I wanted to do was play aces high!!!  
 :cry :cry :cry

Help please
Title: BSOD (blue screen of despair)
Post by: Irwink! on August 24, 2007, 09:44:12 PM
Nah, I don't know your machine but somewhere on the first or one of the first screens that come up at boot there will be instruction to hit a certain key to enter bios configuration. Remember the message may not be exactly the same on all machines and the key you press to enter bios may not be F1 - the exact message and key vary from machine to machine. Also remember that the message may appear only for a second or two during the boot process.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 26, 2007, 02:53:20 PM
nothing... even tried restarting the computer 12 times and pressing every f# button there is on every screen.
Title: BSOD (blue screen of despair)
Post by: Krusty on August 31, 2007, 12:40:35 PM
Most common BIOS entry keys are F1, F2, and DEL

Sometimes if you have a splash image on the screen you can hit ESC or TAB to clear it and see what the BIOS is saying (sometimes, not always)
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 31, 2007, 12:48:25 PM
I've also been attacked by a virus that keeps asking me to download an anti-spyware program. But after reading up on it, found out that it would just kill my computer even further. When I do actually play more than 5 minutes on AH, I get the little bubble that pops up, and then it shuts down aces high. I'll be getting rid of that.

And on top of everything ELSE. A video driver I recently tried to update, supposedly had something 'wrong' with it, and now it uninstalls itself regularly every day or so. I tried reinstalling it, but now.. it won't install.

My computer's a handfull.

Oh and, I managed to get into my BIOS screen, but I didn't know what I was supposed to be looking at.
Title: BSOD (blue screen of despair)
Post by: Krusty on August 31, 2007, 12:51:16 PM
There should be a page in the BIOS that tells you the current hardware "sensors" output. It should list voltages for things like vcore, +5v, +12v, and some others, as well as temperature readouts.

That info could help.



On the other hand, I think you need to back up your personal files, FORMAT C: and start over with a fresh install.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 31, 2007, 12:52:54 PM
For my video driver?  

How would I do all that?



Sorry if I'm being a handful.
Title: BSOD (blue screen of despair)
Post by: Krusty on August 31, 2007, 01:02:42 PM
Quote
Originally posted by Oogly50
For my video driver?  

How would I do all that?



Sorry if I'm being a handful.


No, not for your video driver. The page in the BIOS will have readouts for the motherboard and CPU.

The backup isn't about the vid driver, it's about a PC that's infested so bad you can't get it to do what it is supposed to do. Probably the best way to do this (and insure you get it all cleaned out) is to reformat and reinstall windows.

However, that wipes all your personal files (photoshop, e-mail, broswer favorites, you name it) and all these need to be backed up.

*If* you go with the wipe/reinstall option.


Download and install:
spybot search and destroy
adaware
avg (an anti-virus)

They are all free.

Run the first 2 and see how many things you can clean out.
If that doesn't help, install the AVG. You may have to remove or disable your existing AV software -- not that it was doing its job anyways!

Then run a full HD scan with AVG (this could take hours), and clean/delete any viruses it finds.
Title: BSOD (blue screen of despair)
Post by: Oogly50 on August 31, 2007, 01:11:15 PM
I have all three of those already :)  

I'll run the scans and edit this post when they're done.
Title: BSOD (blue screen of despair)
Post by: Krusty on August 31, 2007, 01:12:42 PM
Make sure you choose the "full system scans" instead of the lesser, faster, scans.
Title: BSOD (blue screen of despair)
Post by: gpwurzel on August 31, 2007, 01:16:40 PM
Oogly, run your scans in safe mode fella, that way you can delete them straight away, as they wont delete if they are doing things (you'll get a pop up saying that). If you find you cant get rid of them all............I'd go with Krusty's idea and do a full install.......any, and I mean any, files you save off your puter to disk/cd/whatever, ensure you do a full virus scan on them before even thinking of putting them back on.............trust me on this one...seen it done sooo many times and had to put the puter to rights afterwards.......

Hope you get it sorted fella...


Wurzel
Title: BSOD (blue screen of despair)
Post by: Krusty on August 31, 2007, 01:40:24 PM
Wurzel brings up a very good point. Some viruses are malicious and aggressive, and spread themselves in many places to prevent removal. If you back up any data, make sure you scan it before copying it over to the re-installed hard-drive (from the CD-ROM or DVD-ROM or whatever)