Solved Blue screen error

[baratanich]

I have got a blue screen error twice or thrice running windows 7 x64 bit. I reinstalled the operating system, but am still getting this error message. I got it twice just after getting the computer back up and running.


How can i know what is causing this problem?

I have purchased a new 4GB Ram last week, I just removed it for safety !

Here are the dump and system info files!

https://skydrive.live.com/redir?resid=A25C62320A4D2FE7!2345

If the problem was the Ram as I suspected, how can I know which Ram is compatibale with my system!?

Thanks,
Bara Tanich

 

[baratanich]

Thanks, but what is this memory dump btw? and how do i fix this rather than just ignoring it? Will changing my RAM fix the problem?

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[baratanich]

Thanks a lot Arc

I have tried to use the tool you mentioned and did unblock and ran it as an administrator, it starts copying some files and then I get a message saying "acess is dinied"

I have uploaded the dumpfiles and the system info files and saved all the drivers info using driver view! (see the attachments)

here is all the info about the laptop and its specs from the hp site!
http://h10025.www1.hp.com/ewfrf/wc/...lc=en&jumpid=reg_r1002_uken_c-001_title_r0001

I have called HP and after having a very long conversation and sending them these files. They said your laptop is not compatible with windows 7. I have used windows 7 for more than 4 months now and I never had a single problem only after I got this new RAM!

let me know if you need any other info!

THank you once again

 

[Arc]

A HP Pavilion 15 series notebook is not compatible to Windows 7? I dont think so. But HP may know better about their machines.

As you are saying that you havent faced any issue till you introduced new RAM, and the crash dumps are also indicating to memory corruption, your first attempt should be testing the RAM.

First make it sure that the RAM is compatible with the PC. 4 GB 1600 MHz DDR3. If not, replace it.

If yes, 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 there is no 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 50, {fffffac00cfe1f88, 0, fffff80002aabc11, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiGetNextNode+25 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffac00cfe1f88, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002aabc11, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb3100
GetUlongFromAddress: unable to read from fffff80002cb31c0
 fffffac00cfe1f88 Nonpaged pool

FAULTING_IP: 
nt!MiGetNextNode+25
fffff800`02aabc11 488b4808        mov     rcx,qword ptr [rax+8]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

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

TRAP_FRAME:  fffff88007e8b3a0 -- (.trap 0xfffff88007e8b3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffac00cfe1f80 rbx=0000000000000000 rcx=fffffa800d009840
rdx=000000000000040e rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aabc11 rsp=fffff88007e8b538 rbp=0000000000000001
 r8=000000000000040e  r9=00000000000007ff r10=0000000000000801
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiGetNextNode+0x25:
fffff800`02aabc11 488b4808        mov     rcx,qword ptr [rax+8] ds:fffffac0`0cfe1f88=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002af60a2 to fffff80002a79540

STACK_TEXT:  
fffff880`07e8b238 fffff800`02af60a2 : 00000000`00000050 fffffac0`0cfe1f88 00000000`00000000 fffff880`07e8b3a0 : nt!KeBugCheckEx
fffff880`07e8b240 fffff800`02a7766e : 00000000`00000000 fffffac0`0cfe1f88 00000000`00000000 fffffa80`0d31bb50 : nt! ?? ::FNODOBFM::`string'+0x43311
fffff880`07e8b3a0 fffff800`02aabc11 : fffff800`02e16850 00000000`00000000 fffffa80`0d31bb50 00000000`00000080 : nt!KiPageFault+0x16e
fffff880`07e8b538 fffff800`02e16850 : 00000000`00000000 fffffa80`0d31bb50 00000000`00000080 00000000`00000001 : nt!MiGetNextNode+0x25
fffff880`07e8b540 fffff800`02cd6248 : fffffa80`0d000b30 fffff880`07e8b640 00000000`00000000 00000000`000000d0 : nt!MmEnumerateAndReferenceImages+0x160
fffff880`07e8b5c0 fffff800`02d33c2a : fffffa80`0d000b30 00000000`00000000 fffffa80`0d31bb50 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x1fc89
fffff880`07e8b760 fffff800`02d50c48 : 000007ff`fffa6000 fffff880`07e8bae0 00000000`00000000 fffffa80`0bd92090 : nt!PspExitProcess+0x52
fffff880`07e8b7c0 fffff800`02d3618d : 00000000`c000041d 00000000`00000001 000007ff`fffa6000 00000000`00000000 : nt!PspExitThread+0x848
fffff880`07e8b880 fffff800`02a6c07a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000b1c : nt!PsExitSpecialApc+0x1d
fffff880`07e8b8b0 fffff800`02a6c3c0 : 00000000`00000000 fffff880`07e8b930 fffff800`02d36100 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`07e8b930 fffff800`02a78877 : fffffa80`0d31bb50 00000000`040ee4f8 00000000`00000002 00000000`040ee570 : nt!KiInitiateUserApc+0x70
fffff880`07e8ba70 00000000`771a108a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`040ed938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771a108a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetNextNode+25
fffff800`02aabc11 488b4808        mov     rcx,qword ptr [rax+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiGetNextNode+25

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_0x50_nt!MiGetNextNode+25

BUCKET_ID:  X64_0x50_nt!MiGetNextNode+25

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_nt!migetnextnode+25

FAILURE_ID_HASH:  {1aa95eee-b9de-4282-d3e5-42458123670a}

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

 

[baratanich]

Thank you for the Awesome reply man!
I will follow what you said and keep you posted!

 

[baratanich]

Sounds like I had a bad stick of ram.I used memtest cd and that Ram gave me one pass and then I had to see few thousands of errors. I got two new 8Gb ram sticks and life back to normal.
Thanks you so much for your help.

 

[Arc]

Sounds like I had a bad stick of ram.I used memtest cd and that Ram gave me one pass and then I had to see few thousands of errors. I got two new 8Gb ram sticks and life back to normal.
Thanks you so much for your help.

Well done!