Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini051906-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32 \drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri May 19 20:45:10.406 2006 (GMT-4)
System Uptime: 0 days 0:10:43.051
Loading Kernel Symbols
.................................................. .................................................. ...................
Loading User Symbols
Loading unloaded module list
...........
*** ERROR: Symbol file could not be found. Defaulted to export symbols for nv4_disp.dll -
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bfacd1cc, b9baeae4, 0}

Probably caused by : nv4_disp.dll ( nv4_disp+f91cc )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bfacd1cc, The address that the exception occurred at
Arg3: b9baeae4, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nv4_disp+f91cc
bfacd1cc 8b80ac010000 mov eax,[eax+0x1ac]

TRAP_FRAME: b9baeae4 -- (.trap ffffffffb9baeae4)
.trap ffffffffb9baeae4
ErrCode = 00000000
eax=00000000 ebx=000001c0 ecx=00000000 edx=e4c76580 esi=00000145 edi=e30bf800
eip=bfacd1cc esp=b9baeb58 ebp=00000000 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nv4_disp+0xf91cc:
bfacd1cc 8b80ac010000 mov eax,[eax+0x1ac] ds:0023:000001ac=????????
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to bfacd1cc

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_disp+0xf91cc


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nv4_disp+f91cc
bfacd1cc 8b80ac010000 mov eax,[eax+0x1ac]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_disp+f91cc

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4410c8d4

FAILURE_BUCKET_ID: 0x8E_nv4_disp+f91cc

BUCKET_ID: 0x8E_nv4_disp+f91cc

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

