BSOD; I need an expert. IRQL_NOT_LESS_OR_EQUAL; UNEXPECTED_KERNEL_MODE_TRAP

[KuroShinigami]

I've had various BlueScreens in the last few days, all of which occured with a delay of 4 days inbetween.

I ran several tests, memtest, chkdsk, prime95 and FurMark all without failure ( aside from prime95 peaking at 68°C after a while. [ still no issues found in the test ]
Chkdsk failed one time during setup and I had to reinstall Win 7 fresh. )

I'm in dire need of some help here since I'm getting anxious and don't dare to play games anymore, just now the last one occured while just browsing the web so I assume temperature is something completely unrelated.

I hope you guys can help me figure out an exact answer to my problem so I can replace parts or fix it by software/updates.

My specs:
AMD FX 8350 ( 4,0ghz )
ASRock 870 Extreme 3 R2.0
Nvidia GTX 970
BeQuiet 600W

Screenshots to crashes included and I'll upload the minidumps and analysis if you want to.

http://pokit.org/get/?3b1c0a6e1acfc8c3f7607c20cb36cba9.jpg
http://pokit.org/get/?59543ae53fee7e33391eaffd10e668ce.jpg
http://pokit.org/get/?4c0da1d8928cd60ec89f0a09fdef246e.jpg


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c52730
Debug session time: Sat Jul 18 04:15:13.540 2015 (UTC - 4:00)
System Uptime: 3 days 2:43:50.679
*******************************************************************************
* *
* 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: fffffa80111eb8d7, 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: fffff80002a85911, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbc100
GetUlongFromAddress: unable to read from fffff80002cbc1c0
fffffa80111eb8d7 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeDelayExecutionThread+85
fffff800`02a85911 4488af67010000 mov byte ptr [rdi+167h],r13b

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: chrome.exe

TRAP_FRAME: fffff8800d8848b0 -- (.trap 0xfffff8800d8848b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000003dcfa00
rdx=0000000003dcfa00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a85911 rsp=fffff8800d884a40 rbp=fffff8800d884b60
r8=0000000000000001 r9=0000000000000002 r10=fffffa8007c02900
r11=0000000000000970 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeDelayExecutionThread+0x85:
fffff800`02a85911 4488af67010000 mov byte ptr [rdi+167h],r13b ds:00000000`00000167=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a7ee69 to fffff80002a7f8c0

STACK_TEXT:
fffff880`0d884768 fffff800`02a7ee69 : 00000000`0000000a fffffa80`111eb8d7 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0d884770 fffff800`02a7dae0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000285`8f9cf100 : nt!KiBugCheckDispatch+0x69
fffff880`0d8848b0 fffff800`02a85911 : fffffa80`097f79d0 00000000`00000000 00000000`00000005 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0d884a40 fffff800`02d7471e : fffffa80`101eb770 00000000`03dcfaf0 00000285`8f9cf100 fffff800`00000005 : nt!KeDelayExecutionThread+0x85
fffff880`0d884ab0 fffff800`02a7eb53 : 00000285`8fa7dac0 fffff880`0d884b60 ffffffff`fffcf2c0 00000000`00000001 : nt!NtDelayExecution+0x59
fffff880`0d884ae0 00000000`76e9defa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03dcfac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e9defa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeDelayExecutionThread+85
fffff800`02a85911 4488af67010000 mov byte ptr [rdi+167h],r13b

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KeDelayExecutionThread+85

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 556356e8

FAILURE_BUCKET_ID: X64_0xA_nt!KeDelayExecutionThread+85

BUCKET_ID: X64_0xA_nt!KeDelayExecutionThread+85

Followup: MachineOwner

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




Thanks to whom might help.

 

[johnbl]

the second one was a double fault. A exception that happens while the exception handler is running.

you will want to make sure you have all overclocking turned off, uninstall any overclocking drivers.
if you still get the problem then, you need to change the memory dump type from minidump to kernel memory dump, then run cmd.exe as an admin and run
verifier.exe /standard /all
and reboot and wait for the next bugcheck.

note use:
verifier.exe /reset
to turn off verifier flags after you are done testing or your machine will run slowly until you do.

