BSOD related to ntoskrnl.exe

B

burnm3w1thf1r3

Member
I'm helping a friend with a BSOD issue. He's had them since the computer was built. And after resolving my issue related to ntoskrnl.exe and my ram being the issue I figured I would take a whack at it. Anyways the computer was never OC so that ruled that out. The issue I had was unsupported ram so I had to manually set the timing and voltage and all that. Which we did but he was still having issues.

Mobo: MSI 890FXA-GD65
Ram: F3-12800CL9D-8GBSR2 (2 sets, 4 sticks in total, 16gb)

I found on a different forum it was suggested to disable the "DCT Unganged Mode" which he just did and now we're testing it, I am currently waiting on the test results. In the mean time I was curious if using 4 sticks of ram could be the issue. Does his board permit the use of all 4 ram slots? If it does not which 2 slots should he be using? And in general is there anything other than manually settings the timing and disabling the DCT mode that would be worth trying? The only other thing I could think of is a bad ram stick which if the results produce a BSOD i will have him run a memtest86+ to figure that out.

Any other suggestions?
 
Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
Alright, since it is a friend's pc I'm going to have to have them run what you're asking and wait on them. Quick update in the mean time. I had them install whocrashed.exe which is how we know its the ntoskrnl.exe causing the crash. However I had him manually set the timing and other settings of the ram in his "advanced dram" settings in the BIOS and disable the DCT ungaged setting as recommended. He BSOD during a malewarebytes scan and this time the cause was the CDD.dll, which after looking that up is caused from bad ram or incorrectly configured ram.

So I'm having him reset the timing and such, but keep the DCT settings disabled. I will report back when I get some feedback. I will also tell him to download and run the program you suggested and hope we gets me some results.
 
johnb35 said:
Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
Click to expand...

Here are the results from what you requested.

==================================================
Dump File : 122414-33321-01.dmp
Crash Time : 12/24/2014 7:21:43 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa80`ffffff26
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`13da33dc
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+143dc
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122414-33321-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 291,440
Dump File Time : 12/24/2014 7:23:57 PM
==================================================
 
That points to your USB ports. If anything has been recently installed that uses a USB port (probably network adapter) then reinstall its respective drivers.
 
You must log in or register to reply here.
Back
Top