BSOD

[sawwei]

Hi Guys,

I am in a need of urgent help, because of the BSOD that I'm constantly having.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88002F88850
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Windows OEM 7 Home Premium x64
Alienware M15x
i7 Q720, 4GB DDR3 RAM, NVIDIA GeForce GTX 260M

The minidumps is attached.
Thank you so much.

 

[richc46]

Sorry no minidump. No download of any kind.

 

[CarlTR6]

Please read these threads and post back. We will be glad to help you.

[1 - Novice] How to ask for help with a BSOD problem

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy.

 

[sawwei]

Thank you for the replies.
I have follow the instruction and put all the minidumps and system health reports in a RAR files.
Do I have to use WINZIP? or will it be fine with WINRAR?
I have attached the files to my post, and I don't understand why doesn't it shows.

 

[zigzag3143]

Thank you for the replies.
I have follow the instruction and put all the minidumps and system health reports in a RAR files.
Do I have to use WINZIP? or will it be fine with WINRAR?
I have attached the files to my post, and I don't understand why doesn't it shows.

How big is it? if more than 8 Mb you will have to put it on an upload service like rapidshare.

Ken

 

[sawwei]

It's only 326kb
I uploaded it again in this post.
Please let me know if you can access it.
I have also updated my User CP with more detailed information of my system.
I have just performed a system recovery two days ago and last night I turned on my notebook for the whole night because I was downloading some torrents files.
When I woke up in the morning I found out that my notebook was restarted and there was the BSOD notifications on the screen.
This is time the BSOD occured when I did not do anything at all.
BSOD happened several times before I did the system recovery and everytime when I checked the windows solutions it was always stated that Video Hardware Error caused the Windows to stop working properly.
I just bought my notebook last February, and it is still under warranty, and I am thinking to send them to the manufacturer, but I can't seem to be able to trigger the BSOD whenever I want to, so how can I be sure if they fixed the problems.
Thank you.

 

[CarlTR6]

Error code 1E KMODE_EXCEPTION_NOT_HANDLED - Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88002f88850, 0, 0}