eax=00000000 ebx=000001c0 ecx=00000000 edx=e4c76580 esi=00000145 edi=e30bf800
eip=bfacd1cc esp=b9baeb58 ebp=00000000 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nv4_disp+0xf91cc:
bfacd1cc 8b80ac010000 mov eax,[eax+0x1ac] ds:0023:000001ac=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 nv4_disp+0xf91cc
start end module name
804d7000 806eb100 nt ntoskrnl.exe Tue Mar 01 19:59:37 2005 (42250FF9)
806ec000 8070c380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
b7e23000 b7e33280 Udfs Udfs.SYS Wed Aug 04 02:00:27 2004 (41107B7B)
b86fe000 b8727f00 kmixer kmixer.sys Wed Aug 04 02:07:46 2004 (41107D32)
b9aae000 b9aee100 HTTP HTTP.sys Fri Oct 08 19:48:20 2004 (41672744)
b9d1f000 b9d70300 srv srv.sys Mon May 09 20:17:49 2005 (427FFDAD)
b9f29000 b9f55400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
ba27b000 ba28f400 wdmaud wdmaud.sys Wed Aug 04 02:15:03 2004 (41107EE7)
baba8000 babb6d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
bacfc000 bacff280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 20:05:44 2005 (43446A58)
bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf9d4000 bfd9ce00 nv4_disp nv4_disp.dll Thu Mar 09 19:31:16 2006 (4410C8D4)
f3df0000 f3e07480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f3e08000 f3e2b000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
f3fdf000 f409c600 avg7core avg7core.sys Mon Apr 24 05:53:04 2006 (444CA000)
f4155000 f4157900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f4165000 f4185f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f4186000 f41f4400 mrxsmb mrxsmb.sys Tue Jan 18 23:26:50 2005 (41EDE18A)
f41f5000 f421fa00 rdbss rdbss.sys Wed Oct 27 21:13:57 2004 (418047D5)
f4220000 f4241d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f4242000 f4269c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f426a000 f42c1d80 tcpip tcpip.sys Wed May 25 15:04:00 2005 (4294CC20)
f42c2000 f42d4400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f6453000 f6486200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f64b7000 f64c6900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f6527000 f6537e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f6538000 f654e680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f654f000 f6562900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f6563000 f6586800 e100b325 e100b325.sys Tue Mar 04 1425 2003 (3E6504E9)
f6587000 f65ad000 ctsfm2k ctsfm2k.sys Mon Jan 10 05:15:22 2005 (41E255BA)
f65ad000 f65dd000 ctoss2k ctoss2k.sys Mon Jan 10 05:15:28 2005 (41E255C0)
f65dd000 f65ff680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f6600000 f6623980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f6624000 f6777200 P17 P17.sys Thu Jul 07 04:14:18 2005 (42CCE45A)
f6778000 f679ae80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f679b000 f67ae780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f67af000 f6b2a340 nv4_mini nv4_mini.sys Thu Mar 09 19:40:42 2006 (4410CB0A)
f73a9000 f73acc80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f73b1000 f73b3580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f73b9000 f73bcc80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f73f1000 f740b580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f740c000 f7438a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f7439000 f74c5480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f74c6000 f74dc780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f74dd000 f74eef00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f74ef000 f750d780 fltmgr fltmgr.sys Wed Aug 04 02:01:17 2004 (41107BAD)
f750e000 f7525800 SCSIPORT SCSIPORT.SYS Wed Aug 04 01:59:39 2004 (41107B4B)
f7526000 f753d480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f753e000 f755c880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f755d000 f756da80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f756e000 f7593e00 d347bus d347bus.sys Sun Aug 22 09:31:09 2004 (4128A01D)
f7594000 f75c1d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f75e3000 f75ebc00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f75f3000 f75fd500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f7603000 f760fc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f7613000 f761be00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f7623000 f762f200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f7633000 f763d580 agp440 agp440.sys Wed Aug 04 02:07:40 2004 (41107D2C)
f7673000 f767be40 SMBios SMBios.sys Thu Sep 11 18:20:22 2003 (3F60F526)
f7693000 f769ba00 processr processr.sys Wed Aug 04 01:59:14 2004 (41107B32)
f76a3000 f76b1b80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f76b3000 f76bfe00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f76c3000 f76d2d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f76d3000 f76dd380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f76e3000 f76ef180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f76f3000 f7701080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f7703000 f770f880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f7713000 f771d200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f7723000 f772ed00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f7733000 f773b900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f7743000 f774cf00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f7753000 f775c480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f7763000 f7771100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f7793000 f779b700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f77b3000 f77bb880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f77c3000 f77cb700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f77d3000 f77dbd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f7863000 f7869200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f786b000 f786f900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7933000 f7937500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f7963000 f7968000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f796b000 f7971800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7973000 f7979000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f797b000 f797c000 fdc fdc.sys unavailable (00000000)
f7983000 f798a000 GEARAspiWDM GEARAspiWDM.sys Wed Feb 02 00:19:49 2005 (420062F5)
f798b000 f798f880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7993000 f7997580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f799b000 f799f080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f79a3000 f79a8a00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f79ab000 f79b0000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f79bb000 f79c1180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f79c3000 f79c8200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f79cb000 f79cfa80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f79d3000 f79da880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f79e3000 f79e9c80 avg7rsxp avg7rsxp.sys Wed Feb 22 19:40:37 2006 (43FD0485)
f79f3000 f79f6000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7a8b000 f7a8d280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f7aaf000 f7ab1580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f7ab3000 f7ab5f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f7ab7000 f7ab9b80 IPFilter IPFilter.sys Thu Apr 11 14:47:22 2002 (3CB5DA3A)
f7ae3000 f7ae4b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7ae5000 f7ae6100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7ae7000 f7ae8480 d347prt d347prt.sys Sun Aug 22 09:31:48 2004 (4128A044)
f7aeb000 f7aeca80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
f7aef000 f7af0380 avgtdi avgtdi.sys Sat Sep 03 20:38:58 2005 (431A4222)
f7b13000 f7b14900 splitter splitter.sys Wed Aug 04 02:07:46 2004 (41107D32)
f7b17000 f7b18100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7b1b000 f7b1c280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7b1d000 f7b1ef00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7b1f000 f7b20080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7b21000 f7b22080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7b23000 f7b24080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7b2b000 f7b2c0c0 avg7rsw avg7rsw.sys Sun Sep 18 20:09:31 2005 (432E01BB)
f7b5d000 f7b5e100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7bab000 f7babd00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7c34000 f7c34d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f7c93000 f7c93c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f7d10000 f7d10b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
f7d2a000 f7d2ab80 mbmiodrvr mbmiodrvr.sys Sat Apr 10 10:42:35 2004 (407807DB)