with verifier turned on you might catch a driver that has problems and it will be named. With the kernel memory dump the debug info will not be stripped out of the memory dump and someone can take a look in the windows debugger as to the cause or name of the device that is having problems.

the memory references looks like a valid memory address but it could still be wrong with some bits flipped.
you might run memtest86 and confirm your hardware is working correctly.

if you post the memory dumps to a server, I can use the debugger to check for certain memory corruptions:
command in the debugger is
!for_each_module !chkimg @#ModuleName
(but will return errors for all drivers that microsoft does not provide)

 

[KuroShinigami]

the second one was a double fault. A exception that happens while the exception handler is running.

you will want to make sure you have all overclocking turned off, uninstall any overclocking drivers.
if you still get the problem then, you need to change the memory dump type from minidump to kernel memory dump, then run cmd.exe as an admin and run
verifier.exe /standard /all
and reboot and wait for the next bugcheck.

note use:
verifier.exe /reset
to turn off verifier flags after you are done testing or your machine will run slowly until you do.

with verifier turned on you might catch a driver that has problems and it will be named. With the kernel memory dump the debug info will not be stripped out of the memory dump and someone can take a look in the windows debugger as to the cause or name of the device that is having problems.

the memory references looks like a valid memory address but it could still be wrong with some bits flipped.
you might run memtest86 and confirm your hardware is working correctly.

if you post the memory dumps to a server, I can use the debugger to check for certain memory corruptions:
command in the debugger is
!for_each_module !chkimg @#ModuleName
(but will return errors for all drivers that microsoft does not provide)

I do have a full memory.dmp available here; ( Although it is 112mb in compressed size )
Thanks a lot for your help Johnbl!
I can run a memtest86 again, although it said no issues found last time, I will also use the verifier as you said and stress the pc with games on purpose.
Along the way I uninstalled a driver of a defective headset, hoping for a change.

http://www.filedropper.com/memorydmp

 

[johnbl]

i think the filedropper service is throttled, you might want to put the file on a different server like microsoft onedrive or mediafire.

I downloaded 10 mb in about 4 mins so far.

the second one was a double fault. A exception that happens while the exception handler is running.

you will want to make sure you have all overclocking turned off, uninstall any overclocking drivers.
if you still get the problem then, you need to change the memory dump type from minidump to kernel memory dump, then run cmd.exe as an admin and run
verifier.exe /standard /all
and reboot and wait for the next bugcheck.

note use:
verifier.exe /reset
to turn off verifier flags after you are done testing or your machine will run slowly until you do.

with verifier turned on you might catch a driver that has problems and it will be named. With the kernel memory dump the debug info will not be stripped out of the memory dump and someone can take a look in the windows debugger as to the cause or name of the device that is having problems.

the memory references looks like a valid memory address but it could still be wrong with some bits flipped.
you might run memtest86 and confirm your hardware is working correctly.

if you post the memory dumps to a server, I can use the debugger to check for certain memory corruptions:
command in the debugger is
!for_each_module !chkimg @#ModuleName
(but will return errors for all drivers that microsoft does not provide)

I do have a full memory.dmp available here; ( Although it is 112mb in compressed size )
Thanks a lot for your help Johnbl!
I can run a memtest86 again, although it said no issues found last time, I will also use the verifier as you said and stress the pc with games on purpose.
Along the way I uninstalled a driver of a defective headset, hoping for a change.

http://www.filedropper.com/memorydmp

 

[KuroShinigami]

i think the filedropper service is throttled, you might want to put the file on a different server like microsoft onedrive or mediafire.

I downloaded 10 mb in about 4 mins so far.

the second one was a double fault. A exception that happens while the exception handler is running.

you will want to make sure you have all overclocking turned off, uninstall any overclocking drivers.
if you still get the problem then, you need to change the memory dump type from minidump to kernel memory dump, then run cmd.exe as an admin and run
verifier.exe /standard /all
and reboot and wait for the next bugcheck.

note use:
verifier.exe /reset
to turn off verifier flags after you are done testing or your machine will run slowly until you do.

with verifier turned on you might catch a driver that has problems and it will be named. With the kernel memory dump the debug info will not be stripped out of the memory dump and someone can take a look in the windows debugger as to the cause or name of the device that is having problems.

