BSOD for years, getting tired of this!

Toggle sidebar Toggle sidebar
D

djisou

Honorable
Sep 5, 2013
15
0
10,510
I would say that my computer get BSOD on average 4 times a week. It often occurs when i'm playing some kind of multimedia, like games, videos or music. Programs that most often results in the BSODs are Spotify, Battlefield 3 and flash applications(like youtube), while other similar programs like foobar2000, Xbmc and Heroes of Newerth almost never give me BSODs. I run Windows 7 service pack 1, and have tried formatting my computer with different windows version, but the problem is the same.

I have tried memtest86+ many times, running it for over 6 hours straight the last time without any errors.

I have updated all of my drivers, and tried different versions for some of them (sound drivers, ethernet drivers and graphic drivers), but it doesn't help.

I have changed AHCI-settings for my SSD driver and updated its firmware.

Here is a link to some of my latest memory dump-files:
#1
#2
#3
#4
#5

Here is a link to cpu-z screen

If you need any more information i would gladly provide it. I have many more dumps if needed. :)

Please help me with my BSOD problem!

Thanks in advance
Djisou
 
Solution
O
Sort by date Sort by votes
D

djisou

Honorable
Sep 5, 2013
15
0
10,510
From what i can remember I have had these BSODs since i built my computer, 2 years ago, so I'm afraid i cant pin point any hardware that might be causing them.
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510
I don't really use any active anti-virus, as I don't like having programs running constantly in the background, but i scan my computer from time to time.
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510
Yes, and I have tried multiple versions of windows, none of which made any difference.

Also I forgot to mention in my OP, that I have run cmd->runsfc /scannow, chkdsk and some 3rd party diagnostic/repair applications that didn't help either. Basically i have googled the shit out of BSOD problems and my different error codes, and tried loads of different "quick fixes" and settings that may solve the problem. But it hasn't helped. Asking for help in forums was my absolute last option, but after hours of trial and error, here I am.

What i'm really looking for is if someone can find any specifics in my errors reports, that might point to where the problem lies, i.e. drivers/hardware/applications?
 
Upvote 0 Downvote
M

M A W

Distinguished
Jul 6, 2013
110
0
18,710
Have you looked in Event Viewer??? I'm not an expert in reading bugcheck analysis or dump files but I'll see what I can do.

(1)(2)Both logs one and two are caused by ntkrnlmp.exe but with different parameters. Typically this problem is associated with faulty RAM.

(3)The problem in the third log is usually caused by "some IEEE 1394 devices." http://support.microsoft.com/kb/980932

(4)In the fourth log you posted, the report says the that it could not read faulting driver name which pointed to RTKVHD64.sys. That's a Realtek sound driver (64-bit I suppose).

(5)The fifth log says that the problem was likely HIDCLASS.SYS. That has to do with USB devices of the sort.

My two cents is that the root cause is a driver (unlikely since you said you've reinstalled them and even the OS), the motherboard, or RAM. Idk what your setup is, but you can try the process of elimination with RAM by taking out 1 or 2 sticks and seeing if the problems persists. If it does, repeat process with the other RAM (put others back in of course).
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510


Event viewer only reports error that happens after the BSOD like "the last system shutdown was unexpected", there are no messages before the BSOD.

Regarding the different reasons, doesn't it seem highly unlikely that i had errors with problems with three different drivers? It must be the RAM, right? I feel like your idea of removing a stick at a time is good, only that i'm afraid that kind of testing will take a very long time, since my BSODS are so infrequent, so for me to be sure that the problem is solved may take weeks. For now i have tried raising my QPI a few notches.

Since i made the first post I've had no BSODS - until yesterday, when i had two. Both BSODs gave ma an error code i haven't seen before(BAD_POOL_HEADER), but list the source of the problem to ntoskrnl.exe, as before. Here are the dumps: 1 2

Thank you for taking your time to try and help me.
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510
I found the solution.

When removing my memory i noticed a sticker on them defining the timings and voltage the memory should have, I thought to myself that I might as well double check that my settings were the same as on the sticker. They weren't.

All my timings were 1 below recommended value and the voltage was way below the recommended value as well. I hadn't changed these settings myself before and honestly thought that it would be set up automatically by the bios, but now i know better.

With the correct settings my system has been running smooth as never before.
 
Upvote 0 Downvote
O

onichikun

Distinguished
Nov 13, 2009
304
1
18,860
I actually find that quite surprising since you already ran memtest86 for over 6 hours with no issue. If it was just timing and voltage related, memtest really should have picked that up.

Maybe the voltage swing was too much when other parts of the motherboard was loaded too which was causing the issue...
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510


Nice call my friend! :) I really thought my problems were gone, since i had went over a week without blue screen, but today i had another one. Over 11 days since the last one. So apparently my problems aren't solved, so i'd like to reopen this topic and ask everyone for help again.

