Multiple random BSODs on new computer

C

cupidincoke

Member
Joined
Dec 21, 2019
Posts
7
Hi experts, I have just built a computer for my girlfriend for christmas and I'm encountering multiple bsods.
Most common error would be IRQL_NOT_LESS_OR_EQUAL

Things I have done:
Clean install of win 10
Windows memory Diagnostics / Memtest86 Single and double sticks with no errors.
Updated Bio/windows updates/Drivers

I have used bluescreenview and noticed the cause is ntoskrnl.exe

Here's the specs: http://speccy.piriform.com/results/cWHLjieOYSTSFG8RTJIEOzi


Please help me as I'm at my wits end. Hope i can fix it in time as a present for my girlfriend for christmas!
 

Attachments

I see you have Driver Verifier enabled. Enable all standard options and 2 additional options (Force pending I / O request and IRP Logging) and enable this Driver Verifier for all drivers except Microsoft drivers
 
MrPepka said:
I see you have Driver Verifier enabled. Enable all standard options and 2 additional options (Force pending I / O request and IRP Logging) and enable this Driver Verifier for all drivers except Microsoft drivers
Click to expand...
Ok. Is there anything that I have to upload to show you?
 
New crash dumps if some blue screens still show up
 
Rich (BB code): 
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80172c9cfc3, Virtual address for the attempted write.
Arg2: 0900000001fe6121, PTE contents.
Arg3: fffff801756646e0, (reserved) << Trap frame of last saved context
Arg4: 000000000000000a, (reserved)

Rich (BB code): 
0: kd> !pte fffff80172c9cfc3
                                           VA fffff80172c9cfc3
PXE at FFFFAB55AAD56F80    PPE at FFFFAB55AADF0028    PDE at FFFFAB55BE005CB0    PTE at FFFFAB7C00B964E0
contains 0000000003808063  contains 0000000003809063  contains 0000000003815063  contains 0900000001FE6121
pfn 3808      ---DA--KWEV  pfn 3809      ---DA--KWEV  pfn 3815      ---DA--KWEV  pfn 1fe6      -G--A--KREV

As the bugcheck suggests, it appears that a driver has attempted to write to a memory address which does not have permit write access.

The call stack from the last saved context, suggests that a graphics card driver may be to blame here:

Rich (BB code): 
0: kd> k
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 fffff801`75664870 fffff80e`3a3d3b27 nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x44
01 fffff801`756648a0 fffff801`72cd7185 dxgkrnl!DpiFdoDpcForIsr+0x37 << Graphics library call
02 fffff801`756648f0 fffff801`72cd67df nt!KiExecuteAllDpcs+0x305
03 fffff801`75664a30 fffff801`72dd62c4 nt!KiRetireDpcList+0x1ef
04 fffff801`75664c60 00000000`00000000 nt!KiIdleLoop+0x84

I've dumped the entire thread stack, and it appears that the AMD graphics card driver may be the culprit.

Rich (BB code): 
0: kd> lmvm atikmdag
Browse full module list
start             end                 module name
fffff80e`3ed20000 fffff80e`42c05000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\u0349841.inf_amd64_01bbb629805d901e\B349895\atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Dec 16 10:47:15 2019 (5DF7D133)
    CheckSum:         03EADCBB
    ImageSize:        03EE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would recommend uninstalling the AMD graphics card driver, and then installing the latest version again directly from the download page.

However, some of the dump files appear to be corrupt, which could suggest issues with the RAM. Have you ensured that the RAM modules are seated correctly and are compatible with each other?

Please run this memory test for each individual stick in each individual slot - Test RAM with PassMark MemTest86

Alternatively, you may wish to run the system with one stick at a time and see if it remains stable.
 
x BlueRobot said:
Rich (BB code): 
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80172c9cfc3, Virtual address for the attempted write.
Arg2: 0900000001fe6121, PTE contents.
Arg3: fffff801756646e0, (reserved) << Trap frame of last saved context
Arg4: 000000000000000a, (reserved)

Rich (BB code): 
0: kd> !pte fffff80172c9cfc3
                                           VA fffff80172c9cfc3
PXE at FFFFAB55AAD56F80    PPE at FFFFAB55AADF0028    PDE at FFFFAB55BE005CB0    PTE at FFFFAB7C00B964E0
contains 0000000003808063  contains 0000000003809063  contains 0000000003815063  contains 0900000001FE6121
pfn 3808      ---DA--KWEV  pfn 3809      ---DA--KWEV  pfn 3815      ---DA--KWEV  pfn 1fe6      -G--A--KREV

As the bugcheck suggests, it appears that a driver has attempted to write to a memory address which does not have permit write access.

The call stack from the last saved context, suggests that a graphics card driver may be to blame here:

Rich (BB code): 
0: kd> k
  *** Stack trace for last set context - .thread/.cxr resets it
# Child-SP          RetAddr           Call Site
00 fffff801`75664870 fffff80e`3a3d3b27 nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x44
01 fffff801`756648a0 fffff801`72cd7185 dxgkrnl!DpiFdoDpcForIsr+0x37 << Graphics library call
02 fffff801`756648f0 fffff801`72cd67df nt!KiExecuteAllDpcs+0x305
03 fffff801`75664a30 fffff801`72dd62c4 nt!KiRetireDpcList+0x1ef
04 fffff801`75664c60 00000000`00000000 nt!KiIdleLoop+0x84

I've dumped the entire thread stack, and it appears that the AMD graphics card driver may be the culprit.

Rich (BB code): 
0: kd> lmvm atikmdag
Browse full module list
start             end                 module name
fffff80e`3ed20000 fffff80e`42c05000   atikmdag T (no symbols)      
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\u0349841.inf_amd64_01bbb629805d901e\B349895\atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Dec 16 10:47:15 2019 (5DF7D133)
    CheckSum:         03EADCBB
    ImageSize:        03EE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would recommend uninstalling the AMD graphics card driver, and then installing the latest version again directly from the download page.

However, some of the dump files appear to be corrupt, which could suggest issues with the RAM. Have you ensured that the RAM modules are seated correctly and are compatible with each other?

Please run this memory test for each individual stick in each individual slot - Test RAM with PassMark MemTest86

Alternatively, you may wish to run the system with one stick at a time and see if it remains stable.
Click to expand...


Thanks for you detailed analysis. I have reinstalled the driver. Will see if it helps.


I have ran Memtest86 and windows memory diagnostics multiple times (each with 4 passes), both single and double sticks. No errors.

I have uploaded a new sysnative zip above for your perusal
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top