BSOD Occurs Randomly - hwpolicy.sys


  1. Posts : 260
    Windows 7 Ultimate x64
       #1

    BSOD Occurs Randomly - hwpolicy.sys


    Hi Guys,

    I have a custom built pc with the spec listed below:

    --------------------------------------------
    AMD Athlon 64 X2 5200+ (Socket AM2)
    Asus M2A-VM HDMI
    ATI Radeon X1250 (Built in)
    Realtek Sound Card (Built in)
    6GB RAM (2x 2GB & 2x 1GB) - DDR2
    Windows 7 Professional x86 - SP1
    --------------------------------------------

    FILES:
    Attachment 330561
    Attachment 330562
    Attachment 330563

    MINIDUMP:
    Attachment 330564

    **EDIT**

    Here is the link for all the BSOD Data from the SF Diagnostic Tool: Attachment 330599

    The computer keeps BSODing whenever i open the browser or install something, i have attached the latest minidump file along with screenshots of the system spec. I recently did a clean install of windows on the pc and that fixed a few of the other BSODs i was having. I have used Bluescreenviewer to read the minidump file and it has told me that hwpolicy.sys and ntkrnlpa.exe was causing the BSOD.

    I have gone through many articles on Google but cannot fix the problem.

    Anyone have any idea on what it could be? I'm not great at analysing minidumps so i have attached it for your information.

    Thanks

    MistUnleashed
    Last edited by MistUnleashed; 25 Aug 2014 at 17:10. Reason: SF Diagnostic Link Added
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Welcome MistUnleashed :) .

    Welcome, please follow the Blue Screen of Death (BSOD) Posting Instructions .

    Although I don't have much information I have a feeling we are dealing with an infection,
    do you believe that kind of scenario is possible?
      My Computer


  3. Posts : 260
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Hi YoYo!

    I'm just about to run the SF Diagnostic Tool!

    I will post the file up when I have done it!

    Infection wise I think its highly unlikely as I have run numerous virus scans and boot-time scans using Avast! and they have come up clear.

    I think its a corrupted driver problem, but i may be wrong!

    Thanks
      My Computer


  4. Posts : 260
    Windows 7 Ultimate x64
    Thread Starter
       #4

    Hi Yoyo155

    BSOD Diagnostic Files: Attachment 330598

    Files are attached and I have updated my original post with them.

    Please let me know what the problems are and advise on how to fix them!

    Thanks!
      My Computer


  5. Posts : 3,056
    Windows 10
       #5

    Hi thanks for the files, although many of the files are missing I can see you have a pretty
    old machine with a BIOS dating way back in 2007, two years before Windows 7 went RTM.
    I can also see you have an assortment of memory modules.

    Code:
    !sysinfo smbios
    [SMBIOS Data Tables v2.4]
    [DMI Version - 36]
    [2.0 Calling Convention - No]
    [Table Size - 1783 bytes]
    
    [BIOS Information (Type 0) - Length 24 - Handle 0000h]
      Vendor                        Phoenix Technologies, LTD
      BIOS Version                  ASUS M2A-VM HDMI ACPI BIOS Revision 1301
      BIOS Starting Address Segment e000
      BIOS Release Date             09/11/2007
      BIOS ROM Size                 100000
      
      BIOS Major Revision           255
      BIOS Minor Revision           255
      EC Firmware Major Revision    255
      EC Firmware Minor Revision    255
    [System Information (Type 1) - Length 27 - Handle 0001h]
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
      Version                       System Version
      Serial Number                                     
      UUID                          00000000-0000-0000-0000-000000000000
      Wakeup Type                   Power Switch
      SKUNumber                      
      Family                         
    [BaseBoard Information (Type 2) - Length 8 - Handle 0003h]
      Manufacturer                  ASUSTeK Computer INC.
      Product                       M2A-VM HDMI
      Version                       1.XX    
      Chassis Type                  Desktop
    [Processor Information (Type 4) - Length 35 - Handle 0005h]
      Socket Designation            Socket AM2 
      Processor Type                Central Processor
      Processor Family              83h - AMD Athlon 64 Processor Family
      Processor Manufacturer        AMD
      Processor ID                  320f0400fffb8b17
      Processor Version             AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
      Processor Voltage             8dh - 1.3V
      External Clock                200MHz
      Max Speed                     3800MHz
      Current Speed                 2600MHz
      Status                        Enabled Populated
      Processor Upgrade             Socket 940
      L1 Cache Handle               000bh
      L2 Cache Handle               000ch
                  
    [Memory Controller Information (Type 5) - Length 24 - Handle 0006h]
      Error Detecting Method        06h - 64-bit ECC
      Error Correcting Capability   04h - None 
      Supported Interleave          03h - One Way Interleave
      Current Interleave            03h - One Way Interleave
      Maximum Memory Module Size    0bh - 2048MB
      Supported Speeds              000ch - 70ns 60ns 
      Supported Memory Types        0014h - Standard EDO 
      Memory Module Voltage         5V 
      Number of Memory Slots        4
      Memory Slot Handle            0007h
      Memory Slot Handle            0008h
      Memory Slot Handle            0009h
      Memory Slot Handle            000ah
      Enabled Err Correcting Caps   00h - 
    [Memory Module Information (Type 6) - Length 12 - Handle 0007h]
      Socket Designation            A0
      Bank Connections              01h - 1 0
      Current Speed                 1ns
      Current Memory Type           0100h - DIMM 
      Installed Size                8ah - 1024 [double bank]
      Enabled Size                  8ah - 1024 [double bank]
      Error Status                  00h - [No Errors] 
    [Memory Module Information (Type 6) - Length 12 - Handle 0008h]
      Socket Designation            A1
      Bank Connections              23h - 3 2
      Current Speed                 35ns
      Current Memory Type           0100h - DIMM 
      Installed Size                8ah - 1024 [double bank]
      Enabled Size                  8ah - 1024 [double bank]
      Error Status                  00h - [No Errors] 
    [Memory Module Information (Type 6) - Length 12 - Handle 0009h]
      Socket Designation            A2
      Bank Connections              45h - 5 4
      Current Speed                 69ns
      Current Memory Type           0100h - DIMM 
      Installed Size                8bh - 2048 [double bank]
      Enabled Size                  8bh - 2048 [double bank]
      Error Status                  00h - [No Errors] 
    [Memory Module Information (Type 6) - Length 12 - Handle 000ah]
      Socket Designation            A3
      Bank Connections              67h - 7 6
      Current Speed                 103ns
      Current Memory Type           0100h - DIMM 
      Installed Size                8bh - 2048 [double bank]
      Enabled Size                  8bh - 2048 [double bank]
      Error Status                  00h - [No Errors]
    The BCC (bugcheck codes) vary greatly, so the best place to start would be testing the RAM.

    Testing the RAM:

    koolkat77 said:
    Test and Diagnose RAM Issues with Memtest86+:


       Tip

    • Pay close attention to part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    When done with the testing procedure take a picture and upload it here.

    This will help you to determine where the issue is origination from (if any):
    Arc said:
    First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

    But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

    How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
    How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
    No code has to be inserted here. It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here. It is a motherboard issue. The particular slot is bad.
    Let us know the results.
      My Computer


  6. Posts : 260
    Windows 7 Ultimate x64
    Thread Starter
       #6

    Memtest Results


    Hi Yoyo,

    Find below the results of the test, i was able to do a full 7 passes but unfortunately on the first attempt, i forgot to take a picture so I re-ran the test up to 5 passes and all was fine. Also, please ignore the reflection of my table-lamp in the picture.

    Attachment 330974

    Yes, when i ran the SF diagnostic tool, it bluescreened a few times so i just uploaded what i could get hold of.

    If you need any more information, please ask.

    Thanks
      My Computer


  7. Posts : 260
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Any Ideas @Yoyo?
      My Computer


  8. Posts : 3,056
    Windows 10
       #8

    Hi sorry for the late reply!

    My gut tells me flaky hardware, but we can explore buggy drivers as well.
    Let's start with Enabling Driver Verifier.

    Arc said:
       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Please enable driver verifier following this TUTORIAL | But using the settings listed below:


    1. Go to Start and type in "verifier" (without the quotes) and press Enter
    2. Select "Create custom settings (for code developers)" and click "Next"
    3. Select "Select individual settings from a full list" and click "Next"
    4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
    5. Select "Select driver names from a list" and click "Next"
    6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
    7. Select "Finish" on the next page.
    Let us know.
      My Computer


  9. Posts : 260
    Windows 7 Ultimate x64
    Thread Starter
       #9

    YoYo155 said:
    Hi sorry for the late reply!

    My gut tells me flaky hardware, but we can explore buggy drivers as well.
    Let's start with Enabling Driver Verifier.

    Arc said:
       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Please enable driver verifier following this TUTORIAL | But using the settings listed below:


    1. Go to Start and type in "verifier" (without the quotes) and press Enter
    2. Select "Create custom settings (for code developers)" and click "Next"
    3. Select "Select individual settings from a full list" and click "Next"
    4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
    5. Select "Select driver names from a list" and click "Next"
    6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
    7. Select "Finish" on the next page.
    Let us know.
    Hi Yoyo,

    Very sorry I haven't checked this account in many months so I never got a chance to reply!

    Unfortunately i'm still facing the problem so i will get onto enabling Driver Verifier and we'll see were it takes us!

    Would it be a good idea to run a SFC /SCANNOW?

    Would this sort out a buggy driver?

    Thanks

    MistUnleashed
      My Computer


  10. Posts : 260
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Unfortunately I just ended up reinstalling Windows 7 onto the PC, must've been a few corrupt drivers in the old installation causing all the trouble!

    Thanks for your help!
      My Computer


 

  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 10:43.
Find Us