This is the latest dump file, from today.

And as before, I'm more than happy to provide any other information you might require. Thank you everyone for taking your time.

Edit: Since my last two BSODs were from the same driver, CorsairLINK_ha, I'm currently looking in to that specific driver. Tough I suspect that it sin't that driver that is causing all the problems.

Sincerely
djisou
 
Upvote 0 Downvote
O

onichikun

Distinguished
Nov 13, 2009
304
1
18,860
This is probably being caused by a bad driver, failing device, rootkit or antivirus program.

Basically a POOL in the NT kernel is a set of pages reserved by the kernel to enable drivers and kernel code to allocate large data structures. There are, however, some strict requirements for a POOL_HEADER structure that if they are not met, or a driver does something wacky, or some corrupt data is returned from memory, the kernel will raise a BAD_POOL_HEADER bug check.

I would try:
1) removing any antivirus for awhile, and use microsoft essentials
2) make sure your drivers are up to date for ALL HARDWARE (including your mobo) some motherboards will ship with some components that windows will allocate default drivers to that are not correct! (this can be due to firmware bugs, VID/PID collisions etc.) -- I have had this happen before with a cheaper motherboard
3) You have a rootkit - sometimes a program running in your kernel (like a rootkit virus) can do something stupid.
4) Remove any non-essential hardware (raid controllers, sound cards, etc.)
5) Make sure your mobo bios is up to date
6) Check your device manager for any yellow exclamation marks

It could still be your memory. Can you try running PRIME95 max mem/cpu burn test and see if it causes this error faster?

EDIT: Just saw your edit. I bet you that CorsairLINk driver is retarded and poorly coded. No offense to Corsair, but I really don't trust products like that... Get rid of it.
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510


Yes, for some reason i had respect for corsair as a company, but that has changed since i got this cooling kit, and especially the driver for it. I mean take a look at the interface of this driver and fan controller:
corsair-link1.jpg


It screams BSOD even before you get one! :)

Anyway I updated the driver (and btw, finding the newest version of the program on their website was hard, lol), and hope that this solves my problem. If it doesn't, I'm pretty much fucked, since i need it to control my corsair fans, so that my computer doesn't sound like a vacuum cleaner! :D

I might return, but lets hope not.

Thanks!
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510
No, I'm afraid they are controlled through an USB-port on the motherboard. Stupid, I know. (I'm using SpeedFan for my other fans in my computer, and it can't control my corsair fans)
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510
So i guess I'll update my status.

Reinstalled windows with a different version than before. I'm very hopeful this will work, but my hopes has been crushed so many times before. :) They probably will yet again.

Running prime95 constantly to try and force an error.
 
Upvote 0 Downvote
gamerk316

gamerk316

Glorious
Jul 8, 2008
13,234
131
44,840


Memtest86 runs with no other programs running, so the effects of memory timings and voltages are smaller compared to running the entire OS. I've seen RAM pass days of memtest86, but fails the instant you boot the OS. Memtest is good for finding RAM with physical errors, not so much for RAM that needs a slight voltage boost, or slightly looser then spec value timings.

Anyway, I can't view the dump files at work; can anyone post the STOP codes for reference?
 
Upvote 0 Downvote
O

onichikun

Distinguished
Nov 13, 2009
304
1
18,860


Actually testing your memory in memtest86 vs running an OS will not change the way your memory controller performs. A memory controller is a hardware core that takes command from the rest of the processor fabric. Memtest86 is nice since it emulates different access patterns to find failures in timings. If your memory is running with a stable voltage and proper timings it will work fine in OS if memtest runs fine for a sufficient period of time. When you start loading other components with a bad power supply that cant provide enough power, your voltages will dip and that can cause stability issues.

Basically the memory controller is a controller and a queue that handles re-ordering bank accesses to ensure the highest bank hit rate possible. Memtest 86 runs through patterns that will make sure to test different possible timing issues. It doesn't matter that your kernel isn't time multiplexing processes. Anyways locality of access indicates you will be hiting cache more than memory in typical programs, and memtest86 hits memory a lot harder.
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510


