Hi, I actually have another problem embedded inside of this BSOD that I will explain in a moment. I built my own pc this summer with specs that are way beyond the recommended requirements for my game (Blacks ops and MW2 btw). While gaming, I will occasionally get a BSOD, and when I use WhoCrashed, it said that all of my BSOD's had something to do with ntoskrnl.exe. The other embedded problem I have is that when I try to compress my minidump files, it says "access is denied". I am an administrator and have even tried the "take ownership" method, however, it keeps saying "access is denied". So I hope you will excuse this uploaded uncompressed minidump folder
. I will post my files in the next post.
📎 AI Summary:
The WindowsForum thread discusses a user experiencing frequent BSODs related to ntoskrnl.exe, with the main concern being the inability to compress or upload minidump files due to permission issues. Several participants suggest practical solutions such as copying files to the desktop before zipping and mention that Windows allows uploading .dmp files directly. The user successfully managed to compress the files after booting into safe mode, aiming to seek help in diagnosing the underlying system problems.
The WindowsForum thread discusses a user experiencing frequent BSODs related to ntoskrnl.exe, with the main concern being the inability to compress or upload minidump files due to permission issues. Several participants suggest practical solutions such as copying files to the desktop before zipping and mention that Windows allows uploading .dmp files directly. The user successfully managed to compress the files after booting into safe mode, aiming to seek help in diagnosing the underlying system problems.
Solution
I'll help you out in the simplest manner and most efficient here.
Replace the memory entirely with new matching set. (Just be sure to remove B's first, but that isn't the culprit, for sure anyhow.)
Good luck with the new hardware when it arrives. (Even though you won't need luck.
)
You're welcome.
Replace the memory entirely with new matching set. (Just be sure to remove B's first, but that isn't the culprit, for sure anyhow.)
Good luck with the new hardware when it arrives. (Even though you won't need luck.
You're welcome.
ok, now the computer isn't even acknowledging that I have permission of the minidump files. It says not file permission when trying to upload them. What should I do? Idk if this will help any, but this is what WhoCrashed says about my BSOD's:
On Fri 11/26/2010 9:00:44 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EE92B0, 0xFFFFF8800950EA30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\112610-18969-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Fri 11/26/2010 8:28:47 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E9B2B0, 0xFFFFF88008A64A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\112610-20092-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 11/25/2010 3:56:38 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E932B0, 0xFFFFF88005C6D930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\112510-20014-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 9/1/2010 12:01:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x34 (0x50830, 0xFFFFF8800317E2A8, 0xFFFFF8800317DB10, 0xFFFFF80002CCF950)
Error: CACHE_MANAGER
Dump file: C:\Windows\Minidump\090110-20311-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
Hope you guys can help.
On Fri 11/26/2010 9:00:44 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EE92B0, 0xFFFFF8800950EA30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\112610-18969-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Fri 11/26/2010 8:28:47 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E9B2B0, 0xFFFFF88008A64A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\112610-20092-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Thu 11/25/2010 3:56:38 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E932B0, 0xFFFFF88005C6D930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\112510-20014-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 9/1/2010 12:01:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x34 (0x50830, 0xFFFFF8800317E2A8, 0xFFFFF8800317DB10, 0xFFFFF80002CCF950)
Error: CACHE_MANAGER
Dump file: C:\Windows\Minidump\090110-20311-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
Hope you guys can help.
Oh, and these were the most recent ones:
On Sun 12/12/2010 2:00:17 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4A (0x74E92DD9, 0x2, 0x0, 0xFFFFF88008AA0CA0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Dump file: C:\Windows\Minidump\121210-17612-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 12/11/2010 11:40:11 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031592E1, 0xFFFFF88006D58BA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\121110-16068-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 12/11/2010 10:11:49 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E9A2B0, 0xFFFFF88003A11930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\121110-17035-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 12/12/2010 2:00:17 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4A (0x74E92DD9, 0x2, 0x0, 0xFFFFF88008AA0CA0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Dump file: C:\Windows\Minidump\121210-17612-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 12/11/2010 11:40:11 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031592E1, 0xFFFFF88006D58BA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\121110-16068-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 12/11/2010 10:11:49 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E9A2B0, 0xFFFFF88003A11930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\121110-17035-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
spaph
New Member
- Joined
- Dec 12, 2010
- Messages
- 30
You go to C:/Windows/Minidump, copy all those files, make a folder on your Desktop, paste them there, then zip that folder. Trying to do anything besides moving/copying/pasting/deleting files in a system folder is a giant pain in the bum on Vista or W7, which is why you move them to a less restricted area (such as your Desktop) before trying to do anything to them.
I know the steps. The problem is that when I try and zip it, using windows default zipper, winrar, and 7z, it always says "access is denied". Is it possible for you guys to tell what's going wrong by looking at the WhoCrashed reports?
Elmer
Extraordinary Member
- Joined
- Mar 5, 2010
- Messages
- 3,862
I'm no expert, I don't pretend to be either but I'm trying to slowly learn (old dog, new tricks etc.). One of the resident experts will be along at some point to help you out but until then, a little light reading for you!
Your most common error Link Removed. The others, Link Removed and Link Removed.
As to why you can't copy/paste/zip your minidump files is beyond me, as it's something I've never experienced. Where do you get stopped? At the copy/paste stage or after that?
I've just noticed that you can upload .dmp files here without zipping them. It may mean you have to attach them individually........
Your most common error Link Removed. The others, Link Removed and Link Removed.
As to why you can't copy/paste/zip your minidump files is beyond me, as it's something I've never experienced. Where do you get stopped? At the copy/paste stage or after that?
I've just noticed that you can upload .dmp files here without zipping them. It may mean you have to attach them individually........
Last edited:
lol WhoCrashed...haha. Might as well be BlueScreenView.
As you've been shown to do many times (thanks Elmer), copy the files to another folder anywhere on the pc, zip them, then attach the zip. If you follow well it will go well.
If not...then you'll be resorting to WC.
As you've been shown to do many times (thanks Elmer), copy the files to another folder anywhere on the pc, zip them, then attach the zip. If you follow well it will go well.
If not...then you'll be resorting to WC.
Uninstall Daemon Tools. Then use this installer/uninstaller to remove sptd.sys, being CAREFUL TO CLICK ON UNINSTALL WHILE USING:
Link Removed
Reboot and install PowerISO to replace it:
PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive
---------------
Uninstall EVGA Precision or MSI Afterburner or whatever other overclocking utility you have installed.
----------
Follow my signature.
Link Removed
Reboot and install PowerISO to replace it:
PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive
---------------
Uninstall EVGA Precision or MSI Afterburner or whatever other overclocking utility you have installed.
----------
Follow my signature.
so should uninstalling both of those fix my bsod's?
That's a question you should ask your pc when you are done following my entire post, including the part about following my signature.
Similar threads
- Solved
- Replies
- 8
- Views
- 3K