the memory references looks like a valid memory address but it could still be wrong with some bits flipped.
you might run memtest86 and confirm your hardware is working correctly.

if you post the memory dumps to a server, I can use the debugger to check for certain memory corruptions:
command in the debugger is
!for_each_module !chkimg @#ModuleName
(but will return errors for all drivers that microsoft does not provide)

I do have a full memory.dmp available here; ( Although it is 112mb in compressed size )
Thanks a lot for your help Johnbl!
I can run a memtest86 again, although it said no issues found last time, I will also use the verifier as you said and stress the pc with games on purpose.
Along the way I uninstalled a driver of a defective headset, hoping for a change.

http://www.filedropper.com/memorydmp

I will upload on mediafire asap.

 

[KuroShinigami]

i think the filedropper service is throttled, you might want to put the file on a different server like microsoft onedrive or mediafire.

I downloaded 10 mb in about 4 mins so far.

the second one was a double fault. A exception that happens while the exception handler is running.

you will want to make sure you have all overclocking turned off, uninstall any overclocking drivers.
if you still get the problem then, you need to change the memory dump type from minidump to kernel memory dump, then run cmd.exe as an admin and run
verifier.exe /standard /all
and reboot and wait for the next bugcheck.

note use:
verifier.exe /reset
to turn off verifier flags after you are done testing or your machine will run slowly until you do.

with verifier turned on you might catch a driver that has problems and it will be named. With the kernel memory dump the debug info will not be stripped out of the memory dump and someone can take a look in the windows debugger as to the cause or name of the device that is having problems.

the memory references looks like a valid memory address but it could still be wrong with some bits flipped.
you might run memtest86 and confirm your hardware is working correctly.

if you post the memory dumps to a server, I can use the debugger to check for certain memory corruptions:
command in the debugger is
!for_each_module !chkimg @#ModuleName
(but will return errors for all drivers that microsoft does not provide)

I do have a full memory.dmp available here; ( Although it is 112mb in compressed size )
Thanks a lot for your help Johnbl!
I can run a memtest86 again, although it said no issues found last time, I will also use the verifier as you said and stress the pc with games on purpose.
Along the way I uninstalled a driver of a defective headset, hoping for a change.

http://www.filedropper.com/memorydmp

:I Okay.. uploading would take another hour.. I have like 0.4mb/s upload..

 

[johnbl]

basically, install usb 3.0 driver, update BIOS, and update Ethernet driver.
I think the bugcheck was related to problems in the USB subsystem but the updated ethernet driver will help your virus scanner and Nvidia streaming software from causing problems with your system.

if you continue to have problems, start cmd.exe as an admin, then run
verifier.exe /standard /all
then reboot. This will force windows to check for driver issues and will force a bugcheck and save debug info on the problem. Note: use
verifier.exe /reset
to turn off the checking after you are done testing or your machine will run slowly until you do.

-------------
download is done,

looking at the memory dump now.

first start by updating your network driver
Atheros NIC driver
\SystemRoot\system32\DRIVERS\L1C62x64.sys Tue Aug 24 02:14:01 2010

it should be the L1c driver on this page:
https://www.atheros.cz/atheros-network-drivers.html
or here:https://www.atheros.cz/atheros-wireless-download.php?chipset=56&system=6
the driver has 3 years of updates and will make your virus scanner and nvidia streaming software work much better.

other issues:
bios is kind of old, BIOS versions before 2013 tend to have issues with USB devices, you might want to update the BIOS.

machine info:
Manufacturer ASRock
Product 870 Extreme3 R2.0
Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4000MHz
Current Speed 4000MHz

BIOS Version P1.70
BIOS Release Date 11/01/2011

there is a p1.80 version BIOS on http://www.asrock.com/mb/AMD/870%20Extreme3%20R2.0/?cat=Download&os=BIOS
it is only one month newer than the one you have but might have some fixes.

I will take a quick look in the debugger to see if I can find the actual cause of the bugcheck.