Here are the error codes:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003acdc25, Address of the instruction which caused the bugcheck
Arg3: fffff88004dbaa90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero..

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa8004e7b6c0, the pool entry being checked.
Arg3: fffffa8004e7b6c0, the read back flink freelist value (should be the same as 2).
Arg4: fffefa8004e7b6c0, the read back blink freelist value (should be the same as 2).

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9800d8fad60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88005f7312e, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003e5ac70, Address of the instruction which caused the bugcheck
Arg3: fffff88003fa4790, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: fffff980323a6001
Arg3: 000000000000d283
Arg4: fffff780c0000000

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003bb0617, Address of the instruction which caused the bugcheck
Arg3: fffff88005dae6e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510


I'd like to do that, if the corsair thing wasn't my CPU-cooler. I don't have any alternative cooling solution.

But how can you be sure that these are the source of the problem(s)? There are many other aplplications (NTFS.sys, hon.exe and svchost.exe for example) that are listed as cause for the BSODs in my logs. On top of that i have had the BSOD problem years before i got the corsair product. Can't there be a deeper problem that causes the errors in all of these programs? It just seem unlikely that there is a fault with so many different things at once.
 
Upvote 0 Downvote
O

onichikun

Distinguished
Nov 13, 2009
304
1
18,860


Ah I had assumed that since you were relying on it you had it since you built the computer. I still think this is driver related, but it could be due to failing hardware that is causing the associated driver to do something wacky. A kernel related problem can cause a problem to be reported in a lot of different EXEs/services.

If you cant force the BSOD to happen faster through prime95, 3dmark, and PC mark, then that is a bit confusing. Does this happen when you are using the internet primarily? You mentioned hon.exe, so I guess this has happened when you were playing heroes of newerth online? Have you tried stressing your ethernet driver? I have had issues with bad ethernet drivers (primarily in linux though) causing kernel problems.. What ethernet card/chipset do you have?

If we can get the BSOD to happen by doing something specific, we can identify your problem. We need to be able to force it to happen though.

By any chance do you notice your internet slowing down/becoming unresponsive periodically, forcing you to restart?

 
Upvote 0 Downvote
D

djisou

Honorable
Sep 5, 2013
15
0
10,510


This morning when i started my computer something weird happened. For one the corsair program didn't start at all, windows claiming that it was an invalid win 32 application. And also, when i started prime95 to try and cause a BSOD, it reported errors on multiple cores on test 1. Since i have had no errors at all in prime 95, up until this morning and suddenly there were loads of them , I got suspicious. Especially since i hadn't changed any settings in BIOS or anything. To me it seemed two files had been corrupted over night, which must be a virus.

I downloaded AVG to scan through my computer, and it found 237 different infected files, everyone with the virus Hidrag.A. Among these files were svchost.exe (the "root" file for the virus"), hon.exe, CorsairLink_ha.exe and so on - every files that has been identified as a cause of BSOD was infected. After removing the virus and scanning one extra time to be sure, both programs are working fine again. Could this virus be responsible for the BSODs?

Regarding the ethernet trail: I have a Realtek network adapter, on chipset x58 (model x58a-ud3r). My bsods happens when I use the internet, but to be fair, I don't remember whenever i used my computer for anything that didn't involve the Internet. I play a lot of online games, use a torrent application frequently and stream live videos all the time. I never experience any problems with my adapter or connection. It is very stable. I'll try find some way to stress my ethernet adapter tough, if torrenting wouldnt be sufficient. :)

Thanks for sticking with my through this problem. You are a great resource to me and i appreciate it!
 
Upvote 0 Downvote
O

onichikun

Distinguished
Nov 13, 2009
304
1
18,860


Definitely a virus can lead to BSODs. Rootkits in windows can live as an infected driver, and typically hooks (replaces portions of code) in windows API calls. I would re-install from scratch, and change all your passwords immediately. This is one reason why I suggested you install Microsoft security essentials earlier. Make sure to change your password after you reformat, install windows, update your operating system and install Microsoft security essentials or another Antivirus.

People who program rootkits are good, but they typically don't spend much time debugging their code for obvious reasons, lol.

If you like to download a lot of different programs from the internet, or browse "unsafe" webpages, I would recommend downloading VirtualBox, and installing Windows in that. Whenever you want to try a new EXE or new webpage, use VirtualBox to do it, and leave your host operating system clean.

Keep java always updated, and ActiveX as restricted as possible.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom