Constant BSOD problem

Discussion in 'Alienware M15x' started by redvyper, Oct 19, 2010.

Thread Status:
Not open for further replies.
  1. redvyper

    redvyper Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    5
    Hello all,

    I am a bit of a lurker on these forums – I've done much browsing here in the past year while researching laptops and solutions for my current laptop.

    Back in March I received my purchased Alienware MX15, a laptop I bought with the purpose of being very reliable for school projects and casual gaming on the side to keep my sanity.

    A month after the laptop reached my home, before I even started taking it to school (I didn't hav suitable laptop carrying pack for it yet), it started getting random BSODs. Sometimes after one hour of operation, sometimes after three hours. These occurred while the computer was plugged into the wall and on battery mode. Typically I am just browsing the internet using Chrome or typing up a paper using OpenOffice when it blue screens.

    I attached a dxdiag.text with my computer specs and driver info.

    Note that following some suggestions I've seen on these forums and others, I've tried reinstalling my video card drivers and wireless card drivers (on another forums, they were causing another person frequent BSODs). I don't believe I have tried reinstalling or updating my motherboard drivers. I did flash my BIOS to AO5. A while ago I removed my synaptics touchpad drivers in order to fix the cursor stuttering.

    A log of one of my recent minidumps is as follows:

    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e53000 PsLoadedModuleList = 0xfffff800`03090e50
    Debug session time: Tue Sep 28 12:42:10.366 2010 (UTC - 7:00)
    System Uptime: 0 days 0:43:28.912
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {8, 80050031, 6f8, fffff80002e8bec0}

    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff80002e8bec0

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


    BUGCHECK_STR: 0x7f_8

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from fffff80002ec2ca9 to fffff80002ec3740

    STACK_TEXT:
    fffff880`02fdbce8 fffff800`02ec2ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`02fdbcf0 fffff800`02ec1172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02fdbe30 fffff800`02e8bec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`02ff7c80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiDoubleFaultAbort+b2
    fffff800`02ec1172 90 nop

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

    FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

    BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

    Followup: MachineOwner


    Using the program “Who Crashed?” here's a condensed profiling of my last couple of BSODs in September:

    On Tue 9/28/2010 7:43:08 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E8BEC0)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    Dump file: C:\Windows\Minidump\092810-24211-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Thu 9/23/2010 8:09:40 PM your computer crashed
    This was likely caused by the following module: nvlddmkm.sys
    Bugcheck code: 0xD1 (0xFFFFEC617E0DE04D, 0x2, 0x8, 0xFFFFEC617E0DE04D)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\092310-18486-01.dmp
    file path: C:\Windows\system32\drivers\nvlddmkm.sys
    product: NVIDIA Windows Kernel Mode Driver, Version 258.96
    company: NVIDIA Corporation
    description: NVIDIA Windows Kernel Mode Driver, Version 258.96



    On Tue 9/21/2010 11:18:00 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E40EC0)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    Dump file: C:\Windows\Minidump\092110-25178-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 9/21/2010 6:59:03 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002E9BEC0)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    Dump file: C:\Windows\Minidump\092110-19422-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



    On Tue 9/14/2010 7:01:56 PM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000315274D, 0xFFFFF880031CABA8, 0xFFFFF880031CA410)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    Dump file: C:\Windows\Minidump\091410-23134-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.




    [my laptop usuage is infrequent right now]


    If anyone had any suggestions (or questions), I would be very much appreciative. Fortunately I have the advanced warranty from Dell on this computer; I've just wanted to try and see if this was something simple I could fix before calling them. Or should I just call them and not bother trying to fix it on my own?

    Also, I happen to have the issue as some others where I can't put the laptop to sleep without it crashing. (I know, it sounds like my laptop needs a pacifier..)

    Thanks,
    redvyper

    [Oh and yes, I've tried completely draining the battery and seeing if that fixed it ;) ]
     

    Attached Files:

  2. ElectricTurtle

    ElectricTurtle Notebook Consultant

    Reputations:
    103
    Messages:
    189
    Likes Received:
    2
    Trophy Points:
    31
    I read your post and your attached file. I know this may sound a little bit dumb but are you sure that your nvidia driver is current and downloaded from nvidia ??? Also, you may want to make sure the driver is win7 ver and a x64 one
     
  3. redvyper

    redvyper Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    5
    I played around with the display drivers for a bit; I believe a few months ago I updated to the latest graphics card drivers to see if that would fix the issue. I read on a few places on how the dell/180.6 (I think that's the version?) were the most stable and at one point reverted the drivers back to that version. None of that seemed to affect the bluescreening anyway. Though that is weird that it's showing up as "vista." The driver file though from nvidia says "_winvista_win7_" so maybe it's how they named it?

    Edit: Has to be a naming thing, when I went to install the new drivers 260.89 drivers, this unpackaging path appeared: C:\NVIDIA\DisplayDriver\260.89\Vista 64-bit\International

    Edit #2: I've gotten the newer drivers from Nvidia's website because the download link for the video card driver's on Dell's website never works for me, I typically get something like this "This webpage is not found.

    No webpage was found for the web address: ftp://ftp.us.dell.com/video/nVidia_GeForce-GT-240M_A01_R279496.exe"
     
  4. ElectricTurtle

    ElectricTurtle Notebook Consultant

    Reputations:
    103
    Messages:
    189
    Likes Received:
    2
    Trophy Points:
    31
    I didn't mean yours was a vista driver, just want to make sure. My old Dell had the same problem with nvidia driver and updating it seemed to reduce the frequency of bsod. So if I were u I'd go to nvidia's website and try the latest driver (again) to make sure that your bsod is not caused by nvidia driver

    Edit: how about your antivirus and firewall??? I did some research and found several reasons for your bsod: 3rd party firewall, ram, hard drive... So don't bother fixing it, just call Dell and leave the burden for them to bear lol :D
     
  5. Wattos

    Wattos Notebook Deity

    Reputations:
    968
    Messages:
    1,200
    Likes Received:
    3
    Trophy Points:
    55
    Did you double check you ram? faulty ram causes random bsod. Either run memtest or inbuilt diagnostics to make sure its not the ram.
     
  6. redvyper

    redvyper Newbie

    Reputations:
    0
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    5
    I ran memtest86 overnight and a bad address popped up though I am a little confused on how it was reported.


    The address 0007cad2494 - 1994.8MB (I'm assuming that means the 2nd memory stick since I believe this has 4 one gigabyte memory sticks in it) is shown as failing three times on the 3rd pass (or Count Chan of 1, 2, and 3). Does this mean that there is one bad location on the ram or multiple? Just asking before I call up dell.

    (Thanks for the suggestion by the way)
    (I have the program still running since it only found the error on its 3rd pass; I'm on my 8th pass right now)
     
  7. Wattos

    Wattos Notebook Deity

    Reputations:
    968
    Messages:
    1,200
    Likes Received:
    3
    Trophy Points:
    55

    To be sure which memstick this is, remove one and run the test and then remove the other one and run the test. Then you know which is broken. In any case, have dell replace the memory (they will most likely replace both sticks). You should never run into an error when running memtest.

    Also, can you run onboard diagnostics (F12 on bootup). Dell will most likely want you to run that instead of memtest.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page