What's new

Solved BSOD from time to time

KimK

New Member
Hi, I had have this problem for a while now but haven't decided to do something until now. I tried to get help from Microsoft, but it really take time to get a response from there so I will try my luck here instead.


I attached the necessary files. Here is also an old crash dump that I took a few days ago after instructions to run verifier. View attachment 52953

Code:
Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffe0002bb4cea0, 2, 0, fffff801bf11e227}


Probably caused by : memory_corruption ( nt!MiIdentifyPfn+157 )


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


0: 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: ffffe0002bb4cea0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff801bf11e227, address which referenced memory


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




READ_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffe0002bb4cea0 


CURRENT_IRQL:  2


FAULTING_IP: 
nt!MiIdentifyPfn+157
fffff801`bf11e227 4d8b3e          mov     r15,qword ptr [r14]


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


BUGCHECK_STR:  AV


PROCESS_NAME:  svchost.exe


ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre


TRAP_FRAME:  ffffd00024113fe0 -- (.trap 0xffffd00024113fe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0e00000000000060 rbx=0000000000000000 rcx=0200000000000000
rdx=fffff801bf11e318 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801bf11e227 rsp=ffffd00024114170 rbp=0000000000000000
 r8=000000000014ed2b  r9=0220000000155abd r10=2c0059b407460001
r11=0000000000000046 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiIdentifyPfn+0x157:
fffff801`bf11e227 4d8b3e          mov     r15,qword ptr [r14] ds:00000000`00000000=????????????????
Resetting default scope


LAST_CONTROL_TRANSFER:  from fffff801bf1d1ae9 to fffff801bf1c5fa0


STACK_TEXT:  
ffffd000`24113e98 fffff801`bf1d1ae9 : 00000000`0000000a ffffe000`2bb4cea0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`24113ea0 fffff801`bf1d033a : 00000000`00000000 ffffe000`2b8d96d8 00000000`00000000 ffffd000`24113fe0 : nt!KiBugCheckDispatch+0x69
ffffd000`24113fe0 fffff801`bf11e227 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`bf3beec0 : nt!KiPageFault+0x23a
ffffd000`24114170 fffff801`bf11e03c : 00000000`00000004 ffffe000`2b8d96d8 00000000`00000001 ffffd000`24114320 : nt!MiIdentifyPfn+0x157
ffffd000`24114220 fffff801`bf48d6db : ffffe000`2b8d96d8 ffffd000`24114b80 ffffe000`2b8d9000 00000091`9d1fb180 : nt!MiIdentifyPfnWrapper+0x3c
ffffd000`24114250 fffff801`bf463093 : ffffc001`96380060 00000000`00000001 ffffd000`24114434 ffffe000`2b8d9000 : nt!PfpPfnPrioRequest+0xbb
ffffd000`241142d0 fffff801`bf4611c3 : 00000091`9d1fb180 fffff801`00000000 00000000`0000004f ffffffff`ffffffff : nt!PfQuerySuperfetchInformation+0x313
ffffd000`24114400 fffff801`bf460f71 : 00000091`9d1fb180 00000091`a03f9000 00000000`00000000 00000091`9d845ed0 : nt!ExpQuerySystemInformation+0x1ff
ffffd000`24114ac0 fffff801`bf1d17b3 : ffffe000`2a9b22c0 00000091`9d842530 00000000`00000401 ffffd000`24114b00 : nt!NtQuerySystemInformation+0x49
ffffd000`24114b00 00007fff`400119da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000091`9d1fb048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`400119da




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nt!MiIdentifyPfn+157
fffff801`bf11e227 4d8b3e          mov     r15,qword ptr [r14]


SYMBOL_STACK_INDEX:  3


SYMBOL_NAME:  nt!MiIdentifyPfn+157


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


DEBUG_FLR_IMAGE_TIMESTAMP:  53388e13


IMAGE_NAME:  memory_corruption


BUCKET_ID_FUNC_OFFSET:  157


FAILURE_BUCKET_ID:  AV_VRF_nt!MiIdentifyPfn


BUCKET_ID:  AV_VRF_nt!MiIdentifyPfn


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:av_vrf_nt!miidentifypfn


FAILURE_ID_HASH:  {62d58b80-4f44-06c4-2065-1bdf1664d4fb}


Followup: MachineOwner
 

My Computer

System One

  • OS
    Windows 8.1

blueelvis

OMG Debugger!
VIP Member
Pro User
Hi KimK & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
Code:
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: 0000000000000049, 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: fffff802f1337230, address which referenced memory
So an attempt was made to access an address which is invalid or out of reach.
Code:
1: kd> .trap 0xffffd00023aaafe0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0a00000000000020 rbx=0000000000000000 rcx=0200000000000000
rdx=fffff802f13371e2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802f1337230 rsp=ffffd00023aab170 rbp=0000000000000000
 r8=00000000000d8e83  r9=0220000000136eee r10=8400ca0205420000
r11=0000000000000042 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=000[COLOR=#0000FF]0000000000000[/COLOR]
iopl=0         nv up ei pl zr na po nc
nt!MiIdentifyPfn+0x160:
fffff802`f1337230 f0410fba6f481f  lock bts dword ptr [r15+48h],1Fh ds:[COLOR=#FF0000]00000000`00000048[/COLOR]=????????
So, according to this, the MiIdentifyPfn tried to lock the address in RED. Let's check the address for it's validity -
Code:
1: kd> !pte [COLOR=#FF0000]00000000`00000048
[/COLOR]                                           VA 0000000000000048
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000000    PTE at FFFFF68000000000
contains 034000011A418867  contains 0000000000000000
GetUlongFromAddress: unable to read from fffff802f15df104
pfn 11a418    ---DA--UWEV  [COLOR=#FF0000]not valid[/COLOR]
So, as we can see that the address is not valid at all.

I would suggest you to run Memtest using this **GUIDE** for no less than 8 passes and report back the result of it. Furthermore, till the time we are troubleshooting, kindly remove the Daemon Tools. Also disconnect any Razer Devices till the time we are troubleshooting.

Also, remove your Avast and replace it with MSE till the time we are troubleshooting. Use this **TOOL** to remove Avast completely.

Let me know how it goes ^_^
 

My Computer

System One

  • OS
    Windows 8.1 Industry Pro B-)
    Computer type
    Laptop
    System Manufacturer/Model
    Toshiba
    CPU
    Core I5 2430M @ 2.4GHz
    Memory
    8 GB DDR3 @ 1600MHz Dual Channel ^_^
    Graphics Card(s)
    Intel HD 3000 B-)
    Screen Resolution
    1366x768
    Hard Drives
    Toshiba 500 GB
    Browser
    Google Chrome
    Antivirus
    Windows Defender & Common Sense!

KimK

New Member
I have ran the memtest and it seems to be no errors. I will hold on before I remove any program and devices as I got frustrated yesterday when my computer crashed two times a row while editing a video, so I did some research on google and found out that someone with the same problem had to updatade the Intel Chipset Drivers. So I googled on my motherboards manufacturer (MSI) and downloaded the Live Updater (I had forgotten totally that it exists). Found out that I had an update on my motherboard and had not installed the Intel Chipset Driver at all.

I will be back in a few days with the results to see how it goes and if the crashes continue I will try out your suggestion. Thanks :)
 

My Computer

System One

  • OS
    Windows 8.1

blueelvis

OMG Debugger!
VIP Member
Pro User
I have ran the memtest and it seems to be no errors. I will hold on before I remove any program and devices as I got frustrated yesterday when my computer crashed two times a row while editing a video, so I did some research on google and found out that someone with the same problem had to updatade the Intel Chipset Drivers. So I googled on my motherboards manufacturer (MSI) and downloaded the Live Updater (I had forgotten totally that it exists). Found out that I had an update on my motherboard and had not installed the Intel Chipset Driver at all.

I will be back in a few days with the results to see how it goes and if the crashes continue I will try out your suggestion. Thanks :)

Sure thing, let me know how it goes ^_^

In case of further problems, kindly upload a freshly generated SF Diagnostic ZIP File so that it could be analysed ^_^
 

My Computer

System One

  • OS
    Windows 8.1 Industry Pro B-)
    Computer type
    Laptop
    System Manufacturer/Model
    Toshiba
    CPU
    Core I5 2430M @ 2.4GHz
    Memory
    8 GB DDR3 @ 1600MHz Dual Channel ^_^
    Graphics Card(s)
    Intel HD 3000 B-)
    Screen Resolution
    1366x768
    Hard Drives
    Toshiba 500 GB
    Browser
    Google Chrome
    Antivirus
    Windows Defender & Common Sense!

KimK

New Member
I have ran the memtest and it seems to be no errors. I will hold on before I remove any program and devices as I got frustrated yesterday when my computer crashed two times a row while editing a video, so I did some research on google and found out that someone with the same problem had to updatade the Intel Chipset Drivers. So I googled on my motherboards manufacturer (MSI) and downloaded the Live Updater (I had forgotten totally that it exists). Found out that I had an update on my motherboard and had not installed the Intel Chipset Driver at all.

I will be back in a few days with the results to see how it goes and if the crashes continue I will try out your suggestion. Thanks :)

Sure thing, let me know how it goes ^_^

In case of further problems, kindly upload a freshly generated SF Diagnostic ZIP File so that it could be analysed ^_^

I almost forgot, but my computer works fine after I updated my BIOS and installed the Intel Chip Driver. Haven't had a crash since that. Thanks :)
 

My Computer

System One

  • OS
    Windows 8.1

blueelvis

OMG Debugger!
VIP Member
Pro User
I almost forgot, but my computer works fine after I updated my BIOS and installed the Intel Chip Driver. Haven't had a crash since that. Thanks :)
Glad to hear that the issue has been solved ^_^.

Thanks for posting back with the solution.

Regards,
Pranav
 

My Computer

System One

  • OS
    Windows 8.1 Industry Pro B-)
    Computer type
    Laptop
    System Manufacturer/Model
    Toshiba
    CPU
    Core I5 2430M @ 2.4GHz
    Memory
    8 GB DDR3 @ 1600MHz Dual Channel ^_^
    Graphics Card(s)
    Intel HD 3000 B-)
    Screen Resolution
    1366x768
    Hard Drives
    Toshiba 500 GB
    Browser
    Google Chrome
    Antivirus
    Windows Defender & Common Sense!

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Top