BSOD ntoskrnl.exe errors

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 7 64
       #1

    BSOD ntoskrnl.exe errors


    Hi

    I'm new to this forum. I have a DELL Studio XPS 8000 I7 (x64), which I've had for just a year. It worked fine for about 9 months, then 3 months ago started crashing randomly. This seemed to become more and more frequent.

    I tried several things.
    - Windows Update
    - chkdsk /r
    - Registry cleaner
    But none of these solved the problem.
    I then took a more drastic step and re-installed Windows 7 from the DELL-supplied media. Even this didn't resolve the problem. I then went through and updated all the drivers. No joy.

    After all this I assumed it must be a hardware fault, so I tried runing DELL Diagnostics (memory/hard-disk/fan etc) - all tests passed okay. I even did a 48-hour soak test on the memory access tests, with no failures. But as soon as I rebooted into windows it went BSOD again. Interestingly it seems rock-solid when running diagnostics - but unstable in Windows.

    Any help would be greatly appreciated!
    Please see attached files.

    Thanks and regards
    Rob
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2

    rlguildford said:
    Hi

    I'm new to this forum. I have a DELL Studio XPS 8000 I7 (x64), which I've had for just a year. It worked fine for about 9 months, then 3 months ago started crashing randomly. This seemed to become more and more frequent.

    I tried several things.
    - Windows Update
    - chkdsk /r
    - Registry cleaner
    But none of these solved the problem.
    I then took a more drastic step and re-installed Windows 7 from the DELL-supplied media. Even this didn't resolve the problem. I then went through and updated all the drivers. No joy.

    After all this I assumed it must be a hardware fault, so I tried runing DELL Diagnostics (memory/hard-disk/fan etc) - all tests passed okay. I even did a 48-hour soak test on the memory access tests, with no failures. But as soon as I rebooted into windows it went BSOD again. Interestingly it seems rock-solid when running diagnostics - but unstable in Windows.

    Any help would be greatly appreciated!
    Please see attached files.

    Thanks and regards
    Rob

    Hi Rob and welcome

    These BSOD's were caused by mcshield.exe which is part of your Macaffee AV. It should be removed and replaced with Microsoft security essentials.


    Also of note mcshield is causing a memory exception so I would like you to test y our memory as well just in case.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\012611-21949-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e50
    Debug session time: Wed Jan 26 15:31:19.080 2011 (GMT-5)
    System Uptime: 0 days 0:01:16.236
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {403, fffff68000096910, bff0000125ae2867, fffff68000099b10}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000000403, The subtype of the bugcheck.
    Arg2: fffff68000096910
    Arg3: bff0000125ae2867
    Arg4: fffff68000099b10
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_403
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  mcshield.exe
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

    Let us know if you need further assistance with this.
      My Computer


  3. Posts : 12
    Windows 7 64
    Thread Starter
       #3

    Many thanks JMH.
    I will do as you suggest and post back the results.
      My Computer


  4. Posts : 12
    Windows 7 64
    Thread Starter
       #4

    Update:

    I ran memtest86 for 2 hours and it didn't report any errors. Is two hours generally long enough?
    Having uninstalled Mcafee AV, and installed MS Security Essentials, the system is much more stable. I can even use it to do some work!

    I was beginning to think the problems were fully resolved but then I got another (different) BSOD yesterday evening - a SYSTEM_SERVICE_EXCEPTION in afd.sys (see attached). Can you shed any light on what caused this?

    Oh, I also got a strange error yesterday (before the BSOD) where the screen froze for a few seconds and then I got a message in the system tray informing me that the video driver had stopped responding, but had recovered. Could this be related?

    Many thanks
    Rob
      My Computer


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

    Hello,

    It appears that you uninstalled McAfee, yet drivers remain loaded in RAM:
    Code:
    mfehidk.sys  Wed Oct 06 15:55:49 2010 (4CACD445)
    mfenlfk.sys  Wed Oct 06 15:56:13 2010 (4CACD45D)
    mfewfpk.sys  Wed Oct 06 15:56:04 2010 (4CACD454)
    Run the McAfee removal tool, and make sure it's all cleaned up: How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

    I see your nVidia drivers are quite old:
    Code:
    nvlddmkm.sys Fri Jun 26 18:15:53 2009 (4A454899)
    That may be the cause of that latest bluescreen you got. Here are the latest drivers; please install them: NVIDIA DRIVERS 266.58 WHQL

    If that doesn't work, we'll have to start on some hardware diagnostics. I am not generally familiar with the Dell diagnostics, meaning I don't know how they compare to the ones I normally recommend. I am assuming they are not as good, though, because if they were, they'd be more popular than they currently are.

    For RAM, we recommend Memtest86; here is a guide: RAM - Test with Memtest86+

    I'd also suggest the Blend and Small FFTs Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Jan 28 02:46:08.030 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:12.232
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE
    SystemProductName = Studio XPS 8000
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  6. Posts : 12
    Windows 7 64
    Thread Starter
       #6

    Hi Jonathan

    Many thanks for your help. I'm very impressed with the level of help and expertise on this forum!

    I downloaded the McAfee removal tool and ran it - it seems to have done the needful.

    I also downloaded and installed the latest GeForce drivers, which seem to work fine. BTW, the drivers I had installed were the ones which Windows Device Manager told me were the latest, presumably there's a delay between a manufactuer creating a driver and MS deigning it the latest?

    I've already run memtest86 for a couple fo hours without fault. Do you recommend running it for a longer duration than that?

    The system seems pretty stable now. However, I woke up this morning to find the "System Repair" screen, which then went on to say that Windows was unable to repair itself. But I rebooted and it started okay. Looking at the event log, there was no BSOD this time, but there is this one interesting item:

    Code:
     
    Log Name: System
    Source: Microsoft-Windows-Kernel-Power
    Date: 30/01/2011 11:13:05
    Event ID: 41
    Task Category: (63)
    Level: Critical
    Keywords: (2)
    User: SYSTEM
    Computer: I7
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="Error">
    <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2011-01-30T11:13:05.880411200Z" />
    <EventRecordID>9014</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>I7</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="BugcheckCode">0</Data>
    <Data Name="BugcheckParameter1">0x0</Data>
    <Data Name="BugcheckParameter2">0x0</Data>
    <Data Name="BugcheckParameter3">0x0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>
    I was fast asleep at the time. Does this indicate a potential problem with the PSU?

    Thanks again for your valuable help and advice.
    Rob
      My Computer


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

    Windows Update is a strange beast. It rarely finds the absolute latest drivers; I don't know where it gets it drivers.

    As for Memtest86, it's probably best to run it for longer. Check out this thread earlier this week: [Win 7] BSOD randomly (PAGE_FAULT_IN_NONPAGED_AREA) - Tech Support Forum

    In short, the OP was consistently getting errors on Pass 7.

    That Kernel Power 41 error is a tough one to diagnose; often it is hardware (often PSU), sometimes it is software. Also, there is a chance it is not a recurring problem. Perhaps there was a voltage drop coming from the power company; only the computers are sensitive enough to that to notice. How likely is that, based on the reliability of your power company?
      My Computer


  8. Posts : 12
    Windows 7 64
    Thread Starter
       #8

    Thanks for the link. I ran memtest86+ for about 5 hours this afternoon, got past pass 7 without errors - so I think the RAM is probably fine.

    I'm note sure about the reliability of our power supply. I've no reason to suspect it's below par - I think a dodgy PSU is probably more likely (although the DELL diagnostics cheked the fan speeds etc and everything passed okay). I'll keep the PC switched on and see what happens tonight.

    It might be worth noting that all my PC problems began at about the same time as we began having building work done - which produced (and still does produce) a large amount of fine dust particles. I've peeped inside the unit and it looks reasonably clean and tidy, but this fine dust gets everywhere.

    Cheers and thanks again for your time
    Rob
      My Computer


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

    Since you mentioned it, give the inside of the computer a good cleaning with a can of compressed air; careful using a vacuum cleaner, as it can generate a static buildup and zap sensitive components.

    What kind of building work was done? Could they have added to or otherwise modified the electrical circuit the computer is on?
      My Computer


  10. Posts : 12
    Windows 7 64
    Thread Starter
       #10

    > What kind of building work was done? Could they have added to or otherwise modified the electrical circuit the computer is on?

    Yes, the building work has involved a complete rewiring - but I discount that as a cause for my current problems because we relocated to a rental house for a while, and the BSODs were occurring there also.

    The good news is it's been 24 hours now and the PC is still running - which is a significant milestone! I won't stick my neck out totally, but I'm hopeful that the good advice offered by you guys has significantly resolved my problems.

    I'm flabergasted that McAfee appears to be the root cause of so much grief over the past few months - but it's hard to draw any other conclusion.

    Many thanks for your advice.
    Rob

    Rob
      My Computer


 
Page 1 of 3 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 13:56.
Find Us