Win7 x64 Random BSOD's, different bugcheck codes

Page 1 of 5 123 ... LastLast

  1. Posts : 25
    Windows 7 x64
       #1

    Win7 x64 Random BSOD's, different bugcheck codes


    Hi, im having trouble finding out what's causing this PC to crash from time to time.
    The poblems started a few weeks ago when i upgraded the CPU and the GPU. The vendors of the components and the motherboard stayed the same.
    (E6550 --> E8500 and HD4850 --> HD6850)
    It had some crashes before but now it got realy bad so i reinstalled the system, updated MB bios, dowloaded drivers from vendor sites, updated everything and only installed basic 3rd party drivers and software.

    The crashes still remained...they happen more often when the computer is under heavy load (3D operations, games running), but they also occur if im playing a video or just use a web browser.
    I ran memtest, chkdisk but nothing, then furmark and intelliburn but no effect.
    The remaining drivers came up clean with verifier, and i looked after anything that came up from the crashdumps but my windbg knowledge is limited so im at the end of my rope here and open to any suggestions.
    Thanks in advance.


    • Windows 7 Enterprise 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
    • Gigabyte GA-P35-DS3 rev. 2.1 (bios version: F14)
    • Intel E8500 (E0)
    • ASUS Radeon HD6850
    • 4x1GB Geil RAM @(5-5-5-18) (2 different sets of 2x1gb same default timings 4-4-4-12)
    • Western Digital 2TB (WD20EARS) - 1 partition
    • Western Digital 640GB (WD6400AAKS) - 2 partition (100GB system partition)
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    These crashes were caused by memory corruption/exception (probably a driver).
    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *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.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - 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.

    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.
      My Computer


  3. Posts : 25
    Windows 7 x64
    Thread Starter
       #3

    As i wrote before: memtest gave me no errors (7 passes), and verifier didnt cause any crashes.
    Anyway if nothing else can be told from the dumps, ill keep running verifier on non MS drivers and report back if a new crashdump is made.

    update:
    attaching the new crashdump
    Last edited by aSmith; 09 Feb 2012 at 10:14.
      My Computer


  4. Posts : 25
    Windows 7 x64
    Thread Starter
       #4

    Another BSOD.
    After restarting, the system froze/became unresponsive on the loading screen (black background, windows logo) and i had to hit reset.
    When it loaded up, a system repair was attempted but it failed.

    dump from the bsod attached
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    aSmith said:
    Another BSOD.
    After restarting, the system froze/became unresponsive on the loading screen (black background, windows logo) and i had to hit reset.
    When it loaded up, a system repair was attempted but it failed.

    dump from the bsod attached

    Still related to memory_corruption and not driver verified. Are you sure verifier is running?

    type verifier /query and see what drivers are being verified.
      My Computer


  6. Posts : 25
    Windows 7 x64
    Thread Starter
       #6

    Update: new crashdump attached.

    here you go:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\SMITH>verifier /query
    2012.02.09., 19:31:12
    Level: 00000FBB
    RaiseIrqls: 0
    AcquireSpinLocks: 1448165
    SynchronizeExecutions: 217735
    AllocationsAttempted: 1166341
    AllocationsSucceeded: 1166341
    AllocationsSucceededSpecialPool: 1166341
    AllocationsWithNoTag: 49
    AllocationsFailed: 0
    AllocationsFailedDeliberately: 0
    Trims: 156718
    UnTrackedPool: 563395

    Verified drivers:

    Name: amdxata.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 0
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 0
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 0
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 0

    Name: serial.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 5
    CurrentNonPagedPoolAllocations: 1
    PeakPagedPoolAllocations: 7
    PeakNonPagedPoolAllocations: 2
    PagedPoolUsageInBytes: 256
    NonPagedPoolUsageInBytes: 32
    PeakPagedPoolUsageInBytes: 1088
    PeakNonPagedPoolUsageInBytes: 4144

    Name: atikmpag.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 8
    CurrentNonPagedPoolAllocations: 848
    PeakPagedPoolAllocations: 8
    PeakNonPagedPoolAllocations: 959
    PagedPoolUsageInBytes: 17248
    NonPagedPoolUsageInBytes: 56092
    PeakPagedPoolUsageInBytes: 17248
    PeakNonPagedPoolUsageInBytes: 62724

    Name: atikmdag.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 2031
    CurrentNonPagedPoolAllocations: 598
    PeakPagedPoolAllocations: 2137
    PeakNonPagedPoolAllocations: 673
    PagedPoolUsageInBytes: 8659356
    NonPagedPoolUsageInBytes: 1157456
    PeakPagedPoolUsageInBytes: 8743204
    PeakNonPagedPoolUsageInBytes: 1274060

    Name: rt64win7.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 1032
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 1032
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 170716
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 170716

    Name: ndis.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 6
    CurrentNonPagedPoolAllocations: 2592
    PeakPagedPoolAllocations: 8
    PeakNonPagedPoolAllocations: 2624
    PagedPoolUsageInBytes: 984
    NonPagedPoolUsageInBytes: 838768
    PeakPagedPoolUsageInBytes: 1296
    PeakNonPagedPoolUsageInBytes: 859968

    Name: wmbenum.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 0
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 1
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 0
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 16

    Name: wmxlcore.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 62
    PeakPagedPoolAllocations: 1
    PeakNonPagedPoolAllocations: 62
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 116892
    PeakPagedPoolUsageInBytes: 60
    PeakNonPagedPoolUsageInBytes: 116892

    Name: rthdmivx.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 87
    PeakPagedPoolAllocations: 1
    PeakNonPagedPoolAllocations: 89
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 44280
    PeakPagedPoolUsageInBytes: 84
    PeakNonPagedPoolUsageInBytes: 44400

    Name: rtkvhd64.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 1154
    PeakPagedPoolAllocations: 1
    PeakNonPagedPoolAllocations: 1155
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 849140
    PeakPagedPoolUsageInBytes: 92
    PeakNonPagedPoolUsageInBytes: 850036

    Name: dump_dumpata.sys, loads: 0, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 0
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 0
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 0
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 0

    Name: dump_atapi.sys, loads: 2, unloads: 1
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 0
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 0
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 0
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 0

    Name: dump_dumpfve.sys, loads: 2, unloads: 1
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 1
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 1
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 16400
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 16400

    Name: wmfilter.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 4
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 6
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 1020
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 1932

    Name: lhidfilt.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 0
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 0
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 0
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 0

    Name: lmoufilt.sys, loads: 1, unloads: 0
    CurrentPagedPoolAllocations: 0
    CurrentNonPagedPoolAllocations: 0
    PeakPagedPoolAllocations: 0
    PeakNonPagedPoolAllocations: 0
    PagedPoolUsageInBytes: 0
    NonPagedPoolUsageInBytes: 0
    PeakPagedPoolUsageInBytes: 0
    PeakNonPagedPoolUsageInBytes: 0

    C:\Users\SMITH>
    Update: new crashdump attached.
    Last edited by aSmith; 09 Feb 2012 at 14:18.
      My Computer


  7. Posts : 25
    Windows 7 x64
    Thread Starter
       #7

    new crashdump
      My Computer


  8. Posts : 40
    Windows 7 Ultimate x86
       #8

    I think the psu might be the problem, what psu do you have ?
      My Computer


  9. Posts : 25
    Windows 7 x64
    Thread Starter
       #9

    i'ts a HKC USP-5580 (580W)
    it shuld be more then enugh...
    HKC Europe B.V.
      My Computer


  10. Posts : 40
    Windows 7 Ultimate x86
       #10

    Try removing the graphics card and then check if that solved your problem, if it did then your psu is the problem.
    Did you try reinstalling Windows ?
      My Computer


 
Page 1 of 5 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 06:45.
Find Us