BSOD Cant seem to find a fix: Desperate!

[Kmb470]

Hey Guys,

I am new to the forum and I am brought here due to an unexpected BSOD I cant seem to figure out how to fix. I keep my machine pretty clean and constantly run CCleaner and MalwareBytes, and all my files are well organized, start-up generally limited to essentials, etc. Listed below is what I am seeing, so any help moving forward would be an absolute life saver.

Anytime I try to run the check for solutions, it just crashes again.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002EB47EF
BCP3: 0000000000000000
BCP4: 00000000FFFA0000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\080112-203409-01.dmp
C:\Users\Kevin Bowles\AppData\Local\Temp\WER-462667-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[FredeGail]

Hello Kmb and welcome to Sevenforums.

To be able to help you, we'd need you to attach some files in order for us to analyse your crash. The below link will guide you through some steps for catching these files. If you have any questions just ask us.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Best Regards,
Frederik.

 

[Kmb470]

Thank you Frederik!

My apologies for the delay, I have been on vacation for the past 2 weeks. That said, my problem hasnt gone away, natually.

I have followed the instructions from the link you posted, ran the tool as admin, and all links ran fine until I ran the windows one. A screen grab of the error received has been included in the zipped file.

Any thoughts on next steps would be greatly appreciated!

 

[FredeGail]

No problem.

You're getting this error because you haven't been running the software as an elevated program. When opening the SF Diagnostic Tool, right-click it and open it as Administrator.

BSOD Analyse

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: 00000000000000dd, 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: fffff80002ec8405, address which referenced memory

Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
:info: Be sure to check your warranty rules and regulations before opening your case.

* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.​

​

Best Regards,
Frederik.