1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved Alienware m15x (older model) BSOD investigation

Discussion in 'Windows 7' started by Crishu, 2010/10/08.

  1. 2010/10/08
    Crishu

    Crishu Inactive Thread Starter

    Joined:
    2010/10/08
    Messages:
    4
    Likes Received:
    0
    Hello,

    A frined of mine asked me to help him with an Alienware m15x laptop that had a little service history.

    It was bought in june 2008, serviced in january 2009 for a random fps drop problem, Alienware returned it saying nothing was wrong. The laptop still had hiccups, but after juggling a few drivers and settings, the fps drops weren't as noticeable.

    Eventually it died in Sept. 2009. It would not boot up locking itself on a white/gray screen. (i think it was overheating .. clocking in 100 degrees Celsius). So back to Alienware it went. They replaced the GPU and all was fine during the next months. Up until these blue screens started showing up, in August.

    The one thing that changed was his HDD, which he upgraded to 320gb from 120. He also installed a fresh copy of Windows 7 HoPr. From then on it seems to have started its BSOD. Could this be the culprit? 0_o

    The laptop originaly came with Windows was Vista but it was upgraded with a digital download/purchase of Windows 7 Home Premium and activated after a fresh installation . No constant errors on the old HDD, just on the latest installation. Due note that now the old HDD is used to see if issues re-occur.

    So please, I am in need of someone who can interpret these windows dump files: Minidump

    I may have come to some conflicting conclusions. So if someone can clarify each dump/date and the probable cause/error it had; and a final conclusion or solution, we would be very grateful.

    Also please consult report for other system info I omitted: everest_report

    If I missed something or if you have any other questions I'll be happy to answer them.

    Thank you. Good day.

    PS: i think that these specifications are from the first Win7 HDD installation, so some drivers may differ.
    I'll post the other report when i get it.

    Processor:
    Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz
    Voltage 3.3 V

    Video Adapter Properties:
    Driver Description NVIDIA GeForce 8800M GTX
    Driver Date 19.08.2009
    Driver Version 8.16.11.8681
    INF File oem19.inf
    Hardware ID PCI\VEN_10DE&DEV_060C&SUBSYS_0770152D&REV_A2
    Location Information @system32\DRIVERS\pci.sys,#65536;PCI bus %1, device %2, function %3;(1,0,0)
    PCI Device NVIDIA GeForce 8800M GTX [NoDB]
    BIOS String Version 62.92.34.0.8
    Video BIOS Date 01/27/08
    Installed Drivers nvd3dum (8.16.11.8681), nvwgf2um, nvwgf2um
    DirectX 4.09.00.0904 (DirectX 9.0c)

    Memory Device Properties:
    Form Factor SODIMM
    Type Detail Synchronous
    Size 2 x 1024 MB
    Speed 667 MHz
    Total Width 64-bit
    Data Width 64-bit
    Device Locator M2
    Bank Locator Bank 1
    Manufacturer Mfg 1
    Serial Number 1234-B1
    Part Number SODIMM001

    Hard Dik Drive:
    Model ID ST9120823ASG (**older one 120gb** with first win7)
    Driver Date 21.06.2006
    Driver Version 6.1.7600.16385
    Driver Provider Microsoft
    INF File disk.inf

    Model ID WD32000BEKT (new 320gb with fresh wjn7)

    Network:
    Network Adapter Broadcom NetLink (TM) Gigabit Ethernet
    Network Adapter Hamachi Network Interface
    Network Adapter Intel(R) Wireless WiFi Link 4965AG

    BIOS Properties:
    Vendor Quanta
    Version vX36 P3
    Release Date 08/29/2008

    Here are the dumps in order of occurrence from the general and detailed view (only highlighted ones) of BlueScreenViewer. Note these happened on the second HDD.

    01) 081610-40763-01.dmp 16/08/2010 12:35:40 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x00000000 0x00000002 0x00000008 0x00000000 tcpip.sys tcpip.sys+76b9d
    ntkrnlpa.exe ntkrnlpa.exe+4682b 0x82853000 0x82c63000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    tcpip.sys tcpip.sys+76b9d 0x8902f000 0x89178000 0x00149000 0x4c15a3db 14/06/2010 6:36:59 AM
    02) 082110-35396-01.dmp 21/08/2010 9:50:33 PM BAD_POOL_CALLER 0x000000c2 0x00000007 0x00001097 0x82d40a00 0x82d40a08 ntkrnlpa.exe ntkrnlpa.exe+11f1b6
    ewusbnet.sys ewusbnet.sys+235e 0x9ce44000 0x9ce79000 0x00035000 0x4b1ce833 07/12/2009 2:34:11 PM
    halmacpi.dll halmacpi.dll+3700 0x8301b000 0x83052000 0x00037000 0x4a5bbf07 14/07/2009 2:11:03 AM
    ndis.sys ndis.sys+c651 0x88f3a000 0x88ff1000 0x000b7000 0x4a5bbf58 14/07/2009 2:12:24 AM
    ntkrnlpa.exe ntkrnlpa.exe+135a00 0x82c0b000 0x8301b000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    03) 082110-33992-01.dmp 21/08/2010 9:53:19 PM BAD_POOL_HEADER 0x00000019 0x00000022 0x00000000 0x00000000 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+9dd99
    ewusbnet.sys ewusbnet.sys+235e 0x8d0da000 0x8d10f000 0x00035000 0x4b1ce833 07/12/2009 2:34:11 PM
    ndis.sys ndis.sys+c651 0x89291000 0x89348000 0x000b7000 0x4a5bbf58 14/07/2009 2:12:24 AM
    ntkrnlpa.exe ntkrnlpa.exe+3c848 0x82c4a000 0x8305a000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    04) 082110-33087-01.dmp 21/08/2010 9:56:35 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e 0xc0000005 0x82d6f46a 0x96dffb30 0x96dff710 ndis.sys ndis.sys+c651
    ewusbnet.sys ewusbnet.sys+235e 0x8f2ba000 0x8f2ef000 0x00035000 0x4b1ce833 07/12/2009 2:34:11 PM
    halmacpi.dll halmacpi.dll+3700 0x82c19000 0x82c50000 0x00037000 0x4a5bbf07 14/07/2009 2:11:03 AM
    ndis.sys ndis.sys+c651 0x89278000 0x8932f000 0x000b7000 0x4a5bbf58 14/07/2009 2:12:24 AM
    ntkrnlpa.exe ntkrnlpa.exe+11f46a 0x82c50000 0x83060000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    05) 082310-32619-01.dmp 23/08/2010 1:34:25 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x00000000 0x00000002 0x00000001 0x93102c5f dxgmms1.sys dxgmms1.sys+cc5f
    dxgmms1.sys dxgmms1.sys+cc5f 0x930f6000 0x9312f000 0x00039000 0x4a5bc265 14/07/2009 2:25:25 AM
    halmacpi.dll halmacpi.dll+5ba9 0x83019000 0x83050000 0x00037000 0x4a5bbf07 14/07/2009 2:11:03 AM
    ntkrnlpa.exe ntkrnlpa.exe+4682b 0x82c09000 0x83019000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    06) 091510-32463-01.dmp 15/09/2010 9:49:00 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e 0xc0000005 0x8eef7bb5 0x969579e8 0x969575c0 dxgmms1.sys dxgmms1.sys+16bb5
    dxgmms1.sys dxgmms1.sys+16bb5 0x8eee1000 0x8ef1a000 0x00039000 0x4a5bc265 14/07/2009 2:25:25 AM
    halmacpi.dll halmacpi.dll+ca73 0x82c1e000 0x82c55000 0x00037000 0x4a5bbf07 14/07/2009 2:11:03 AM
    07) 091610-35568-01.dmp 16/09/2010 3:18:25 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x82c8ef21 0x98120a94 0x00000000 cdd.dll cdd.dll+72c9
    cdd.dll cdd.dll+72c9 0x98d40000 0x98d5e000 0x0001e000 0x00000000
    ntkrnlpa.exe ntkrnlpa.exe+8af21 0x82c04000 0x83014000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    watchdog.sys watchdog.sys+107e 0x8df62000 0x8df6f000 0x0000d000 0x4a5bc21a 14/07/2009 2:24:10 AM
    win32k.sys win32k.sys+cd37c 0x98ab0000 0x98cfa000 0x0024a000 0x4c1c425a 19/06/2010 7:06:50 AM
    08) 092210-32760-01.dmp 22/09/2010 9:44:03 PM KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000005 0x82cc2f21 0xa8273a94 0x00000000 cdd.dll cdd.dll+72c9
    cdd.dll cdd.dll+72c9 0x98d00000 0x98d1e000 0x0001e000 0x00000000
    ntkrnlpa.exe ntkrnlpa.exe+8af21 0x82c38000 0x83048000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    watchdog.sys watchdog.sys+107e 0x8dd5b000 0x8dd68000 0x0000d000 0x4a5bc21a 14/07/2009 2:24:10 AM
    win32k.sys win32k.sys+cd37c 0x98a70000 0x98cba000 0x0024a000 0x4c1c425a 19/06/2010 7:06:50 AM
    09) 092810-31730-01.dmp 28/09/2010 5:01:18 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x42d38a4c 0x00000002 0x00000001 0x82c681b9 nvlddmkm.sys nvlddmkm.sys+955c5
    halmacpi.dll halmacpi.dll+392d 0x83011000 0x83048000 0x00037000 0x4a5bbf07 14/07/2009 2:11:03 AM
    ntkrnlpa.exe ntkrnlpa.exe+126a3c 0x82c01000 0x83011000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    nvlddmkm.sys nvlddmkm.sys+955c5 0x8f22b000 0x8fb8aa00 0x0095fa00 0x4a8d10b0 20/08/2009 12:00:32 PM
    10) 092910-32682-01.dmp 29/09/2010 8:15:14 PM 0x00000119 0x07000000 0x89f0b788 0x852b2700 0x87ad76e8 watchdog.sys watchdog.sys+1276
    dxgmms1.sys dxgmms1.sys+795a 0x92ef4000 0x92f2d000 0x00039000 0x4a5bc265 14/07/2009 2:25:25 AM
    ntkrnlpa.exe ntkrnlpa.exe+676c5 0x82c08000 0x83018000 0x00410000 0x4c1c3fac 19/06/2010 6:55:24 AM
    watchdog.sys watchdog.sys+1276 0x8d77a000 0x8d787000 0x0000d000 0x4a5bc21a 14/07/2009 2:24:10 AM
    11) 100410-32183-01.dmp 04/10/10 01:51 PM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0x0000000d 0x00000000 0x00000000 0x00000000 HIDCLASS.SYS HIDCLASS.SYS+33fd
    HIDCLASS.SYS HIDCLASS.SYS+33fd 0x95d04000 0x95d17000 0x00013000 0x4a5bc865 14/07/2009 2:51:01 AM
     
    Last edited: 2010/10/08
  2. 2010/10/08
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,680
    Likes Received:
    104
    If you want help, you'll need to post the information here.

    Run the dump file through BlueScreenView and look for the files highlightesd in pink in the results window - as shown on their site and post them here.

    See this link on how to enter your System Details.
     

  3. to hide this advert.

  4. 2010/10/12
    Crishu

    Crishu Inactive Thread Starter

    Joined:
    2010/10/08
    Messages:
    4
    Likes Received:
    0
    Thank you for your reply.
    I have edited the first post, regarding your recommendation.
    So, can anyone spot something that could point to the HDD being the culprit?
     
  5. 2010/10/12
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    With BSOD's all over the place I would suggest starting with updating all your drivers and BIOS.
     
    Arie,
    #4
  6. 2010/10/20
    Crishu

    Crishu Inactive Thread Starter

    Joined:
    2010/10/08
    Messages:
    4
    Likes Received:
    0
    Thank you for your reply.

    I have instructed my frined to do another clean install and will aid him as best as i can in choosing the latest and/or best drivers for his laptop (Alienware Area-51 m15x - it's a tricky machine with lots of troubleshooting threads )

    With the old hard drive there was only one consistent blue screen till now, but no minidups were generated, not sure why. I'll post the details if get them. Better yet i hope i can make him join the thread.
     
  7. 2010/10/21
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    OK, please keep us informed.
     
    Arie,
    #6
  8. 2010/11/09
    Crishu

    Crishu Inactive Thread Starter

    Joined:
    2010/10/08
    Messages:
    4
    Likes Received:
    0
    Alienware M15x Area 51 - M 8800 GTX

    The laptop is used pretty intensely and a reinstall required a well prepared multipronged action :D
    But we finally found some time to tackle the reinstall and now are awaiting results.

    I managed to run a Everest Stability Test along side a FurrMark test for about 10h (4pm-2am) and nothing notable. GPU hovered around 90C and CPU, ram, HDD were in normal parameters.
    Maybe I'll follow up with some 3dmark batches and he'll keep testing his usual games when he get's the chance.

    Current drivers are:
    1. Intel Chipset Drivers - Latest online drivers from Intel website
    2. NVIDIA Display Drivers - 186.81 win 7 32 bit, NVIDIA website (best one found, over 190+ are nogo)
    3. PhysX 9.09.0814
    4. Audio Drivers - Realtek, Win7_R254
    5. OSD Utility - M15x_OSD_Vista_00020 (Alienware)
    6. Synaptic Touchpad Drivers - Synaptics v14.0.3 Win7
    7. Media Card Reader Drivers - M15x_MediaReader_Vista_3.51.01
    8. Turbo Memory Drivers + Matrix Storage - Latest online drivers from Intel website
    9. Bluetooth Drivers - M15x_Bluetooth_vista_6.0.1.5100
    10. Latest DirectX

    Network drivers installed by Windows. After installing all Drivers, ran Windows Update.
     
  9. 2010/11/10
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,680
    Likes Received:
    104
    Thanks for your feedback. If the issue seems fixed, please mark your thread as 'Resolved'.

     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.