I see some problems that look USB related.
you have a device that failed to initialize, most likely a failed driver install.
here is the device string:
InstancePath is "PCI\VEN_1B6F&DEV_7023&SUBSYS_70231849&REV_01\4&4e58618&0&0048"
you might want to go to your motherboard vendors website and update the BIOS and drivers.
the vendor id of the PCI device that is missing a driver it 1b6f which is the id for Etron.
http://www.pcidatabase.com/vendor_details.php?id=1710
most likely the etron usb 3.0 driver.
from the debugger: here is the actual ethernet controller you have:
Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20)

(when looking for the driver AR8151 is the chip used in the card)

 

[KuroShinigami]

I'm giving it a try, thanks a lot for your time, I'm really really grateful, I just got another bluescreen with an entirely different message..
I'll just follow your steps for now though.

If something occurs, I'll report back here and in a new thread I assume.

Thanks again, really really much.

 

[KuroShinigami]

Here's the .dmp of the last crash, I don't know whether that helps you in anything, but it kind of made my head turn when it was yet another different bugcheck.

http://www.mediafire.com/download/122ym0gq1qetq2b/072015-28548-01.dmp

 

[johnbl]

the bughceck just shows that a bad memory address was passed to windows while you were running league of legends and it called a bugcheck. Memory address passed in was memory address 0x0.

looks like you are still running a 2010 version of your ethernet driver, I would update it to a current version.

you can run cmd.exe as an admin then run
verifier.exe /standard /all
and reboot
and it will make winodows check for common device driver errors and it will force a bugcheck and name the driver name that has the problem. You do this to prove what driver needs to be updated or you can just guess it is a bug in your old network driver (most likely)

Note: use verifier.exe /reset to turn off this checking when done testing.

Here's the .dmp of the last crash, I don't know whether that helps you in anything, but it kind of made my head turn when it was yet another different bugcheck.

http://www.mediafire.com/download/122ym0gq1qetq2b/072015-28548-01.dmp

 

[xKrusaderx]

the bughceck just shows that a bad memory address was passed to windows while you were running league of legends and it called a bugcheck. Memory address passed in was memory address 0x0.

looks like you are still running a 2010 version of your ethernet driver, I would update it to a current version.

you can run cmd.exe as an admin then run
verifier.exe /standard /all
and reboot
and it will make winodows check for common device driver errors and it will force a bugcheck and name the driver name that has the problem. You do this to prove what driver needs to be updated or you can just guess it is a bug in your old network driver (most likely)

Note: use verifier.exe /reset to turn off this checking when done testing.

Here's the .dmp of the last crash, I don't know whether that helps you in anything, but it kind of made my head turn when it was yet another different bugcheck.

http://www.mediafire.com/download/122ym0gq1qetq2b/072015-28548-01.dmp

Does this mean that League of legends is causing another issue beyond the ethernet driver? I have League installed as well and have the same issue even after updating NIC, BIOS, etc. I'm really interested in your comment.

UPDATE:


My computer goes through the whole download/update. Starts on the installation of Windows 10, completes copying all of the files and then gets 6% of the way through installing software and drivers and then pops up with just a plain IRQL_NOT_LESS_OR_EQUAL. There is no epfwwfp.sys or anything else, just the IRQL_NOT_LESS_OR_EQUAL. Then it restarts and windows update pops up and says that failed 1 update; Errors found C1900101-30018. I then run the windows update diagnostic test and it says that it corrects the following:

I've tried to redo the whole process again and it gets me in the same loop.

 

[johnbl]

bugchecks are not caused by apps. They are caused by the hardware and the interface to the hardware(drivers and BIOS). Apps just make system calls that end up using drivers which have bugs (assuming your system is stable and not overclocked) Newer programs may use newer features that a old driver may not have implemented correctly and that can cause the driver to bugcheck. Generally, you update the BIOS, update the various drivers and see if your problem is fixed. If not, you have to run diagnostics or turn on debugging flags to figure out the problem. (verifier.exe)

looks like microsoft is using some new error codes
Errors found C1900101-30018
I am not sure what this one is. via google i found this:http://www.wiknix.com/solved-windows-8-1-installation-error-0xc1900104-when-install-via-usb-flash-drive/
looks like it might be that your drive partition is not marked as the active primary partition. (or your reserve partition is too small)

the bughceck just shows that a bad memory address was passed to windows while you were running league of legends and it called a bugcheck. Memory address passed in was memory address 0x0.

