bluescreen after fresh install

[merkelbeek]

Hello,


I have installed my pc new and i get random bluescreen crashes, one day i get 4 crashes and another non
i have made a dump with bluescreen view you can find it here:
https://www.dropbox.com/s/i3xku7jc5zzlkzy/Crash List.htm

can someone help me with this?

thanks

 

[kituhi1234]

Hey

There is nothing in the dump you have sent other than "<" symbol. Could you send them agian as a zip or jpeg something?

 

[merkelbeek]

sorry these are the good dumps

==================================================
Dump File : 012114-15865-01.dmp
Crash Time : 21-1-2014 22:29:45
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`68e1b748
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02ce2cd1
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74540
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.22436 (win7sp1_ldr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+74540
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012114-15865-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292.920
Dump File Time : 21-1-2014 22:30:21
==================================================

==================================================
Dump File : 012114-15475-01.dmp
Crash Time : 21-1-2014 21:36:55
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`659b3750
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02cfada0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74540
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.22436 (win7sp1_ldr.130828-1532)
Processor : x64
Crash Address : ntoskrnl.exe+74540
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012114-15475-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292.904
Dump File Time : 21-1-2014 21:37:38
==================================================

 

[gregrocker]

Follow the Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Forums.

While you wait for analysis, check that your drivers are up to date. Win7 drivers are provided in the installer and via Important and Optional Windows Updates after enabling Automatically deliver drivers via Windows Update (Step 3).

Check for Updates now. THen check Device Manager if any are missing or in error state.

Other Troubleshooting Steps for Windows 7

Other steps for getting and keeping a perfect Clean Reinstall - Factory OEM Windows 7
are the same for retail. Compare this to the install you did.

 

[merkelbeek]

This are my dumps from above guide

 

[merkelbeek]

someone pls help me with those dumps

 

[gregrocker]

What were the results of the other specific troubleshooting steps I gave you?

 

[Arc]

Hi merkelbeek.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   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

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8068e1b748, 2, 1, fffff80002ce2cd1}
[COLOR=Red]
Probably caused by : memory_corruption [/COLOR]( nt!MiUnlinkFreeOrZeroedPage+181 )

Followup: MachineOwner
---------

3: 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: fffffa8068e1b748, 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: fffff80002ce2cd1, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efd100
GetUlongFromAddress: unable to read from fffff80002efd1c0
 fffffa8068e1b748 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`02ce2cd1 48893cc2        mov     qword ptr [rdx+rax*8],rdi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88009ed03d0 -- (.trap 0xfffff88009ed03d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000d1c36e8 rbx=0000000000000000 rcx=0000000000000007
rdx=fffffa8000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ce2cd1 rsp=fffff88009ed0560 rbp=000000000000007c
 r8=0000000000000000  r9=0000000000000000 r10=fffffa800c5d1380
r11=fffff88002fd7180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiUnlinkFreeOrZeroedPage+0x181:
fffff800`02ce2cd1 48893cc2        mov     qword ptr [rdx+rax*8],rdi ds:fffffa80`68e1b748=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc2ae9 to fffff80002cc3540

STACK_TEXT:  
fffff880`09ed0288 fffff800`02cc2ae9 : 00000000`0000000a fffffa80`68e1b748 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09ed0290 fffff800`02cc1760 : ffffffff`fffffb80 fffff680`00035988 fffffa80`0f207ec0 fffffa80`08e18740 : nt!KiBugCheckDispatch+0x69
fffff880`09ed03d0 fffff800`02ce2cd1 : 00000000`00000000 fffffa80`0c5d2190 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`09ed0560 fffff800`02ce74e8 : fffff880`09ed0640 00000000`002f5d7c fffffa80`08e18740 00000000`0000007b : nt!MiUnlinkFreeOrZeroedPage+0x181
fffff880`09ed05d0 fffff800`02cd3982 : 00000000`00000080 80000002`00000002 fffffa80`0f2247d8 00000000`00000003 : nt!MiRemoveAnyPage+0x1d8
fffff880`09ed06f0 fffff800`02ce1975 : 00000000`00000001 00000000`06c1f000 fffff880`09ed0ae0 fffff8a0`03b04e70 : nt!MiResolveDemandZeroFault+0x9f2
fffff880`09ed07e0 fffff800`02ce0163 : 00000000`00000080 00000000`06c1f000 fffff680`000360f8 fffffa80`0f2247d8 : nt!MiResolveProtoPteFault+0x4f5
fffff880`09ed0870 fffff800`02ccfb79 : 00000000`00000000 00000000`06c1f000 fffffa80`0db88b50 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`09ed0980 fffff800`02cc166e : 00000000`00000001 00000000`06c1f000 00000000`fffdb001 00000000`05b4a000 : nt!MmAccessFault+0x359
fffff880`09ed0ae0 00000000`61f48580 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0015f1e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x61f48580


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`02ce2cd1 48893cc2        mov     qword ptr [rdx+rax*8],rdi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+181

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea08b

IMAGE_VERSION:  6.1.7601.22436

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181

BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!miunlinkfreeorzeroedpage+181

FAILURE_ID_HASH:  {a52f858c-ea5f-1c83-8d70-b206bb4818e0}

Followup: MachineOwner
---------

 

[merkelbeek]

previously i tried memtest already and the outcome was possitive not faults in there so