BSOD on Dell Studio 15 1558

Page 1 of 6 123 ... LastLast

  1. Posts : 45
    Windows 7 Home Premium 64-Bit
       #1

    BSOD on Dell Studio 15 1558


    Recently I have been getting the annoying blue screen and crashes on my one month old Dell Studio 15.

    Attached are the minidumps from windows. I have ran whocrashed and it has not identified the issue, other that it points to a driver.

    I have not upgraded any drivers since getting the laptop new from dell, a little more than a month ago. I contacted their support and they were absolutely useless.

    But I did run their diagnostics immediately after the last crash and it came through clean. I ran the memory diagnostic 5 times, and the complete system diagnostic once, including the extended drive test. All were clean and the tests overall ran for 3.5-4 hours.

    I even ran the driver verifier yesterday and it did not detect anything. Since I do not know what do do with it, I turned it off for now.

    Any help is greatly appreciated. Thanks everyone
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    All three of your .dmp files are reporting the same cause... ntkrnlmp.exe.. As this is a core system file, we know that this is not the problem... Make sure that you have driver verifier enabled... this wlll stress the drivers, and should result in a BSOD... NOTE: It may take up to 36 hours to do, so be patient.. upload the new .dmp files when you get them...

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffffffffffffd0, 2, 1, fffff80002c7c2b0}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 45
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #3

    Can you advise on the correct procedure and options for enabling driver verifier?

    Also, how do I disable it?
    Thanks
      My Computer


  4. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #4

    run Verifier with these settings:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    To turn off DV--> verifier /reset
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    In addition to Tom's good advice, be sure to remove McAfee with this tool: http://download.mcafee.com/products/...tches/MCPR.exe

    Install MSE instead: www.microsoft.com/Security_Essentials/
      My Computer


  6. Posts : 45
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #6

    After my last post I had removed dell quickset and the system has been clean. Today I noticed that the function keys were not working and reinstalled the latest quickset. It crashed a few minutes ago, minidump attached

    I will be removing quickset again until this can be resolved
      My Computer


  7. Posts : 45
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #7

    Sorry I forgot to include the whocrashed report:

    On Fri Fri 7 30 2010 1:00:10 AM your computer crashed
    This was likely caused by the following module: ntoskrnl.exe
    Bugcheck code: 0xA (0x76DE2FD0, 0x2, 0x1, 0xFFFFF80002CE22B0)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Dump file: C:\Windows\Minidump\073010-22963-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 Computer


  8. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #8

    Tony, do you have a mini dump for this crash? If so please upload it. Never mind. I was just blind and didn't see it.
      My Computer


  9. Posts : 45
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #9

    Here is some additional info from event viewer:
    Event 1001, Windows Error Reporting
    Fault bucket X64_0xA_nt!IopDisassociateThreadIrp+9c, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0

    Event 1001, BugCheck
    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000076de2fd0, 0x0000000000000002, 0x0000000000000001, 0xfffff80002ce22b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 073010-22963-01.
      My Computer


  10. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #10

    I haven't seen Driver Verifier is on, can you please enable it so that we can know if there are any faulty drivers. Also, Mcafee is there, make sure you uninstall it as Jonathan King suggest to eliminate the cause.
      My Computer


 
Page 1 of 6 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:41.
Find Us