Tech Support Forum banner
Status
Not open for further replies.

[SOLVED] Random BSOD errors

2K views 9 replies 2 participants last post by  Patrick 
#1 ·
Ok so my laptop is 1 year old and I never had any BSODs till a month back.
The model is Lenovo Y500

First I installed HDD sentinel to check for bad sectors. The Health was 97% just before the last incident occured. Then after a BSOD with error :
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe+5a540
the health dropped to 93%.


RAM test was good and Chkdsk also came clean with some errors which it repaired before this last BSOD. I had KIS 2013 installed previously.

I am confused as to how to proceed now. Any help is appreciated!!

So I am attaching my dumps and a screenshot of BlueScreenView as all BSOD's were not same. Thank you!
 

Attachments

See less See more
4
#2 · (Edited)
Re: Random BSOD errors

Hi,

IRQL_NOT_LESS_OR_EQUAL (a)

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

Code:
5: kd> .trap 0xfffff8800b9584f0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffca83d9458b49 rbx=0000000000000000 rcx=0000000080000000
rdx=0000098000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80306af1df4 rsp=fffff8800b958680 rbp=fffff8800b958749
 r8=00000000ffffffff  r9=fffffa8013531968 r10=0000000000000000
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiPfPutPagesInTransition+0x46b:
fffff803`06af1df4 48ff4068        [COLOR=Blue]inc     [/COLOR]qword ptr [[COLOR=Purple]rax+68h[/COLOR]] ds:ffffca83`d9458bb1=????????????????
On the faulting instruction, we were incrementing the contents of rax+68 by one.

KERNEL_DATA_INPAGE_ERROR (7a)

This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

BugCheck 7A, {4, 0, fffffa80100da4a0, fffff8a00d7dcb32}

The 1st argument (4) indicates the lock type is a PTE address.

The 2nd argument (0) indicates our NTSTATUS code is STATUS_SUCCESS.

We can check our 1st argument address per the 4th argument:

Code:
5: kd> !pte fffff8a00d7dcb32
                                           VA fffff8a00d7dcb32
PXE at FFFFF6FB7DBEDF88    PPE at FFFFF6FB7DBF1400    PDE at FFFFF6FB7E280358    PTE at FFFFF6FC5006BEE0
contains 0000000001053863  contains 0000000000310863  contains 000000017457B863  contains 000000019C670880
GetUlongFromAddress: unable to read from fffff803155da0e4
pfn 1053      ---DA--KWEV  pfn 310       ---DA--KWEV  pfn 17457b    ---DA--KWEV  [COLOR=Red]not valid[/COLOR]
                                                                                  Transition: 19c670
                                                                                  Protect: 4 - ReadWrite
It's invalid.

----------------------------

I don't really suspect a software corruption/conflict causing this at all unless I start seeing different bug checks and symptoms, but if it comes down to it, we'll work with Driver Verifier.

Edit -- Your laptop has an SSD, so chkdsk isn't giving you actual results. Ensure the firmware is 100% up to date, and if it is, your SSD is dying IMO.

Regards,

Patrick
 
#5 ·
Re: Random BSOD errors

Ok, I haven't had the time yet to run SeaTools in DOS but two new BSODs came up while I was downloading stuff with help from Internet Download Manager. I happened when when it was joining all the threads




Can you pinpoint if its the RAM or the HDD? Thanks!
 

Attachments

Status
Not open for further replies.
You have insufficient privileges to reply here.
Top