none
Blue Screen of Death - Windows 7 Pro RRS feed

  • General discussion

  • I've just received a new Dell E6510 64-bit one week ago with Windows 7 Pro on it.  With only patches from Microsoft installed, it blue screened on the first day after receiving it.  It blue screened again this morning when I disconnected from my office wireless network and brought up the Cisco VPN client.  Windows says it's checking for a solution after it blue screens and starts to boot again, but it never gives any information about a solution or cause after that.  I use this laptop with clients and don't want to experience a bsd while doing a presentation.  How can I get this resolved?
    Wednesday, October 13, 2010 1:44 PM

All replies

  • Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your Skydrive [1] and post a link here, so that I can look at the dumps with the debugger and to to see the cause of the crash.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, October 13, 2010 8:04 PM
  • Hi,

    The system goes to a blue screen because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).

     

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

     

    If you are outside the US please see http://support.microsoft.com for regional support phone numbers.

     

    I hope the problem will be resolved soon. Thanks!

     

    Regards,

    Alex Zhao

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, October 15, 2010 9:25 AM
    Moderator
  • Thanks, Andre

    Here are the three DMP files from the latest BSDs that I've had. 

     

    http://cid-4dcc3553ec85bb59.office.live.com/self.aspx/Dell%20E6510%20DMP%20Files

     

    Travis

     

    Saturday, October 23, 2010 12:35 PM
  • You have 2 crashes of this type:

    Bug Check 0xFE: BUGCODE_USB_DRIVER - This indicates that an error has occurred in a Universal Serial Bus (USB) driver.

    1 with this:
    Arguments:
    Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB

    1 with this:
    Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver - A hardware failure has occurred due to a bad physical address found in a hardware data structure. This is not due to a driver bug.

    but the debugger doesn't get the required symbols to debug this. You should check your USB ports for errors. Use other ports on your PC if possible. You should also contact Dell about it, because your Dell Latitude E6510 is too new, to have such issues.

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) - An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.

    caused by this driver:

        Image path: \SystemRoot\system32\DRIVERS\dne64x.sys
        Image name: dne64x.sys
        Timestamp:        Tue Nov 11 02:01:24 2008

    So update the driver, please.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, October 23, 2010 4:56 PM
  • thanks.  I'll try other USB ports and update the driver.
    Saturday, October 23, 2010 8:00 PM