View Full Version : Blue Screen in XP New Build - HELP PLEASE
iambentheboff
10-09-2007, 09:33 PM
Recently put together this system:
Antec Sonata 3 Super Black Mini Tower
Intel-DC e6750 @2.66GHZ
Arctic Cooling Freezer 7 Pro
2GB (2x1GB) CorsairTwinX XMS2, DDR2
LiteOn DH-20A3P-12C 20x DVD±R, 8x
Abit Fatality FP-IN9 SLI Mobo
Sapphire 1950 GT 256MB
Samsung HDD 250 (E-IDE) spinpoint
AKASA 3.5" AK-ICR-01E Internal Multi card reader
19" Iiyama PLE1900WS-B
Microsoft Windows XP Home Edition
Microsoft Desktop 6000 Cordless
Kept having BSOD for multiple reasons which I could not work out. I ran Memtest for 10 cycles w/o any errors at all. Also changed hard disks, reinstalled XP home to a different samsung HDD but SATA and changed the graphics card to 1950XT. Downloads new drivers for Graphics card and motherboard but still getting intermittent errors.
First time round used Abit firewall and had no anti-virus. Second time used windows firewall and McAfee Suite but still happening. Rarely get same BSOD message more than once.
Tried RAM in different slots. More than powerful enough PSU, brand new, no dust. Using Antec Freezer but not overclocked and CPU runs at 27 oC.
Included some minidump files, can anyone help??
kane77573
10-09-2007, 09:38 PM
I will check the memory dumps for you.
gerrynicol
10-09-2007, 09:43 PM
I had a bad board with what looks like the same issues as you are having. I suspected my RAM first but then used some gold ram and it still crashed. swapped the mobo out and the system now runs fine. You could try updating the BIOS, but I had no luck with any of the bios updates. Check the net for issues with the board, im sure the
kane77573
10-09-2007, 09:45 PM
Well mcafee crashed your box on one occasion
WRITE_ADDRESS: 0000002c
CURRENT_IRQL: 2
FAULTING_IP:
NVENETFD+a02
b9ce1a02 894b2c mov dword ptr [ebx+2Ch],ecx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: McProxy.exe
LAST_CONTROL_TRANSFER: from b9ce1c50 to b9ce1a02
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9bec963c b9ce1c50 894b03b0 89079d08 00000002 NVENETFD+0xa02
9bec965c ba62e600 894b0008 9bec9688 00000001 NVENETFD+0xc50
9bec9674 806e6c4f 89548030 00000000 89cf2000 NDIS!ndisMProcessSGList+0x90
9bec9698 ba62e56e 00000000 89548030 886196fc hal!HalBuildScatterGatherList+0x191
9bec96f0 ba615a08 00000000 00000001 897d66b0 NDIS!ndisMAllocSGList+0xd9
9bec970c b989a528 897d66b0 89079d08 89079cd0 NDIS!ndisMSendX+0x1a0
9bec9748 ba615985 8994c6e8 89079d08 00000002 psched!MpSend+0x706
9bec9770 abb01d00 893856c8 89079d08 8974e658 NDIS!ndisMSendX+0x1d6
9bec9798 abb018ce 8974e658 89079d08 88f63240 tcpip!ARPSendData+0x198
9bec97c4 abb0170a 8974e658 9bec9800 00000001 tcpip!ARPTransmit+0x193
9bec97f4 abb014a9 8974d630 0100a8c0 89079d08 tcpip!SendIPPacket+0x18e
9bec9940 abb06da8 abb3f698 8892a4a8 8892a440 tcpip!IPTransmit+0x287f
9bec99ac abb0713b d2c55b01 00000100 886196d8 tcpip!TCPSend+0x5d8
9bec99d4 abb06766 00000001 00000000 00000100 tcpip!TdiSend+0x1cc
9bec9a08 abb0423d 88619620 889d982c 9bec9a60 tcpip!TCPSendData+0x83
9bec9a24 804ef095 8971f900 88619620 abadc0d0 tcpip!TCPDispatchInternalDeviceControl+0x51
9bec9a34 abae2c7a 9bec9aa4 abadc0d0 9bec9a0f nt!IopfCallDriver+0x31
9bec9a6c abadc19a 89737870 88619620 88619008 Mpfp+0x7c7a
9bec9aa8 804ef095 89737870 88619620 88922228 Mpfp+0x119a
9bec9ab8 ab9dcede 00000000 00000008 9bec9b1c nt!IopfCallDriver+0x31
9bec9b10 ab9d35e5 885cbc78 0160a728 ab9d35e5 afd!AfdFastConnectionSend+0x209
9bec9c5c 8057f1fd 8861b960 00000001 013efe78 afd!AfdFastIoDeviceControl+0x415
9bec9d00 805780c2 000008cc 00000000 00000000 nt!IopXxxControlFile+0x255
9bec9d34 8054086c 000008cc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
9bec9d34 7c90eb94 000008cc 00000000 00000000 nt!KiFastCallEntry+0xfc
013efec8 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
NVENETFD+a02
b9ce1a02 894b2c mov dword ptr [ebx+2Ch],ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: NVENETFD+a02
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NVENETFD
IMAGE_NAME: NVENETFD.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43f615cd
FAILURE_BUCKET_ID: 0xD1_W_NVENETFD+a02
BUCKET_ID: 0xD1_W_NVENETFD+a02
Followup: MachineOwner
Uninstall mcafee first
try this for a few days and see if you get another Bluescreen.
try reinstalling the NIC driver and overwrite the old one.
Then if not, I also saw the problem stemed from when mcafee scanned the nvidia lan driver sys file
Disable this in the bios if you have another nic card if uninstalling mcafee does not work
And try running the os with this disabled.
this next debug file speaks for itself, Might be some usb drive you plugged in also.
READ_ADDRESS: 026e6f6c
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_CompleteTransfer+1a
b998cb8c 8b7728 mov esi,dword ptr [edi+28h]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from b998e754 to b998cb8c
STACK_TEXT:
8055036c b998e754 026e6f44 89d6c0e0 89d6c0e0 USBPORT!USBPORT_CompleteTransfer+0x1a
805503a4 b998ff6a 89d6c028 80545d0c 89d6c230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
805503d0 b999dfb0 89d6c028 80545d0c 89d6c028 USBPORT!USBPORT_DpcWorker+0x224
8055040c b999e128 89d6c028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
80550428 805450bf 89d6c64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544fa4 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !USBPORT
b998cb40-b998cb48 9 bytes - USBPORT!USBPORT_QueuePendingUrbToEndpoint+19a
[ 04 03 4b 08 89 01 89 71:75 e7 83 65 fc 00 8b 40 ]
b998cb4a-b998cb4b 2 bytes - USBPORT!USBPORT_QueuePendingUrbToEndpoint+1a4 (+0x0a)
[ 46 08:55 fc ]
b998cb4d-b998cb69 29 bytes - USBPORT!USBPORT_QueuePendingUrbToEndpoint+1a7 (+0x03)
[ 61 0c 00 89 41 08 8a 96:c0 28 85 d2 8d 4b 02 89 ]
b998cb6b-b998cb7f 21 bytes - USBPORT!USBPORT_QueuePendingUrbToEndpoint+1c5 (+0x1e)
[ 00 cc cc cc cc cc cc 8b:02 3b 45 e8 89 45 d8 89 ]
61 errors : !USBPORT (b998cb40-b998cb7f)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE_64
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_64
BUCKET_ID: MEMORY_CORRUPTION_LARGE_64
Followup: memory_corruption
iambentheboff
10-09-2007, 10:09 PM
I was still having problems even when McAfee not installed. I installed anti-virus software just incase there was any problems with my first install. Could the USB problem be an internal card reader that plugs into the usb header on the mobo?
kane77573
10-09-2007, 10:41 PM
try disconnecting that usb reader
also try and use another nic card and disable the onboard in bios.
gerrynicol
10-09-2007, 11:34 PM
you can also check this thread out, this is where I got most of the info I had.
http://forums.hexus.net/showthread.php?t=100633
I killed my board using Bios 13 though wouldn't even boot, no screen at all.
If your bios is the early one (10 I think) it has a lot of issues, even now the latest bios has not solved everyone issues.
but hey go through the motions and check all the dumps if you like http://www.observedtrials.net/vb/images/smilie/dunno.gif
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.