looks like you are still running a 2010 version of your ethernet driver, I would update it to a current version.

you can run cmd.exe as an admin then run
verifier.exe /standard /all
and reboot
and it will make winodows check for common device driver errors and it will force a bugcheck and name the driver name that has the problem. You do this to prove what driver needs to be updated or you can just guess it is a bug in your old network driver (most likely)

Note: use verifier.exe /reset to turn off this checking when done testing.

Here's the .dmp of the last crash, I don't know whether that helps you in anything, but it kind of made my head turn when it was yet another different bugcheck.

http://www.mediafire.com/download/122ym0gq1qetq2b/072015-28548-01.dmp

Does this mean that League of legends is causing another issue beyond the ethernet driver? I have League installed as well and have the same issue even after updating NIC, BIOS, etc. I'm really interested in your comment.

UPDATE:


My computer goes through the whole download/update. Starts on the installation of Windows 10, completes copying all of the files and then gets 6% of the way through installing software and drivers and then pops up with just a plain IRQL_NOT_LESS_OR_EQUAL. There is no epfwwfp.sys or anything else, just the IRQL_NOT_LESS_OR_EQUAL. Then it restarts and windows update pops up and says that failed 1 update; Errors found C1900101-30018. I then run the windows update diagnostic test and it says that it corrects the following:

I've tried to redo the whole process again and it gets me in the same loop.

 

[xKrusaderx]

Thanks for checking that johnbl. I've gone through and checked to see on diskmanagement if the drive was big enough and was the active and primary and it is. I have a Samsung SSD 840 EVO which isn't your standard, but it hasn't given me any problems. I checked the link you provided and I don't have a PortableOperatingSystem registry to edit. Would I need to change the size of either my recovery or EFI System Partition? Which partition is the reserve partion?

Update:

Here is a look from my disk manager.

bugchecks are not caused by apps. They are caused by the hardware and the interface to the hardware(drivers and BIOS). Apps just make system calls that end up using drivers which have bugs (assuming your system is stable and not overclocked) Newer programs may use newer features that a old driver may not have implemented correctly and that can cause the driver to bugcheck. Generally, you update the BIOS, update the various drivers and see if your problem is fixed. If not, you have to run diagnostics or turn on debugging flags to figure out the problem. (verifier.exe)

looks like microsoft is using some new error codes
Errors found C1900101-30018
I am not sure what this one is. via google i found this:http://www.wiknix.com/solved-windows-8-1-installation-error-0xc1900104-when-install-via-usb-flash-drive/
looks like it might be that your drive partition is not marked as the active primary partition. (or your reserve partition is too small)

the bughceck just shows that a bad memory address was passed to windows while you were running league of legends and it called a bugcheck. Memory address passed in was memory address 0x0.

looks like you are still running a 2010 version of your ethernet driver, I would update it to a current version.

you can run cmd.exe as an admin then run
verifier.exe /standard /all
and reboot
and it will make winodows check for common device driver errors and it will force a bugcheck and name the driver name that has the problem. You do this to prove what driver needs to be updated or you can just guess it is a bug in your old network driver (most likely)

Note: use verifier.exe /reset to turn off this checking when done testing.

Here's the .dmp of the last crash, I don't know whether that helps you in anything, but it kind of made my head turn when it was yet another different bugcheck.

http://www.mediafire.com/download/122ym0gq1qetq2b/072015-28548-01.dmp

Does this mean that League of legends is causing another issue beyond the ethernet driver? I have League installed as well and have the same issue even after updating NIC, BIOS, etc. I'm really interested in your comment.

UPDATE:


My computer goes through the whole download/update. Starts on the installation of Windows 10, completes copying all of the files and then gets 6% of the way through installing software and drivers and then pops up with just a plain IRQL_NOT_LESS_OR_EQUAL. There is no epfwwfp.sys or anything else, just the IRQL_NOT_LESS_OR_EQUAL. Then it restarts and windows update pops up and says that failed 1 update; Errors found C1900101-30018. I then run the windows update diagnostic test and it says that it corrects the following:

I've tried to redo the whole process again and it gets me in the same loop.

 

[Brandon-]

I've had various BlueScreens in the last few days, all of which occured with a delay of 4 days inbetween.

