News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Jims BSOD problem

    Posted on WSjimboba Comment on the AskWoody Lounge

    Home Forums AskWoody support Windows Windows 7 Questions: Windows 7 Jims BSOD problem

    Viewing 26 reply threads
    • Author
      Posts
      • #495418 Reply
        WSjimboba
        AskWoody Plus

        Have been having a recent session of BSOD just after start up usually within 5 mins of settling down.
        This Win7 is 64bit.
        On the other Drive I have a 32bit version which runs fine.
        I have attached a minifile dump record for perusal and comment.
        All drivers are up to date including Video and also have changed the AV as well.
        Help and comment appreciated.
        Jim

        Attachments:
      • #1458382 Reply
        satrow
        AskWoody MVP

        Still the same BSOD triggers as last time around, Jim; to my amateur eye it looks like a Registry call that does it – I can’t see what’s making that call, or what Registry location it’s to.

        Carefully read and follow the instructions here then attach the required zipped folder back here, there’ll be a lot more background info that we can work on. Note that this will probably take 10 minutes or so to run – with your recent up times being sub 5 minutes, it might prove tricky.

      • #1458386 Reply
        WSjwitalka
        AskWoody Lounger

        Try a Clean boot and see if you still get the BSOD.
        http://support.microsoft.com/kb/929135

        Jerry

      • #1458397 Reply
        Berton
        AskWoody_MVP

        I just worked on a Win7 that was similarly shutting down and turned out his Power Profile was missing. Cleaned up the computer and replaced one file [rpcss.dll] in System32 that his antivirus couldn’t clean and got the Power Options working again.

        Before you wonder "Am I doing things right," ask "Am I doing the right things?"
      • #1458431 Reply
        WSjimboba
        AskWoody Plus

        Yes, will do…This was a new install which was ok for about 5 months on an SSD which is much better than my old Adaptec Raid config..will update you soonest…

      • #1458443 Reply
        WSjimboba
        AskWoody Plus

        Please find attached as requested. There was no BSOD this time round but the info may be useful.
        Also an updated mini dump file which shows another driver conflict?
        Thanks
        Jim

        Attachments:
      • #1458518 Reply
        satrow
        AskWoody MVP

        Hiya, Jim.

        I’m currently having some problems, I’ve asked for some help with your BSOD problem, hopefully you’ll get further instructions soon.

      • #1458532 Reply
        WSjcgriff2
        AskWoody Lounger

        Hi –

        Update your Asus ATK0110 driver. This 2005 version is known to cause BSODs in Windows 7, 8 & 8.1 systems –

        Code:
         ASACPI.sys   Sun Mar 27 22:30:36 [COLOR="#FF0000"]2005[/COLOR] (42476C4C)

        http://sysnative.com/drivers/driver.php?id=ASACPI.sys

        See if the system stabilizes after updating asacpi.sys.

        Regards. . .

        jcgriff2
        MS MVP

        EDIT: Be sure that your SSD firmware is up to date.

      • #1458549 Reply
        WSjimboba
        AskWoody Plus

        Updated the .sys file from Asus. BSOD happened again about 5 mins after switching on.
        SSD Firmware ok as well…
        Over too you…
        Thanks
        Jim

      • #1458578 Reply
        satrow
        AskWoody MVP

        Could you zip and attach the latest minidump please.

      • #1458583 Reply
        WSjimboba
        AskWoody Plus

        Yes of course.. crashed twice tonight..

        Attachments:
      • #1458613 Reply
        WSjcgriff2
        AskWoody Lounger

        This Win7 is 64bit.
        On the other Drive I have a 32bit version which runs fine.

        Are both versions of Windows 7 validated?

        http://www.microsoft.com/genuine/validate

        See if Driver Verifier flags any 3rd party drivers – http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-blue-screen-of-death-related-windows-8-1-8-7-and-windows-vista.html

        Regards. . .

        jcgriff2

        • #1458622 Reply
          WSjimboba
          AskWoody Plus

          Yes, both versions are genuine.
          Will run verifier a bit later..
          Regards
          Jim

      • #1458614 Reply
        Coochin
        AskWoody_MVP

        This Win7 is 64bit.
        On the other Drive I have a 32bit version which runs fine.

        Is the other Windows installation visible from whichever one is active?

        If it is there is a risk of “crosstalk” that can cause all manner of woe.

        • #1458623 Reply
          WSjimboba
          AskWoody Plus

          ..Only visible via Windows Explorer..which I wouldnt use.
          There are no links to the other win 7 from this os..
          Jim

          • #1458626 Reply
            Coochin
            AskWoody_MVP

            ..Only visible via Windows Explorer..which I wouldnt use.
            There are no links to the other win 7 from this os..
            Jim

            To clarify, when you boot into Win7 64bit is the HDD partition the 32bit partition hidden?

            If it is not hidden there is a certain risk that the active Windows will attempt to load files from the inactive Windows partition. This is a well-known problem among users experienced with dual-booting, and I personally have experienced this problem back when I first started dual-booting XP and Win98SE about 2002.

            Currently I have three desktop PCs and one laptop (which I use sometimes when I am attending on customers). My main PC has two installations of Win7, one of my workbench PCs has Vista and XP, the second workbench PC has Win7 and XP, the laptop has Win7, Vista, and XP. All these Windows installations are on their own separate partitions.

            I use “BootIt Bare Metal” from http://www.terabyteunlimited.com/ to boot between the various OSs. BootIt is configured to hide the inactive OS partitions to avoid the “crosstalk” problem.

            BootIt is also an excellent partition manager and imaging program.

            • #1458683 Reply
              WSjimboba
              AskWoody Plus

              Thanks for that info ..would you believe that having activated the verifier all has been ok now for 24 hours…grrr

      • #1458731 Reply
        WSjimboba
        AskWoody Plus

        Have now had several crashes with verifier enabled. Have attached the latest minidump file.

        Attachments:
      • #1458812 Reply
        satrow
        AskWoody MVP

        The latest dumps were verified, that’s a good thing 🙂

        Symantec/Norton drivers are flagged for the dumps, uninstall Norton 360, use the SymNRT tool after a reboot to ensure it’s fully removed, install MSE and enable the Windows firewall for further testing (they’re least likely to be involved in any BSOD): https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us
        http://windows.microsoft.com/en-us/windows/security-essentials-download

        BSOD BUGCHECK SUMMARY[/COLOR]

        Code:
        [font=lucida console]
        Debug session time: Mon Jul  7 18:30:29.285 2014 (UTC + 1:00)
        Loading Dump File [C:Users SysnativeBSODApps70714-46004-01.dmp]
        Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
        System Uptime: 0 days 0:02:17.267
        *** WARNING: Unable to verify timestamp for [B]EX64.SYS[/B]
        *** ERROR: Module load completed but symbols could not be loaded for [B]EX64.SYS[/B]
        Probably caused by : [B]EX64.SYS[/B] ( EX64+b648e )
        BugCheck 50, {fffff88069d86f5c, 0, fffff88004b8b48e, 5}
        BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
        Bugcheck code 00000050
        Arguments: 
        Arg1: fffff88069d86f5c, memory referenced.
        Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
        Arg3: fffff88004b8b48e, If non-zero, the instruction address which referenced the bad memory
        	address.
        Arg4: 0000000000000005, (reserved)
        BUGCHECK_STR:  0x50
        DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
        PROCESS_NAME:  itype.exe
        FAILURE_BUCKET_ID:  X64_0x50_VRF_[B]EX64[/B]+b648e
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
        Debug session time: Mon Jul  7 18:26:44.877 2014 (UTC + 1:00)
        Loading Dump File [C:UsersRoLYSysnativeBSODApps70714-46223-01.dmp]
        Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
        System Uptime: 0 days 0:01:16.469
        *** WARNING: Unable to verify timestamp for [B]SRTSP64.SYS[/B]
        *** ERROR: Module load completed but symbols could not be loaded for [B]SRTSP64.SYS[/B]
        Probably caused by : [B]SRTSP64.SYS[/B] ( SRTSP64+b5ad2 )
        BugCheck 50, {fffff6bc4000b928, 1, fffff80002c5e08e, 5}
        BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
        Bugcheck code 00000050
        Arguments: 
        Arg1: fffff6bc4000b928, memory referenced.
        Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
        Arg3: fffff80002c5e08e, If non-zero, the instruction address which referenced the bad memory
        	address.
        Arg4: 0000000000000005, (reserved)
        BUGCHECK_STR:  0x50
        DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
        PROCESS_NAME:  System
        FAILURE_BUCKET_ID:  X64_0x50_VRF_[B]SRTSP64[/B]+b5ad2
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
        [/font]

        I would leave Driver Verifier enabled for the next 24-48 hours to see whether it flags anything else.

        You can use Nirsoft’s DriverView to check the dates of your loaded 3rd party drivers, anything predating SP1 should be treated with suspicion, anything predating W7 Release should be eliminated wherever possible. While some of these drivers may work fine on a 32 bit system or Vista, W7 and x64 is a different story. http://www.nirsoft.net/utils/driverview.html x64 and other download links are near the bottom.

        To setup DrivervView for this task, go to View > Hide Microsoft drivers and View > Choose columns – Driver name, File type, Description, Product name, Modified date, File name, Service name, Service display name, Company and Digital signature are needed for best cross-reference. Click the Modified date header to sort by driver age, pre-2010 = suspect, look for updates, pre-2009 = remove or update (though like everything PC, there are a few exceptions, secdrv.SYS Macrovision Security driver being one of them).

        3rd party drivers loaded in the latest dumps below:

        *** 3rd PARTY DRIVER LIST ***

        Code:
        [font=lucida console]
        ASACPI.sys                  Thu May 14 02:25:17 2009 (4A0B72FD)
        AsIO.sys                    Mon Apr  6 08:21:08 2009 (49D9AD64)
        BHDrvx64.sys                Tue May  6 08:04:20 2014 (53688974)
        DUMETR64.SYS                Fri Mar  1 19:37:29 2013 (51310379)
        ENG64.SYS                   Thu Aug 22 21:38:20 2013 (521676BC)
        EX64.SYS                    Thu Aug 22 21:36:51 2013 (52167663)
        EraserUtilRebootDrv.sys     Thu Mar 20 16:30:59 2014 (532B17C3)
        IDSvia64.sys                Wed Mar  5 04:30:47 2014 (5316A877)
        Ironx64.SYS                 Tue Jul 30 01:59:35 2013 (51F70FF7)
        MBAMSwissArmy.sys           Thu Mar 20 22:12:35 2014 (532B67D3)
        NvStreamKms.sys             Wed Apr 30 01:59:44 2014 (53604B00)
        SRTSP64.SYS                 Mon Feb 10 23:04:55 2014 (52F95B17)
        SRTSPX64.SYS                Sat Jul 27 03:45:06 2013 (51F33432)
        SSPORT.sys                  Fri Aug 12 00:07:32 2005 (42FBDA34)
        SYMDS64.SYS                 Wed Jul 31 00:29:08 2013 (51F84C44)
        SYMEFA64.SYS                Thu Feb 27 23:32:07 2014 (530FCAF7)
        SYMEVENT64x86.SYS           Sat Jul 27 03:26:58 2013 (51F32FF2)
        SYMNETS.SYS                 Thu Feb 13 11:25:14 2014 (52FCAB9A)
        SbieDrv.sys                 Thu May 29 19:16:25 2014 (53877979)
        a320raid.sys                Wed Feb 10 19:12:38 2010 (4B730526)
        adpu320.sys                 Wed Feb 28 00:04:15 2007 (45E4C6FF)
        amdxata.sys                 Fri Mar 19 16:18:18 2010 (4BA3A3CA)
        asahci64.sys                Sun Jan 30 05:44:07 2011 (4D44FAA7)
        ccSetx64.sys                Tue Sep 24 04:58:04 2013 (52410DCC)
        eeCtrl64.sys                Thu Mar 20 16:30:59 2014 (532B17C3)
        lvrs64.sys                  Wed Jan 18 06:40:36 2012 (4F166964)
        lvuvc64.sys                 Wed Jan 18 06:41:08 2012 (4F166984)
        mbam.sys                    Wed Oct 30 16:11:45 2013 (52712FC1)
        mv614x.sys                  Mon Mar 26 06:53:22 2007 (46075FD2)
        mwac.sys                    Tue Mar  4 21:47:13 2014 (531649E1)
        nvlddmkm.sys                Tue May 20 00:08:44 2014 (537A8EFC)
        nvm62x64.sys                Fri Oct 17 22:01:06 2008 (48F8FD12)
        nvstor.sys                  Fri Mar 19 20:45:11 2010 (4BA3E257)
        nvvad64v.sys                Fri Mar 28 13:32:06 2014 (533579D6)
        point64.sys                 Fri Apr 12 13:15:29 2013 (5167FAE1)
        [/font]

        Useful links for the above drivers:
        http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
        http://www.carrona.org/drivers/driver.php?id=AsIO.sys
        http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
        http://www.carrona.org/drivers/driver.php?id=DUMETR64.SYS
        http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
        http://www.carrona.org/drivers/driver.php?id=EX64.SYS
        http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
        http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
        http://www.carrona.org/drivers/driver.php?id=Ironx64.SYS
        http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
        http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
        http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
        http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
        http://www.carrona.org/drivers/driver.php?id=SSPORT.sys
        http://www.carrona.org/drivers/driver.php?id=SYMDS64.SYS
        http://www.carrona.org/drivers/driver.php?id=SYMEFA64.SYS
        http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
        http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
        http://www.carrona.org/drivers/driver.php?id=SbieDrv.sys
        a320raid.sys – this driver hasn’t been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]
        http://www.carrona.org/drivers/driver.php?id=adpu320.sys
        http://www.carrona.org/drivers/driver.php?id=amdxata.sys
        http://www.carrona.org/drivers/driver.php?id=asahci64.sys
        http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
        http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
        http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
        http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
        http://www.carrona.org/drivers/driver.php?id=mbam.sys
        mv614x.sys – this driver hasn’t been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.[/color]
        http://www.carrona.org/drivers/driver.php?id=mwac.sys
        http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
        http://www.carrona.org/drivers/driver.php?id=nvm62x64.sys
        http://www.carrona.org/drivers/driver.php?id=nvstor.sys
        http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
        http://www.carrona.org/drivers/driver.php?id=point64.sys

        • #1459278 Reply
          WSjimboba
          AskWoody Plus

          Hi Satrow,
          Done as you have asked..wait and see. Thanks for bearing with me on this…I wonder if your original thought that there is a registry entry problem might be the answer.
          Thae a320 driver isnt used here as it is a ssd drive. The mv6 14x.sys is a Marvell Sata driver for the Data Drive so will update that one
          Will keep you posted.
          Thanks Jim

      • #1459288 Reply
        satrow
        AskWoody MVP

        Hi, Jim.

        Some loaded drivers from Marvell and Adaptec are of 2007 vintage, way too old to be considered safe on an SP1 x64 system, if you can, remove the a320 hardware and fully uninstall any software/drivers for it. I think the Marvell should update ok. Check dates with DriverView after each change and reboot.

        If there is/was a Registry issue, it may be related to one of the aging or removed drivers, I don’t have the skills (and I doubt if minidumps contain enough data to trace it anyway) to track it down to that level.

        Ensure that Driver Verifier has been turned off and just use the PC as normal, if it doesn’t BSOD again in 10 or so days, you probably have it fixed.

      • #1459327 Reply
        WSjimboba
        AskWoody Plus

        Hi Satrow
        Cant get an up to date sata driver mv614x.sys from Asus. They only support up to Vista 64 bit which is still 2007 vintage.
        Marvell web site seems next to useless as well..any ideas. Did try other versions of this driver with bad results??

      • #1459349 Reply
        satrow
        AskWoody MVP

        I’ve spent some time looking for an updated driver as well, no success. If it were mine, I’d create a Restore point, shut it down, switch the drive to a free onboard chipset SATA channel, disable the Marvell in the BIOS and test.

        If the Marvell drivers still load (check using DriverView), you should be able to remove them via Device Manager.

      • #1459636 Reply
        WSjimboba
        AskWoody Plus

        Hi Satrow
        Had several more BSODs the last one was before I could log into Windows!
        Driver verifier is in use of course. Havnt progressed your last thought yet about putting in a separate
        Sata card as yet. Does this Minidump show anything new as yet…? Thanks for all your time you are putting in..Jim

        Attachments:
      • #1459640 Reply
        satrow
        AskWoody MVP

        Hi again, Jim.

        I’ll analyse the latest dump soon, in the meantime: I asked in #21 to ensure that DV was disabled (leaving it on longer than 24-48 hours will lead to an increasing likelihood of it triggering ‘false’ BSODs, as it does add to the stress levels of Windows, by design), you have had it turned off in the interim, only re-enabling it after suffering another BSOD, yes?

      • #1459673 Reply
        WSjimboba
        AskWoody Plus

        Sorry Yes thats right..I will disable it again…

      • #1459920 Reply
        WSjimboba
        AskWoody Plus

        Hi Satrow
        Am now getting a lot of crashes..tried several times to send to you but crashed.
        Am sending this in safe mode. Driver verifier reset too. Will have to go back to 32bit until a reason can be found. It must be driver related as this safe mode is fine.
        Sorry to be a pain..regards Jim

        Attachments:
      • #1459927 Reply
        WSjwitalka
        AskWoody Lounger

        Have you verified that the PC is not overheating and have you run a memory check program?

        Jerry

        • #1459975 Reply
          WSjimboba
          AskWoody Plus

          Hi Jerry
          Have run 2 different Mem check progs and is fine and no overheating either..Jim

      • #1459949 Reply
        satrow
        AskWoody MVP

        Hi, Jim.

        Now we’re seeing some consistency, the most recent crashes are all 0x50’s with the same Stack Trace and effectively identical Windows up times:

        Code:
        [font=lucida console]
        BugCheck 50, {fffff0a00a0493a0, 1, fffff80002f55bba, 7}
        Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+7a )
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
        BugCheck 50, {fffff0a00123bc70, 1, fffff80002f95bba, 7}
        Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+7a )
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
        BugCheck 50, {fffff02001255478, 1, fffff80002f9bbba, 7}
        Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+7a )
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
        BugCheck 50, {fffff0a0012347f8, 1, fffff80002f9dbba, 7}
        Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+7a )
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
        BugCheck 50, {fffff0a0012acbf0, 1, fffff80002faabba, 7}
        Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+7a )
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
        BugCheck 50, {fffff0a00127b320, 1, fffff80002f45bba, 7}
        Probably caused by : ntkrnlmp.exe ( nt!CmpInsertKeyHash+7a )
        ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
        [/font]

        SYSTEM UP-TIME

        Code:
        [font=lucida console]
        System Uptime: 0 days 0:03:28.844
        System Uptime: 0 days 0:03:28.585
        System Uptime: 0 days 0:03:29.930
        System Uptime: 0 days 0:03:28.891
        System Uptime: 0 days 0:03:28.529
        System Uptime: 0 days 0:03:28.873
        [/font]

        STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
        Usual causes: Defective hardware (particularly memory – but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

        Cause:

        Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

        Another common cause is the installation of a faulty system service.

        Antivirus software can also trigger this error, as can a corrupted NTFS volume.

        Can you try to re-run the BSOD collection routine again from Safe Mode, the resulting logs should now contain some repetition that might help pinpoint the problem.

        • #1459976 Reply
          WSjimboba
          AskWoody Plus

          Hi Satrow,
          Antivirus was removed..mem checks done ok. Reckon a faulty system service seems a good bet..wonder which one though…?
          Had tried a different video card as well…
          Safe mode of course keeps running fine…

          • #1460511 Reply
            Coochin
            AskWoody_MVP

            Hi Satrow,
            Antivirus was removed..mem checks done ok. Reckon a faulty system service seems a good bet..wonder which one though…?

            If the BSOD flashes on your screen too fast for you to read it, go into Safe Mode, click Start then right-click Computer then left-click Properties. On the left side under “Control Panel Home” click “Advanced system settings”. Under the “Startup and Recovery” section in the lower part click “Settings”. In the “Startup and Recovery” settings dialog untick “Automatically restart”, then click “OK”. Close all windows back to your Desktop then restart into Normal Mode. The next time you see the BSOD it will stay on the screen so you can read what it says (probably PAGE_FAULT_IN_NONPAGED_AREA).

            In my experience with the kind of BSOD (GPF) errors you are getting the first thing to do is test the RAM for errors, which you seem to have done. The second thing is to run a repair scan on your Windows partition.

            Open an elevated Command Prompt window (Start/Search type “cmd” (no quotes), right-click “cmd” at the top of the list of results, left-click “Run as Administrator”. At the Command Prompt type:

            chkdsk c: /r

            then press Enter. A message should appear in the Command Prompt window asking you to restart your computer; go ahead and do so and the chkdsk scan should run as Windows begins to start back up. The scan will check for, and attempt to repair, any problems with the NTFS filesystem.

            You can troubleshoot services using msconfig (Start/Search type msconfig then right-click it in the results list, left-click “Run as Administrator”). Under the “Services” tab place a tick in the “Hide all Microsoft services” then untick any services you think could be causing the problem, then click “Apply”. After you click “OK” you will be prompted to restart the computer, go ahead and restart. You might have to repeat this msconfig method several times to identify which, if any, service is causing the BSOD.

      • #1459978 Reply
        satrow
        AskWoody MVP

        Can you try to re-run the BSOD collection routine again from Safe Mode, the resulting logs should now contain some repetition that might help pinpoint the problem. http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-death-bsod-posting-instructions-windows-8-7-vista.html

      • #1460060 Reply
        WSjimboba
        AskWoody Plus

        Hi Satrow
        Herewith..managed to do it in normal windows this time
        Jim

        Attachments:
      • #1460439 Reply
        WSjimboba
        AskWoody Plus

        Hi Satrow
        Have you had time to analyse these files?
        Regards
        Jim

    Viewing 26 reply threads

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Jims BSOD problem

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.