Frequent blue screen's of death

Mido123

Reputable
Aug 2, 2015
13
0
4,510
Hi

I have been getting frequent and random blue screen's of deaths with various bug check codes, however the address cause seems to be the same, does this mean I should just get a new graphics card? or install a driver before the latest?

Below are the two dump files
Dump File : 073115-31668-01.dmp
Crash Time : 7/31/2015 8:01:13 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`030809a5
Parameter 3 : fffff880`0b744fe0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f840
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.17795 (win7_gdr.150318-1623)
Processor : x64
Crash Address : ntoskrnl.exe+6f840
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\073115-31668-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 350,832
Dump File Time : 7/31/2015 8:02:19 PM


Dump File : 080315-30513-01.dmp
Crash Time : 8/3/2015 12:36:15 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041790
Parameter 2 : fffffa80`033a9da0
Parameter 3 : 00000000`0000ffff
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+7fd00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080315-30513-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 378,744
Dump File Time : 8/3/2015 12:37:31 AM


I've googled the causes of the bug check codes and i know the cause and I've taken some steps to try and fix them. I've tried unclocking my graphics card, setting the correct voltages to my RAM from my UEFI and applying the correct XMP profile. Adding to that I've done a memtest on all 4 of my 4GB DDR3 RAMS (1 pass though which took 5.5 hours) and there were zero errors. I;ve also ran a windows memory diagnostic and it displayed nothing. At this point i've given up, because i've had endless blue screens happen to me and i can't seem to pinpoint the reason.. please help. I will try anything at this point

Thanks!
 
first one is memory management bugcheck because a bad memory address was passed to windows.
the second one is the memory manager saying that the mapping between what is located in memory to the pagefile.sys entries has been corrupted.

I would update the BIOS, reset it to defaults and boot and run memtest86 on its own boot image to confirm you memory settings are correct.
(sounds like you did the memtest but you should confirm the BIOS is up to date and has been reset to defaults)

I would then update the motherboards chipset drivers from the vendors website. I would most likely move the storage to another sata port on the primary controller (slower one).
I would run crystaldiskinfo.exe and take a look at SMART error data.
I might turn off the systems virutal memory (pagefile.sys) and reboot and turn it back on.
If I had a solid state dirve, I would check the firmware for known updates and maybe boot into BIOS and leave the system in BIOS for a few hours to let the SSD do its clean up routines. (windows 7 is not too SSD aware)

if you think window is the problem: check the windows core files for corruption, run cmd.exe as an admin then run
sfc.exe /scannow
and confirm that all corruptions are fixed, reboot and run the command again . ( sometimes malware will undo the fixes)
then run a malwarebytes scan. if you don't find anything then there are settings to help debug the problem and find the cause of the corruption. (verifier.exe)


 

Mido123

Reputable
Aug 2, 2015
13
0
4,510


Thanks for your very elaborate reply I'll definitely try those things later today.

I've recently re-installed windows and all of my motherboard's driver's are up to date but I will do as you said and run a memtest today anyway after setting my UEFI to the factory defaults.

However, I'm just not sure what you mean about "move the storage to another sata port on the primary controller" are you telling me to remove the sata cable thats connected to my hard disk to a different port on the mother board? How can I tell if it is a slower one, from the manual?? Or is there anything physically written on it that says it is slower. I have a fatal1ity p67 professional mother board by the way

Thanks again for replying I'll try all those things as you mentioned, I was not aware I can do those things


I was jsut trying to re-download memtest when i got another BSOD, here is the dump file..
Dump File : 080315-42775-01.dmp
Crash Time : 8/3/2015 9:10:26 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffda80`14459990
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`03146fef
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+7fd00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080315-42775-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 335,664
Dump File Time : 8/3/2015 9:11:52 PM

The same driver is causing this again but it is it another memory management problem again? If it is I'm tempted to just buy new RAM chips and get this over with. I'm going to test each RAM chip now
 

Mido123

Reputable
Aug 2, 2015
13
0
4,510


My motherboard is a fatal1ity p67 professional, I have an intel core i7 processor As for the RAMS I do not recall if they came in a single package or not but for the specs they are pretty much all identical. All of my RAMS are a G Class SNIPER
F3-12800CLD9-8GBSR2
DDR3-1600 PC3- 12800 4GBx2
XMP CL9-9-9-24 1.25v

The only difference is the barcode number where a pair end in 66 and 67 and the other two end in 24 and 25, but I do not think that makes any difference.

I've tried going to my UEFI and manually setting in XMP CL9-9-9-24 1.25v but I still got a BSOD

Hope this gives you enough infot to help diagnose the problem, thanks for replying!
 
yes, a different port, often many motherboards will come with two SATA controllers. one that is supported directly with the CPU chipset and a faster one from an add on chip. Often the driver for the add on chipset has bugs. You would have to look at your motherboard manual but often the ports will be color coded for the different speeds.



 

Mido123

Reputable
Aug 2, 2015
13
0
4,510


I'll try that once i do the memtest, I just got another BSOD with this dump file..

Dump File : 080315-42775-01.dmp
Crash Time : 8/3/2015 9:10:26 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffda80`14459990
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`03146fef
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor : x64
Crash Address : ntoskrnl.exe+7fd00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080315-42775-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 335,664
Dump File Time : 8/3/2015 9:11:52 PM
 

Brandon-

Reputable
Aug 1, 2015
322
0
4,960

IRQL_LESS_OR_NOT_EQUAL is usually a RAM problem. Take all 4 sticks of RAM out of your Motherboard, and insert 1 at a time until you find the faulty stick.
 
Windows attempt to load drivers in different orders on each boot. It does this so malware can not just attack a single memory location. This also means that one bad driver will corrupt the memory of the driver that stores its data next to it in memory. This means you will get several different bugchecks for the same problem. (generally about 5 different ones)

to find these type of problems you should put your memory dump on a server and post a link. Often, people can just look at your driver list and tell you the known bad driver name/date.

it the list looks ok, then you would want to start cmd.exe as an admin then run
verifier.exe /standard /all
and reboot your system, this will force winodows to look for common driver errors that cause corruption and it will force a bugcheck at the time of the corruption rather than when the victim driver attempts to use the corrupted data.
in this case the bad driver will be named in the memory dump file.
Note: turn off verifier when you are done testing:
verifier.exe /reset
or you machine will run 20% slower until you run the command.

-----------
all that that bugcheck means is that the system tried to read memory address
ffffda80`14459990 and that address was not currently paged into memory so the call failed.
(it was required to be in physical memory at the time of the call)

it looks like it might be a valid address so it might be just a driver bug.

You should put your actual memory dump on a server and post a link