Unloaded modules:
ba22e000 ba258000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c12000 f7c13000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bad90000 bad9d000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bada0000 badae000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ba258000 ba27b000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b75000 f7b77000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f64a7000 f64b3000 ATITool.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f77a3000 f77ac000 intelppm.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7a87000 f7a8b000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79b3000 f79b8000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7a83000 f7a86000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt








Now just take a look at that. I'm going to kill that pig and smash this computer.

Godforsaken turd ripped $46 out of me. I'll get it back in blood GOD DAMNIT!

You should definitely demand your money back.

Same old error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem.

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.


Anything different about what you were doing? Were you able to restart immediately?

Yes. I immediately went back into Battlefront II. That first crash was in the main menu when I was selecting a map list. After restarting, I created a map list, went into the game and crashed in the first minute. Then I went back into Battlefront II and played online for over an hour with no crashes. *Sigh*

It's safe to rule out heat. How can a computer crash within the first minute of operation?

I want to buy a new motherboard, but not until I am 100% certain it will solve my problems and have gotten my money back! All week my father has driven me to Staples and back. That technician can go back to being a janitor in a library.

It is hard to pinpoint the hardware issue without being able to test each component.

Especially the RAM; Graphics Card; and CPU. If you can absolutely say that these components are OK then you can probably say the motherboard is having problems.

But mostly a motherboard with problems will not even boot the BIOS.

As you have worked thru the RAM and Graphics Card I would try a different CPU (if possible).

I don't see how this can be software alone. Did you tell the tech guy about all the dumps and everything that you have tried? Have you asked about hardware issues? Can you see if he has a spare CPU to test?

BTW: I once met a very smart janitor in a library. He read all night for years and years. He just had no other ambition.

Nice janitor story, heh.

I put up two fresh dumps, debugged and in a text document on my desktop. I also had another text document where I explained everything about the crashes and the fact that I changed my video card and all. When I hooked up the computer, I took a look at the times that these 3 files were accessed; at 4-second intervals. I'm sure he read through them, right...

RAM - tested with Memtest successfully. Computer still crashed when either one of them was in there, new and old one. The old stick never showed any signs of damage or defection. New stick is..well, new. I also cleaned the gold-plated connectors with an eraser.

Graphics card - self-explanatory; upgraded to pure sexiness

CPU - Hmm, could it be that the processor stops...processing within a minute of games? And when I turn on a game, then shut off the computer and turn it on the next day, getting a dump that I would've gotten if I had played a little longer, could that be CPU?

Motherboard - Hmm (I wish it really was the mobo) But I have read instances where mobos do these sorts of things but boot normally. Remember the oddities that would happen, such as the computer no longer turning on or XP blue screening before it loads? That would all be blamed at the mobo.

Hard drive - Works fine; I could do ANYTHING except play games and I wouldn't crash at all. Scanned and diagnosed lots of times.

PSU - Well, it is new and I think the technician did a power test. Or maybe one of the computer associates lied on the phone...

Heat - no, I would get a frostbite if I stuck my head in there. Cool as a...cooling...tank...?

Software such as drivers - that's what that "genius" claimed. Pfft.

Dummy should've at least checked all my IDE cables! But then again, problems there should cause universal crashes, not just game-related ones.

What anti virus are you using? What firewall?

As a test go to start/run msconfig | startup

Uncheck everything and reboot and try to play.

Hmm I haven't crashed now. The only times I crashed were the two early ones that happened as soon as I turned on a game when I brought the computer home. I've played Battlefront II and NHL 06 online so far.

BTW, unchecking everything in msconfig? :O!

I'm using Windows Firewall and an always-updated AVG Free.

There is nothing in msconfig startup that XP needs to start.

Everything listed there has been added by 3rd party software.

Unchecking is a test mode. You can always recheck.

The only 2 items that I have starting are AVG and my Firewall (Sygate).

This is just a test to see if some software is triggering your issues.

Ok, I disabled all startup items, save A/V, Creative sound control panel, NeroCheck, and Nvcpl (Nvidia display panel)

I've also noticed that BSOD crashes completely screw up my drive speeds. For example, when I look at the settings through Nero, my CD-RW is reading at 40x or 24x instead of 52x and my DVD drive is reading at 2x instead of 16x. I clicked the box to "restore settings at startup" but even manually changing the speeds doesn't work. It pisses me off and it started with the BSODs.