check you downloaded the correct network driver
this is what I have: Intel® PRO/Wireless 3945ABG Network Connection: 12.4.3.9 and that is the latest according to the Intel website.
I don't know about the realtek network adapter though because their website is not clear to me.
I have a Realtek PCIe GBE Family Controller. with this version 5.736.728.2009 I don't know what to check it against because there are all these fake realtek websites and no real one with info on it.
EDIT. I found a download page from PC pitstop that has my driver version as the current one for WinXP. Maybe the internet gods just hate me.
parallel port drivers are used only for printing, not for general data transfer.
Maybe the printer software is the problem? It's the only thing that was installed before the problem started... is that possible?
Maybe I should uninstall all my software one by one... i dunno. System restore doesn't work at all (I thought I was clever by creating a restore point before I did anything with the computer, but it does not help me because it won't revert to that point, or any other point for that matter).
check you downloaded the correct network driver
I expanded the list of network adapters and updated everything. Only the Realtek PCIe Family Controller downloaded an update.
Then I went on facebook and loaded restaurant city to test it. The computer froze but did not turn off and was making a terrible noise. This is the same thing that it did with a DVD except the screen blanked out that time. I had to manually shut it down. Then it loaded normal and then went to BSOD. But then auto restart so I couldn't read it (EVEN THOUGH I changed that setting previously. weird).
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000008, 0xba340d70, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini100209-01.dmp.
I hate this.:upset:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini100209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Oct 2 00:08:42.812 2009 (GMT-7)
System Uptime: 0 days 0:01:33.500
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, ba340d70, 0, 0}
Probably caused by : ntoskrnl.exe ( nt!NtGetWriteWatch+433 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: ba340d70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: dwwin.exe
LAST_CONTROL_TRANSFER: from 00000000 to 8053bbaa
STACK_TEXT:
a61f6ffc 00000000 00000000 00000000 00000000 nt!NtGetWriteWatch+0x433
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtGetWriteWatch+433
8053bbaa 53 push ebx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!NtGetWriteWatch+433
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3
FAILURE_BUCKET_ID: 0x7f_8_nt!NtGetWriteWatch+433
BUCKET_ID: 0x7f_8_nt!NtGetWriteWatch+433
Followup: MachineOwner
Here's the mini dump from the DVD failure. Isn't this fun?!
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini093009-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Sep 30 21:39:49.515 2009 (GMT-7)
System Uptime: 0 days 0:45:45.195
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
...........
*** WARNING: Unable to verify timestamp for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1902fe, a6d61570, a6d6126c, b9e7b8c7}
*** WARNING: Unable to verify timestamp for fltmgr.sys
Unable to load image SRTSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
Probably caused by : Ntfs.sys ( Ntfs!NtfsFinishIoAtEof+5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 001902fe
Arg2: a6d61570
Arg3: a6d6126c
Arg4: b9e7b8c7
Debugging Details:
------------------
EXCEPTION_RECORD: a6d61570 -- (.exr 0xffffffffa6d61570)
ExceptionAddress: b9e7b8c7 (Ntfs!NtfsFinishIoAtEof+0x00000005)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: a6d6126c -- (.cxr 0xffffffffa6d6126c)
eax=00000000 ebx=a6d61710 ecx=8ac38270 edx=00000000 esi=e1a420d0 edi=a6d618f4
eip=b9e7b8c7 esp=a6d61638 ebp=a6d61638 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
Ntfs!NtfsFinishIoAtEof+0x5:
b9e7b8c7 8f ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x24
PROCESS_NAME: PowerDVD.exe
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER: from b9e8189c to b9e7b8c7
STACK_TEXT:
a6d61638 b9e8189c e1a420d0 b9e82fd2 8aca6748 Ntfs!NtfsFinishIoAtEof+0x5
a6d6163c e1a420d0 b9e82fd2 8aca6748 a6d616b4 Ntfs!NtfsCommonQueryInformation+0x375
WARNING: Frame IP not in any known module. Following frames may be wrong.
a6d61698 b9e8149c a6d61710 8aca6748 8ad332d0 0xe1a420d0
a6d616fc b9e814d5 a6d61710 8aca6748 00000001 Ntfs!NtfsFsdDispatchSwitch+0x12a
a6d61820 804ef19f 8ad1c020 8aca6748 8aca6748 Ntfs!NtfsFsdDispatchWait+0x1c
a6d6185c 804ef19f 8ad332d0 8aca6748 8ad23698 nt!MiFlushSectionInternal+0x256
a6d61874 804ef19f 8ad1d4d8 8aca6748 8aca6748 nt!MiFlushSectionInternal+0x256
a6d618a8 b9f159e5 a6d618c8 8a53c258 00000000 nt!MiFlushSectionInternal+0x256
a6d618e0 a81b09f1 8ac4bbf0 a6d6192c e829a2c0 fltmgr!FltPerformSynchronousIo+0xb9
a6d61914 a81b177d 89c21ecc e829a2a8 a81b5d68 SRTSP+0x189f1
a6d61934 a81a990c a67e00a1 89c21e70 89c21f24 SRTSP+0x1977d
a6d61978 b9f11ef3 01c21ecc 01d6199c 00000000 SRTSP+0x1190c
a6d619e0 b9f14338 00c21e70 00000000 89c21e70 fltmgr!FltpPerformPostCallbacks+0x1c5
a6d619f4 b9f14867 89c21e70 89d897f0 a6d61a34 fltmgr!FltpProcessIoCompletion+0x10
a6d61a04 b9f14ef9 8a53c258 89d897f0 89c21e70 fltmgr!FltpPassThroughCompletion+0x89
a6d61a34 b9f21754 a6d61a54 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x269
a6d61a70 804ef19f 8a53c258 89d897f0 89d897f0 fltmgr!FltpCreate+0x26a
a6d61b60 805bf450 8ad2f9e8 00000000 8ac7aa50 nt!MiFlushSectionInternal+0x256
a6d61bd8 805bb9dc 00000000 a6d61c18 00000040 nt!MiFindExportedRoutineByName+0x6e
a6d61c2c 80576033 00000000 00000000 00000001 nt!IopInitializeDCB+0xb2
a6d61ca8 805769aa 0b8fef3c 00100020 0b8fef10 nt!SeAssignSecurity+0xa
a6d61d04 8057a1a9 0b8fef3c 00100020 0b8fef10 nt!SepDuplicateToken+0x22a
a6d61d44 8054162c 0b8fef3c 00100020 0b8fef10 nt!RtlFreeHeap+0x193
a6d61d64 7c90e514 badb0d00 0b8feec0 00000000 nt!RtlIpv4StringToAddressExW+0xad
a6d61d78 00000000 00000000 00000000 00000000 0x7c90e514
FOLLOWUP_IP:
Ntfs!NtfsFinishIoAtEof+5
b9e7b8c7 8f ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Ntfs!NtfsFinishIoAtEof+5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025be5
STACK_COMMAND: .cxr 0xffffffffa6d6126c ; kb
FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsFinishIoAtEof+5
BUCKET_ID: 0x24_Ntfs!NtfsFinishIoAtEof+5
Followup: MachineOwner
---------
In network connections I disabled the LAN and enabled the wireless internet. I thought that maybe if the problem lies with the 'wired' network adapter then maybe I should try to use the wireless instead.
So using the wireless connection I went on the internet and loaded my stupid game frozen, computer made grinding noise. I turned it off. I got a BSOD.
Then another same BSOD when rebooting again.
THEN I rebooted the computer and opened device manager and it sort of froze and SKINNY HORIZONTAL bars danced on the screen!!! ***?! (I capture all this on video for the manager of MDG).
Then I rebooted and it would not turn on. It sounded on but the screen was blank.
then I rebooted and tried to open the internet and it froze when I was entering the WEP. And the dancing horizontal bars appeared again.
Then I rebooted but the screen remained blank while it sounded like it was turning on. Power button light on.
Then I rebooted and it turned on. I checked the device manager for info. Nothing different. Connected to internet wirelessly after entering WEP key. Came to this board to write this up and it crashed. lol. kill me please. BSOD. and then another BSOD after reboot.
And then one of those 'load in safe mode or start window normally' screen. And it froze on that.
Reboot and then another load in what mode screen. Selected last known good configuration. Then it finally loaded. I disabled the wireless and enabled the wired.
Then I turned it off and took out the RAM and put in the other stick to see what would happen. And here I am. (And it's 2am. And I wanted to go to bed early. And my side hurts and I'm dying of an ulcer.)
So.... I don't think that there is a point in posting all the memory dumps and BSODs I took pictures of because I have decided that my laptop is a lemon and I will call the MDG manager tomorrow morning.
I dare not try to connect wirelessly with this RAM because I just can't take it. I dare not open facebook either. This RAM is untested but the previous one passed as clean on the first pass (but then memtest froze after 94% on the 2nd pass... soo.... broked?).
EDIT. the bars were horizontal not vertical.