Probably caused by : nwifi.sys ( nwifi!Dot11AllocateSendPacket+58 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002f88850, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


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

FAULTING_IP: 
+575e952f007ad868
fffff880`02f88850 6897f80280      push    0FFFFFFFF8002F897h

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb40e0
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f89768 -- (.exr 0xfffff88002f89768)
ExceptionAddress: fffff80002a7f905 (nt!ExpInterlockedPopEntrySListFault16)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f89810 -- (.trap 0xfffff88002f89810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000002a81940007 rbx=0000000000000000 rcx=fffff88008b1c280
rdx=48dd6f4b988e70e1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a7f905 rsp=fffff88002f899a0 rbp=fffff88002f89a30
 r8=48dd6f4b988e70e0  r9=00000000646e5344 r10=fffff88008b1c280
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a7f905 498b08          mov     rcx,qword ptr [r8] ds:0001:48dd6f4b`988e70e0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b0ebdb to fffff80002a7c740

STACK_TEXT:  
fffff880`02f88798 fffff800`02b0ebdb : 00000000`0000001e ffffffff`c0000005 fffff880`02f88850 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f887a0 fffff800`02acdd30 : fffffa80`0800e920 fffff800`02a44f7a fffffa80`0800e920 00000000`00000001 : nt!KipFatalFilter+0x1b
fffff880`02f887e0 fffff800`02aaad1c : 00000000`00000000 fffff880`02f88f30 fffff880`02f88a01 fffff880`02f88f58 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`02f88820 fffff800`02aa240d : fffff800`02bc8bc4 fffff880`02f8aec0 00000000`00000000 fffff800`02a0c000 : nt!_C_specific_handler+0x8c
fffff880`02f88890 fffff800`02aa9a90 : fffff800`02bc8bc4 fffff880`02f88908 fffff880`02f89768 fffff800`02a0c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f888c0 fffff800`02ab69ef : fffff880`02f89768 fffff880`02f88fd0 fffff880`00000000 fffffa80`00000005 : nt!RtlDispatchException+0x410
fffff880`02f88fa0 fffff800`02a7bd82 : fffff880`02f89768 fffff880`08b1c280 fffff880`02f89810 fffffa80`06ad7790 : nt!KiDispatchException+0x16f
fffff880`02f89630 fffff800`02a7a68a : fffff880`02f89dd1 fffffa80`04c3ac60 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f89810 fffff800`02a7f905 : fffff880`08b1c280 fffff880`08ae21cc 00000000`00000001 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f899a0 fffff880`08ae21cc : 00000000`00000001 00000000`00000001 fffff880`02f89a30 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16
fffff880`02f899b0 fffff880`08ae6142 : 00000000`00000001 fffffa80`07c45f10 00000000`00000000 fffffa80`07427010 : nwifi!Dot11AllocateSendPacket+0x58
fffff880`02f899e0 fffff880`08ae651b : fffffa80`07427010 00000000`00000000 fffffa80`07427010 00000000`00000000 : nwifi!MP6SendOneNBL+0x262
fffff880`02f89b30 fffff880`08aebf67 : 00000000`00000302 fffffa80`07c45d30 00000000`00000000 00000000`00000000 : nwifi!MP6SendNBLInternal+0x67
fffff880`02f89b80 fffff880`016e7af4 : fffffa80`04fd7270 00000000`00000001 00000000`00000000 fffffa80`04c3ac60 : nwifi!FilterSendNetBufferLists+0x7f
fffff880`02f89bb0 fffff880`040de199 : fffffa80`07c45d30 fffffa80`05d871a0 00000000`00000000 fffff880`02f89ca0 : ndis!NdisFSendNetBufferLists+0x64
fffff880`02f89bf0 fffff880`016e7a39 : 00000000`00000001 00000000`00000000 fffffa80`079e8080 00000000`00000011 : pacer!PcFilterSendNetBufferLists+0x29
fffff880`02f89cf0 fffff880`017a3785 : fffff880`0681a625 00000000`00000000 fffffa80`05d871a0 fffff880`02f8a200 : ndis!ndisSendNBLToFilter+0x69
fffff880`02f89d50 fffff880`0186634e : 00000000`00000000 00000000`0000000e fffffa80`07419410 fffffa80`079e8080 : ndis!NdisSendNetBufferLists+0x85
fffff880`02f89db0 fffff880`01867a67 : fffff880`0196c9a0 00000000`00000000 fffffa80`077a0000 00000000`01960800 : tcpip!IppFragmentPackets+0x39e
fffff880`02f89ed0 fffff880`018637d5 : 00000000`00000000 00000000`00000000 00000054`00000320 00000000`0000000e : tcpip!IppDispatchSendPacketHelper+0x87
fffff880`02f89f90 fffff880`01865124 : fffffa80`081f9006 00000000`00009900 fffffa80`00000014 00000000`00000000 : tcpip!IppPacketizeDatagrams+0x2d5
fffff880`02f8a0b0 fffff880`0186a1ee : fffffa80`04bb0f00 fffffa80`0827b007 fffff880`0196c9a0 fffffa80`081f9010 : tcpip!IppSendDatagramsCommon+0x754
fffff880`02f8a380 fffff880`0185ce2a : fffffa80`0827b010 00000000`00000000 00000000`00000001 00000000`00000002 : tcpip!IpNlpSendDatagrams+0x3e
fffff880`02f8a3c0 fffff880`018791f7 : 00000000`0000c97b ffff0000`036ec5f5 fffffa80`00000002 fffffa80`0741d860 : tcpip!TcpTcbHeaderSend+0x5ea
fffff880`02f8a570 fffff880`01874a56 : 00000000`00000000 fffffa80`04ba7000 fffff880`01966128 fffff880`01840ac2 : tcpip!TcpTcbSend+0x807
fffff880`02f8a7f0 fffff880`0187c44c : fffff880`06968000 00000000`00000000 00000000`00000000 fffff880`0185f700 : tcpip!TcpFlushDelay+0x316
fffff880`02f8a8d0 fffff880`0185e6c7 : fffffa80`04ba998c fffffa80`04bcb9b0 fffffa80`04bb998c 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x20c
fffff880`02f8a980 fffff880`0185e799 : fffff880`02f8ab00 fffff880`0196c9a0 fffff880`02f8ab10 fffffa80`04a00ad0 : tcpip!IppDeliverListToProtocol+0x97
fffff880`02f8aa40 fffff880`0185ec90 : fffffa80`075c9cb0 fffffa80`081a6b00 00000000`00000011 fffff880`02f8ab00 : tcpip!IppProcessDeliverList+0x59
fffff880`02f8aab0 fffff880`0185db21 : 00000000`6401a8c0 fffffa80`04ba7000 fffff880`0196c9a0 00000000`07419401 : tcpip!IppReceiveHeaderBatch+0x231
fffff880`02f8ab90 fffff880`0185c592 : fffffa80`07415a30 00000000`00000000 fffffa80`07419401 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff880`02f8ad90 fffff880`01875e5a : fffffa80`07419410 fffff880`02f8aec0 fffffa80`07419410 fffff880`01960000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`02f8ae70 fffff800`02a8be5a : fffffa80`075c9cb0 fffff880`02f86000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`02f8aec0 fffff880`01875882 : fffff880`01875d80 fffff880`02f8afd0 fffffa80`07c45d02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`02f8afa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Dot11AllocateSendPacket+58
fffff880`08ae21cc 4885c0          test    rax,rax

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  nwifi!Dot11AllocateSendPacket+58

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b

FAILURE_BUCKET_ID:  X64_0x1E_nwifi!Dot11AllocateSendPacket+58

BUCKET_ID:  X64_0x1E_nwifi!Dot11AllocateSendPacket+58

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

The dumps blames nwifi.sys and points to memory corruption. This is a hardware/hardware related error. Usually this is related to a network adapter/driver problem.

I find the following out of date drivers on your system:

AnyDVD.sys Thu Apr 09 20:40:36 2009 - AnyDVD Filter Driver or Watch & copy any DVD! belongs to the software AnyDVD by SlySoft, Inc (www.slysoft.com). Update the driver or the software or uninstall it.

BCM42RLY.sys Tue Jul 07 20:34:55 2009 - Broadcom iLine10(tm) PCI Network Adapter Proxy Protocol Driver belongs to the software BCM42RLY or Broadcom iLine10(tm) PCI Network Adapter by Broadcom Corporation (www.broadcom.com). I suspect this driver had a lot to do with your crash. Update this driver

e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver. Update this driver.

ElbyCDIO.sys Tue Feb 17 12:11:23 2009 - ElbyCD Windows NT/2000/XP I/O driver or ElbyCD Windows NT/2000 I/O driver belongs to the software CDRTools or ElbyCDIO Driver or DVD Region Killer or VirtualCloneDrive by Elaborate Bytes AG (www.elby.ch). Update the driver or the software or uninstall the software.

rimspx64.sys Mon Mar 03 04:19:03 2008 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com This driver is very obsolete. If you cannot update the driver, upgrade your card reader to one that is certified Win 7 compatible.

rixdpx64.sys Fri Jul 27 06:45:50 2007 - See above.

Update these drivers from the manufacturers' websites. Win 7 does not like older drivers. They can and do cause memory corruption. Reboot and run your system and lets see if you have another crash. If you do, upload that BSOD file to us. And we will go from there. If your system runs smoothly, please let us know that, too. If you need help with the drivers, please post and ask.

By the way, we do prefer that you use zip instead of RAR.

What antivirus and firewall are you running?

 

[cluberti]

2: kd> r
Last set context:
rax=0000002a81940007 rbx=0000000000000000 rcx=fffff88008b1c280
rdx=48dd6f4b988e70e1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a7f905 rsp=fffff88002f899a0 rbp=fffff88002f89a30
 r8=48dd6f4b988e70e0  r9=00000000646e5344 r10=fffff88008b1c280
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=0001  es=0000  fs=0000  gs=0000             efl=00010202
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a7f905 498b08          mov     rcx,qword ptr [r8] ds:0001:48dd6f4b`988e70e0=????????????????

2: kd> .formats 48dd6f4b988e70e0
Evaluate expression:
  Hex:     48dd6f4b`988e70e0
  Decimal: 5250475111056568544
  Octal:   0443353364563043470340
  Binary:  01001000 11011101 01101111 01001011 10011000 10001110 01110000 11100000
  Chars:   H.oK..p.
  Time:    Mon Feb  4 14:51:45.656 18239 (GMT-4)
  Float:   low -3.68201e-024 high 453498
  Double:  1.02565e+043

If I had a full dump I could search the dump to see who or what is writing the string H.oK..p. Someone or something is writing this over what appears to otherwise likely have been a list head, corrupting what I am making an educated guess at was supposed to be the packet data the mini filter was looking to send. Driver verifier might help here, but I think Carl is right on when he pinpointed your network drivers should be updated - this is a network stack crash, and thus updating your network drivers (especially considering this appears to be traffic over WiFi at the time of the crash) would be the best course of action right now.

 

[sawwei]

What antivirus and firewall are you running?

I am running a Microsoft Essential Antivirus with no firewall on Homegroup LAN.
I will usually go to the Dell Alienware support site to keep myself updated with the latest drivers.
All of the drivers installed on my system are all current, at least according to their support page.
I did try to find a newer Video driver in the NVIDIA website, but when I installed it my screen resolutions got all weird up and also the color looks horrible.
So I changed back to the driver given on the dell's support page and everything was back to normal.
What do you suggest I should do about this driver thing ?
I consider myself as a person who likes the system to be always updated, but sometimes the latest drivers gives me lots of problems as well.
Thanks a lot for your detailed explanations...

 

[cluberti]

Honestly, I'd be calling Dell and making them handle this. Most folks here have homebrew machines and don't have an OEM to go to when things fail, but assuming this is still under warranty I'd be harassing them for a better Win7 driver.

 

[sawwei]

Honestly, I'd be calling Dell and making them handle this. Most folks here have homebrew machines and don't have an OEM to go to when things fail, but assuming this is still under warranty I'd be harassing them for a better Win7 driver.

Well, I've been thinking about doing that for a while now, but honestly I don't think Dell will be able to provide me with better drivers than those that they posted on their support page.
I had all of those drivers installed on my system, yet I am still experiencing this BSOD.
I can help but think that maybe their system is not stable enough to handle all this stuffs.

 

[cluberti]

Well, Dell can put a lot more pressure on vendors to fix drivers than you can.

 

[CarlTR6]

What antivirus and firewall are you running?

I am running a Microsoft Essential Antivirus with no firewall on Homegroup LAN.
I will usually go to the Dell Alienware support site to keep myself updated with the latest drivers.
All of the drivers installed on my system are all current, at least according to their support page.
I did try to find a newer Video driver in the NVIDIA website, but when I installed it my screen resolutions got all weird up and also the color looks horrible.
So I changed back to the driver given on the dell's support page and everything was back to normal.
What do you suggest I should do about this driver thing ?
I consider myself as a person who likes the system to be always updated, but sometimes the latest drivers gives me lots of problems as well.
Thanks a lot for your detailed explanations...

You are very welcome. MSE is good; continue to use it. If you wish, you can enable Windows Firewall. It will not cause system conflicts.

NVidia drivers are interesting. I had to try five before I could get my video card and system working properly. I ended up using the third or fourth one down the list. I can confirm that the latest drivers from NVidia are not always the best.

The big question here is your Broadcom driver and the Intel driver. Are these the ones you could not update? You did properly by going to the Dell website. Many times, laptop manufactures modify the manufactures' drivers for the particular laptop systems. Sometimes, however, you have to try the manufactures' sites.

Honestly, I'd be calling Dell and making them handle this. Most folks here have homebrew machines and don't have an OEM to go to when things fail, but assuming this is still under warranty I'd be harassing them for a better Win7 driver.

Cluberti is spot on and I thank him for the backup and his observations. But it is Dell that needs to make this right. Unfortunately, too many times, hardware manufacturers choose not to go to the expense of updating drivers. They would rather sell upgraded hardware. Planned obsolescence.

Did you try to see if the Broadcom site has an updated driver? Or the Intel site?

 

[sawwei]

From your explanations above, you did not mention any Intel driver that I should look into or did you ?
I tried to access the Broadcom site but it was very confusing and I tried to use their search engine to look for my driver but it returned with no result.
When I search the web for the Broadcom driver that suits my system, I found that my driver is the latest one.
I have removed some other drivers/softwares you mentioned in the report above, since I think I don't need them anyway.(eg.ANYDVD, Region DVD Killer, etc)

 

[CarlTR6]

Good job on removing the obsolete software. Here is the driver I was talking about:

e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver

Were you able to update this one? Actually, removing/uninstalling the card reader may be enough to give you a stable system. But the dump does point to the network adapter/drivers. Check this link and see what you can find: Broadcom.com - Ethernet NIC Driver Downloads

Have you had any more BSOD's since the one you uploaded? If not let your system run. If you get another BSOD, upload it to us and then enable Driver Verifier. Upload any Driver Verifier enabled dumps.

Driver Verifier - Enable and Disable

 

[sawwei]

e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver

Were you able to update this one?
Have you had any more BSOD's since the one you uploaded? If not let your system run. If you get another BSOD, upload it to us and then enable Driver Verifier. Upload any Driver Verifier enabled dumps.

I wasn't able to find a better driver than the one installed on my system.
I also have not experienced more BSOD since my upload, and hopefully it stays that way...
Carl, I think I found what caused all of those problem I'm having.
First of all it was because when you log into Dell Alienware's support page, you need to log in with your Service Tag Number, and then they will redirect you to the support page that suitable for your system needs.
Because of that, I thought that every single one of the drivers on that page were needed by my system.
Later on I thought that since Alienware is a custom build notebook, than the drivers could have been for other hardwares that weren't even in my notebook.
My network adapter is Intel 82577LM Gigabit LAN, and I installed both the drivers for that adapter and Broadcom's WLAN adapter. I think those two drivers caused the system conflict, hence resulted in the BSOD. Do you think this was the cause, Carl ?

 

[CarlTR6]

Yes, I think so. The stack in your BSOD analysis is a network stack crash; so your network adapter and wi-fi adapter were involved in the crash. Such can easily be caused by a faulty or old driver.

I surely hope the drivers have fixed your problem. It is good to hear that you have not had another BSOD. Report back to us in a couple of day and let us know how your system is doing. I hope we can mark the thread as solved. Of course if you have another crash, upload the dump file to us. Good luck and happy computing.

 

[sawwei]

Hi Carl,

I haven't got a BSOD since that last one, but I actually did a System Recovery last Saturday and it was because my Wi-Fi can' connect to my wireless router at home.
It detected the connection but can't connect to it. Even after the System Recovery, I still could not connect the WLAN. I thought there must have been some problem with my WLAN hardware, but after a while I managed to connect it. I am hoping that I will not have a hardware related problems, since I hate it to send it back to the manufacturer.
When everything ran smoothly I decided to back up my system, just in case if I had another problems in the future. Hopefully I would not need them....
Thanks so much for helping me solving my problems.

 

[CarlTR6]

That is news we love to hear!! You are very welcome and thank you for reporting back. We will ask the moderators to mark this one as solved. Happy Computing.

 

[sawwei]

Hi Carl,

The BSOD happened again this morning !!!
I attached the dump files.