Constant BSOD

Zinnkio

Zinnkio

Zinnkio

Associate
Joined
27 Dec 2012
Posts
116
Computer was working fine yesterday and had been for a while on Windows 10 until I got a Irql_not_less_or_equal BSOD. It would consistently give me this error so I tried a clean install. Even through the clean installs I was given multiple BSODs:
-The error stated before
-Attempted_write_to_readonly_memory
-Driver_overran_stack_buffer
-Kernal_thread_priority_floor_violation
-unexpected_kernal_mode_trap (NTFS.sys)

I am lost at what to do.

Any help appreciated.
 
On Thu 13/08/2015 14:33:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-7453-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x13927)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80099C03927, 0xFFFFD001184D4C30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 13/08/2015 14:33:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x13927)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80099C03927, 0xFFFFD001184D4C30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 13/08/2015 12:20:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-9500-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x12989)
Bugcheck code: 0x7F (0x8, 0xFFFFF80119F2CE70, 0xFFFFA001E54CE1E0, 0xFFFFF8014D162989)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 13/08/2015 12:13:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-7921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0xBE (0xFFFFC0012D606AC0, 0x8000000105AD2101, 0xFFFFD00156C05590, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 13/08/2015 12:11:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081315-7640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0xF7 (0x2A81DDEDDE30, 0xA58F7FA5FD9C, 0xFFFF5A70805A0263, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Click to expand...

They're the BSODs that I've had since I've actually managed to get windows running. It said that It couldn't find any conflicting drivers...
 
Possibly. I am actually at a LAN sesh with the lads and I've installed the win 10 iso on a SanDisk USB drive using rufus because the USB doesn't actually show up using the official creation tool. I'll be in a position tomorrow to try an alternate, working copy of win10. Thanks for the suggestions so far!
 
Just used a different memory stick and tried to install Windows 10. Got a BSOD during the install bad_pool_header so still no luck. Gonna try again until it works.
 
Just got another BSOD too. The irql_not_less_or_equal one. Could my ssd be dying. The power was cut off abruptly 2 days ago and it seems to have been since that that it's been doing this constant BSOD thing.
 
Burn memtest to a CD (or USB stick) and run that.

Failing that, try another SATA cable, then HDD/SSD
 
Ran memtest and returned no errors. Tried a different sata port for my ssd, still reciveving BSODs. Tried a different hard drive with no luck also. I've tried both Windows 10 and 7 OSs and neither work. I'm really lost and frustrated. The error that appears the most is the irql_not_less_or_equal BSOD. I don't understand how it can throw a BSOD while it's actually installing windows. Is my motherboard dying do people reckon?
 
Swapped out the mobo for a friend's which seemed to help for a while but then I got the blue screens as I was updating windows 7 and now I'm getting them constantly again. Swapped gpu too to no avail. I tried every combination of connected SSDs and HDDs and none have helped. The only piece of hardware left is the cpu and I don't know if it would cause BSODs. Anyone have any guidance. Is it new computer time? :(
 
So I thought I'd give memtest another go and it's just thrown me a load of errors this time. No idea why it didn't before. Determining which stick it is and then I'll report back if there's any success.
 
When testing three sticks of RAM in slot 1, 2 and 3, memtest throws back errors. However when each stick is tested in each slot, there are no errors shown. There was a 4Gb Kingston stick coupled with 2x2Gb samsung sticks previously. They have always worked before but have recently decided to not work together. Because of this I'm having to run a single 4Gb stick. No BSODs at all any more. It seems a new RAM purchase is in order. Thanks for your help guys :D

Zinnkio
 
You must log in or register to reply here.
Back
Top Bottom