I ran several tests, memtest, chkdsk, prime95 and FurMark all without failure ( aside from prime95 peaking at 68°C after a while. [ still no issues found in the test ]
Chkdsk failed one time during setup and I had to reinstall Win 7 fresh. )

I'm in dire need of some help here since I'm getting anxious and don't dare to play games anymore, just now the last one occured while just browsing the web so I assume temperature is something completely unrelated.

I hope you guys can help me figure out an exact answer to my problem so I can replace parts or fix it by software/updates.

My specs:
AMD FX 8350 ( 4,0ghz )
ASRock 870 Extreme 3 R2.0
Nvidia GTX 970
BeQuiet 600W

Screenshots to crashes included and I'll upload the minidumps and analysis if you want to.

http://pokit.org/get/?3b1c0a6e1acfc8c3f7607c20cb36cba9.jpg
http://pokit.org/get/?59543ae53fee7e33391eaffd10e668ce.jpg
http://pokit.org/get/?4c0da1d8928cd60ec89f0a09fdef246e.jpg


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c52730
Debug session time: Sat Jul 18 04:15:13.540 2015 (UTC - 4:00)
System Uptime: 3 days 2:43:50.679
*******************************************************************************
* *
* 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: fffffa80111eb8d7, 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: fffff80002a85911, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbc100
GetUlongFromAddress: unable to read from fffff80002cbc1c0
fffffa80111eb8d7 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeDelayExecutionThread+85
fffff800`02a85911 4488af67010000 mov byte ptr [rdi+167h],r13b

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: chrome.exe

TRAP_FRAME: fffff8800d8848b0 -- (.trap 0xfffff8800d8848b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000003dcfa00
rdx=0000000003dcfa00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a85911 rsp=fffff8800d884a40 rbp=fffff8800d884b60
r8=0000000000000001 r9=0000000000000002 r10=fffffa8007c02900
r11=0000000000000970 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeDelayExecutionThread+0x85:
fffff800`02a85911 4488af67010000 mov byte ptr [rdi+167h],r13b ds:00000000`00000167=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a7ee69 to fffff80002a7f8c0

STACK_TEXT:
fffff880`0d884768 fffff800`02a7ee69 : 00000000`0000000a fffffa80`111eb8d7 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0d884770 fffff800`02a7dae0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000285`8f9cf100 : nt!KiBugCheckDispatch+0x69
fffff880`0d8848b0 fffff800`02a85911 : fffffa80`097f79d0 00000000`00000000 00000000`00000005 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0d884a40 fffff800`02d7471e : fffffa80`101eb770 00000000`03dcfaf0 00000285`8f9cf100 fffff800`00000005 : nt!KeDelayExecutionThread+0x85
fffff880`0d884ab0 fffff800`02a7eb53 : 00000285`8fa7dac0 fffff880`0d884b60 ffffffff`fffcf2c0 00000000`00000001 : nt!NtDelayExecution+0x59
fffff880`0d884ae0 00000000`76e9defa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03dcfac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e9defa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeDelayExecutionThread+85
fffff800`02a85911 4488af67010000 mov byte ptr [rdi+167h],r13b

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KeDelayExecutionThread+85

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 556356e8

FAILURE_BUCKET_ID: X64_0xA_nt!KeDelayExecutionThread+85

BUCKET_ID: X64_0xA_nt!KeDelayExecutionThread+85

Followup: MachineOwner

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<




Thanks to whom might help.

Hi Kuro, not sure if you got this fixed but that BSOD is usually a RAM problem. Take your RAM sticks out and test each one at a time.

 

[johnbl]

none of your partitions are marked active.
(the currently selected boot device) this might be related to the EFI partition and how the
Unified Extensible Firmware Interface (UEFI) works. I just don't know because I have never owned a machine that actually used it.

you might delete the entire partition data: http://www.howtogeek.com/215349/how-to-remove-an-efi-system-partition-or-gpt-protective-partition-from-a-drive-in-windows/

but be be cautious, I have not deleted a EFI partition before. you might have to turn something off in the BIOS. These new functions were made to prevent modifications of low level functions and may block booting if it sees something it does not like. IE the bios sees a boot sector that has been modified it might refuse to boot the system.