Random BSODs on new computer

Page 1 of 5 123 ... LastLast

  1. Posts : 47
    Windows 7 Ultimate x64
       #1

    Random BSODs on new computer


    Hi, I recently built a new computer, it's my first time and all seemed well, but I had some issues whilst installing Windows 7 onto it, there were some driver issues with sata raid controllers missing, this was fixed after I format my harddisk. The issue now is Windows constantly keeps bluescreening. It lasts maybe 10 minutes and or lasts 1 minute, it happens regardless of what I am doing, just randomly occurs. The pc specs are:

    Corsair Force GT 120GB SSD
    A western digital 2TB harddisk which I have currently disconnected as I thought maybe that was causing the problems but it seems its not the case.
    Motherboard is a Asus P8Z68 V Pro Gen3
    Processor is an i5 2500k at stock speeds.
    Power supply is an OCZ 750W ZT Series
    I don't have a graphics card, i'm using intels integrated graphics.

    I followed the guide to get my bsod dump information somewhere on the forums, and here it is.

    Code:
    Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.20642.amd64fre.win7_ldr.100211-1706
    Machine Name:
    Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e55e50
    Debug session time: Mon May 14 16:45:46.304 2012 (UTC + 1:00)
    System Uptime: 0 days 0:03:49.226
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffd5018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    .........
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\user.ini, error 2
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {5c, 2, 1, fffff80002c71bf0}
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    Probably caused by : memory_corruption ( nt!MiComputeFlushRange+39c )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000000000000005c, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002c71bf0, address which referenced memory
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    
    WRITE_ADDRESS:  000000000000005c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiComputeFlushRange+39c
    fffff800`02c71bf0 488908          mov     qword ptr [rax],rcx
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  VSSVC.exe
    
    TRAP_FRAME:  fffff88007559310 -- (.trap 0xfffff88007559310)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000005c rbx=0000000000000000 rcx=0000000000000075
    rdx=0000000000000040 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002c71bf0 rsp=fffff880075594a0 rbp=fffffa8006f71320
     r8=0000000000000000  r9=fffff88002f64180 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiComputeFlushRange+0x39c:
    fffff800`02c71bf0 488908          mov     qword ptr [rax],rcx ds:00000000`0000005c=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c84ee9 to fffff80002c85980
    
    STACK_TEXT:  
    fffff880`075591c8 fffff800`02c84ee9 : 00000000`0000000a 00000000`0000005c 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`075591d0 fffff800`02c83b60 : 00000000`00000001 00000000`0000005c fffffa80`06f2b900 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`07559310 fffff800`02c71bf0 : fffff8a0`068575b8 fffffa80`08062180 fffff980`08ecf9e8 fffffa80`06f288f0 : nt!KiPageFault+0x260
    fffff880`075594a0 fffff800`02c715e9 : fffff980`00000000 fffff880`07559728 00000000`00000000 fffff880`07559580 : nt!MiComputeFlushRange+0x39c
    fffff880`07559530 fffff800`02c7133a : 00000000`00000000 fffff980`08ecf9e8 00000000`00000000 fffff880`012e8961 : nt!MmFlushSection+0x49
    fffff880`075595f0 fffff880`012ff642 : fffffa80`06f7f568 00000000`00000000 fffff8a0`00000000 00000000`00000001 : nt!CcFlushCache+0x88a
    fffff880`075596f0 fffff880`012ae9e7 : 00000000`00000000 fffff8a0`06858140 00000000`00000000 00000000`00000001 : Ntfs!NtfsFlushUserStream+0x92
    fffff880`07559770 fffff880`012ffbbd : fffffa80`06f288f0 fffffa80`08062180 fffffa80`061c9f01 fffff8a0`00c85a00 : Ntfs!NtfsFlushVolume+0x2c7
    fffff880`075598a0 fffff880`013005f0 : fffffa80`06f288f0 fffffa80`06e8f770 fffffa80`06facc60 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
    fffff880`07559980 fffff880`0100323f : fffffa80`06e8fb10 fffffa80`06e8f770 fffffa80`06f288f0 fffff880`075599a8 : Ntfs!NtfsFsdFlushBuffers+0x104
    fffff880`075599f0 fffff880`010016df : fffffa80`07e488e0 00000000`00000000 fffffa80`07e48800 fffffa80`06e8f770 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`07559a80 fffff800`02f9daf9 : 00000000`00000002 fffffa80`06facc60 00000000`00000000 fffffa80`06e8f770 : fltmgr!FltpDispatch+0xcf
    fffff880`07559ae0 fffff800`02f2b691 : fffffa80`06e8f770 fffffa80`0702bb60 fffffa80`06facc60 00000000`000007ff : nt!IopSynchronousServiceTail+0xf9
    fffff880`07559b50 fffff800`02c84bd3 : fffffa80`0702bb60 00000000`ffec2270 fffffa80`07e488e0 fffffa80`06facc60 : nt!NtFlushBuffersFile+0x171
    fffff880`07559be0 00000000`776a036a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`031df688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776a036a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiComputeFlushRange+39c
    fffff800`02c71bf0 488908          mov     qword ptr [rax],rcx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiComputeFlushRange+39c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b74e94c
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiComputeFlushRange+39c
    
    BUCKET_ID:  X64_0xA_nt!MiComputeFlushRange+39c
    
    Followup: MachineOwner
    ---------
    I would greatly appreciate it if anyone could help me solve this issue.

    Thanks.
      My Computer


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

    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
    Please attach the DMP files to your next post not to post one.


    If you are overclocking STOP

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
      My Computer


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

    Thanks for your reply. Here are the files I think you requested.
      My Computer


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

    bump
      My Computer


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

    edmundkong36 said:
    Thanks for your reply. Here are the files I think you requested.


    These crashes were caused by memory corruption 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 a 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-7 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.

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

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    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 "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like.
    From my limited experimentation it makes the BSOD's come faster.
    - 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.

    If you are using win 8 add these

    - Concurrency Stress Test
    - DDI compliance checking

    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.

    Thanks to JCGriff2 & Usasma.

    Sysnative Forums

    Driver Reference Table (DRT)


    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Driver Verifier

    Using Driver Verifier (Windows Drivers)
      My Computer


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

    Hi there, I have ran Memtest on my two RAM sticks together in their original slots. The result was 5 passes and 0 errors. Do I have to run the test on each ram individually and in every slot?

    As for the driver verifier, I played a movie but the system seems to lag terribly and I cant move the mouse. However, it is unwilling to BSOD so I had to restart the system.
      My Computer


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

    edmundkong36 said:
    Hi there, I have ran Memtest on my two RAM sticks together in their original slots. The result was 5 passes and 0 errors. Do I have to run the test on each ram individually and in every slot?

    As for the driver verifier, I played a movie but the system seems to lag terribly and I cant move the mouse. However, it is unwilling to BSOD so I had to restart the system.
    Good news on memtest. Verifier is of course your call
      My Computer


  8. Posts : 47
    Windows 7 Ultimate x64
    Thread Starter
       #8

    My memory dump file zipped up is still too big, 75mb... have I done anything wrong?
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    It sounds like you are trying to zip up a copy of C:\Windows\MEMORY.DMP file instead of a copy of the C:\Windows\Minidump directory. Follow the https://www.sevenforums.com/crashes-d...tructions.html to provide the full crash reports and minidump files.
      My Computer


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

    Ah, I see... such a noob... here are the minidump files.

    Thanks
      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 05:56.
Find Us