• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Getting the infamous BSOD :(

z1ggy

z1ggy

Lifer
Blue screen of death. Been happening now for a month or so..I'd say this was the 6th time or so. However, this last time I got back to after my log in screen and it says "windows explorer stopped working" then BSOD'ed again. What is the likely root of the problem and what can I do to fix it?

My sig is my hardware specs.
 
z1ggy said:
Blue screen of death. Been happening now for a month or so..I'd say this was the 6th time or so. However, this last time I got back to after my log in screen and it says "windows explorer stopped working" then BSOD'ed again. What is the likely root of the problem and what can I do to fix it?

My sig is my hardware specs.
Click to expand...

Your sig isn't being displayed, so it must be turned off.

If you haven't already, install software like Whocrashed or Nirsoft's Bluescreenview (it is safe even if your antivirus flags it as infected - Nirsoft stuff sometimes flags because of the toolkit they use to build some of their software). Also, go to the start menu and in the run box type "View Advanced System Settings" without the quotes and hit enter. Under the Startup and Recovery section, hit the Settings button. Make sure that Windows is set to save kernel memory dumps.

If these options are already set, Whocrashed or Bluescreenview will allow you to load the dump files to see what is crashing.

It also wouldn't hurt to download and burn a bootable MEMTEST86+ ISO to test your memory modules one at a time ("Windows Explorer stopped responding" always immediately makes me suspect file system corruption, which can begin with a bad memory module more times than not).

If you don't have any monitoring software installed (such as Speedfan or HWMonitor), do so as this will allow you to keep an eye on your CPU and GPU temps to see if anything is out of wack there.
 
Last edited:
Steltek said:
Your sig isn't being displayed, so it must be turned off.

If you haven't already, install software like Whocrashed or Nirsoft's Bluescreenview (it is safe even if your antivirus flags it as infected - Nirsoft stuff sometimes flags because of the toolkit they use to build some of their software). Also, go to the start menu and in the run box type "View Advanced System Settings" without the quotes and hit enter. Under the Startup and Recovery section, hit the Settings button. Make sure that Windows is set to save kernel memory dumps.

If these options are already set, Whocrashed or Bluescreenview will allow you to load the dump files to see what is crashing.

It also wouldn't hurt to download and burn a bootable MEMTEST86+ ISO to test your memory modules one at a time ("Windows Explorer stopped responding" always immediately makes me suspect file system corruption, which can begin with a bad memory module more times than not).

If you don't have any monitoring software installed (such as Speedfan or HWMonitor), do so as this will allow you to keep an eye on your CPU and GPU temps to see if anything is out of wack there.
Click to expand...

ASRock Z68 Pro3, i3-2100, 8GB G.Skill 1333, ZOTAC GTX460, Antec 550w, Hitachi 1.5TB HDD, 1TB Fantom Ext. HD, ASUS DVD/CD, HAF 912, Win 7 x64 Ultimate

^ Hardware specs.

Okay I will download those toolkits and run the command line stuff. If it is a memory issue, that's not too terrible. I can fix that for cheap. I'd hate to have to replace a motherboard or worse.
 
Here is th ebug report from Whocrashed:

On Wed 11/13/2013 11:36:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111313-33197-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80045E4B70, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


How can i fix this issue? It doesn't really give a solution.
 
When did the crashes start, and can you think of any drivers you have installed/upgraded around that time period?

I know the description says this isn't caused by faulty RAM, but I wouldn't rule that out, unless you are able to find the driver causing the problem.
 
Another crash last night. Comp wasn't even doing anything just sitting there... :-/

On Fri 11/15/2013 11:43:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111613-43945-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x5E9F000, 0xFFFFF8A005EA0010)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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.
 
z1ggy said:
Not that I know of, but I can check my comp to see the dates of all software install.
Click to expand...

Not a bad idea. While you are in there, look at Windows updates and see if any match the date the blue screens started?

Is your external hard drive plugged in 24/7? Does it power down after so many minutes? And is there software running in the background for that hard drive (doing backups, etc)?
 
ketchup79 said:
Not a bad idea. While you are in there, look at Windows updates and see if any match the date the blue screens started?

Is your external hard drive plugged in 24/7? Does it power down after so many minutes? And is there software running in the background for that hard drive (doing backups, etc)?
Click to expand...
+1
 
ketchup79 said:
Not a bad idea. While you are in there, look at Windows updates and see if any match the date the blue screens started?

Is your external hard drive plugged in 24/7? Does it power down after so many minutes? And is there software running in the background for that hard drive (doing backups, etc)?
Click to expand...

Yes to the HD being in 24/7. No it's pretty much always on. I don't run any auto back up programs with it, I manually back up my internal to it every so often.

I've been so busy lately. I may have time today to check my software install dates to see if I did anything lately that would cause this.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top