Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD randomly on new computer

  • Please log in to reply
No replies to this topic

#1 EdmundK


  • Members
  • 1 posts
  • Local time:08:36 PM

Posted 14 May 2012 - 11:09 AM

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.

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

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


fffff800`02c71bf0 488908          mov     qword ptr [rax],rcx




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
fffff800`02c71bf0 488908          mov     qword ptr [rax],rcx ds:00000000`0000005c=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c84ee9 to fffff80002c85980

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


fffff800`02c71bf0 488908          mov     qword ptr [rax],rcx


SYMBOL_NAME:  nt!MiComputeFlushRange+39c

FOLLOWUP_NAME:  MachineOwner



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.


Edited by EdmundK, 14 May 2012 - 11:10 AM.

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users