PC freezing and random BSODs

Page 2 of 2 FirstFirst 12

  1. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #11

    Ok, here it is.. this time got these two:
    CLOCK_WATCHDOG_TIMEOUT
    PAGE_FAULT_IN_NONPAGED_AREA

    I tested the RAM yesterday, each stick separately for 4 passes, but I will do it again and let the test run for 8 passes.
    Last edited by thafuchs; 15 Feb 2013 at 18:19. Reason: changed the zip
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #12

    So you haven't enabled driver verifier yet.

    I guess you haven't taken the memtest too?

    And have you followed the other links suggested?


    For any further proceeding, let us know the results of the suggested steps accordingly.
      My Computer


  3. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #13

    Yes, I enabled it and let it run until I got these BSOD... I'll try these other steps you suggested
      My Computer


  4. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #14

    I did the memtest for 11 passes, but it found no errors. Also run the stress test (Prime95 - recommended in the stop 0x101 thread) for about 9 hours until my pc froze, but until then it hadn't found any errors either, the results are in the zip.
    I enabled drive verifier and got one more BSOD. These last BSOD I got seemed to freeze while "Initializing disk for crash dump..." and it just stops responding. Maybe that's the reason there's no dump?
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #15

    The latest crash is a special pool detected memory corruption.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98034c3eee0, address trying to free
    Arg2: fffff98034c3e755, address where bits are corrupted
    Arg3: 0000000000530118, (reserved)
    Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted
    But current threads stack is not showing anything.

    As the memtest came clear, we can say that it is a problem caused by a device driver. It is the situation that the dumps are coming silent about it. Here, as I can say, the best feasible solution will be a Clean Reinstall - Factory OEM Windows 7. Have a look here: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
    Recently it was found (here: https://www.sevenforums.com/crashes-d...ml#post1869800 ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem.
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 17:40.
Find Us