BSOD or better blacksod

[Solferin]

Hey guys, me again but just on different section of the forums. Ok I got blacksod on win 7 a few days ago while playing WoW, WoW stopped, distorted sound comming from the headphones then rig restarted. Thought it was the mbo or something overheated, but i checked the temps and all and everything was ok. So i decided to install win 8 since well i tried that. Installing went great, put all of the drivers, went awesome, nothing happened. I then went to install battle.net that too went ok but as soon as the battlenet started checking wow file that`s on another partition i got blackscreened again, rig restarted, i went on installing wow from scratch, uninstalled battlenet, reinstalled battlenet, started installing wow, downloaded 10 gbs and again blacksreen.

I checked both times with bluescreenviewer and it only says ntoskrnl.exe+5b5d2d. The win 7 blackscreen also said it was ntoskrnl.exe but with another +, think it was 7something, cant remember now. On win 8 there wasnt any sound, rig just restarted. its 0x124 error. I read somewhere here it could be OC related. I did OC my cpu over ASRock utility that offers me the OC mode from 4ghz to 4.3ghz when the logo appears, the logo before win starts to load where you can still enter the BIOS. But i changed it back with load default bios settings. Could it be related to that? i also flashed bios a while back to version 1.30, it had 1.20 before, could it be the bios version? Should i return to 1.20? And finally could it just be my mbo is overheating somehow no matter the fact that room temp is around 25 with air conditioning blowing all the time and is set to 19 C, and my case is fully open?

Any and all suggestion is welcomed and appreciated.

p.s. i removed the battery from the mbo to reset the BIOS manually this time and will leave the rig to work all night to see if this happens again. Tho right now im a bit puzzled why is this happening. Win 7 worked for 4 days before that bsod that made me put win 8.

p.p.s and sorry if i posted this on the wrong part of the forum.

Cheers

 

[ESPclipse]

While it would help to have a complete minidump report, ntoskrnl-sourced crashes are caused by unhandled exceptions at the kernel-level. Probably caused by a bad driver somewhere. Remove the overclock for now and run:

sfc /scannow

to check for missing/corrupt system files. Hopefully nothing wrong there. Show more of the crash dump, if you can, and be very vigilant in updating system drivers. I use Driver Booster or Slimdrivers to update my drivers from one unified location, if you do not do that already. Some say that BlackSOD is usually caused by display drivers, but don't quote me on that Again, show us more of the crash dump. The software WhoCrashed may even diagnose the issue for you, if you wish to try that, too.

 

[Solferin]

Mhm i already ccleaned the win after i uninstalled amd overdrive (was watching cpu temps with it since i have conflicting reports with specy or hwmonitor or core temp, they all say my cpu runs on 35 C idle, but my bios says my cpu is on 40 to 45 C idle, dont know who to trust) and sapphire trix. So i lost the dmp file, will have to wait for another bsod.

Hmm now when i think about it, there was a bsod before installing 15.7 drivers, while i was updating win. Tho it didnt happen for a day and a half untill tonight so i forgot about that one. 15.7 amd gpu drivers*. Im writing this on my phone so i cant edit this properly sorry for that.

If i get a bsod over night ill post more details.

Win 7 worked for about 5 days before that funny soundy bsod. Playing on ultra all 5 days, tho they are on ssd, win 8 are on hdd.

 

[Solferin]

P.s. Will install whocrashed and check sfc in the morning, im reinstaling wow to see if it willl bsod again. Tho whocrashed needs a bit more bsods to figure out whats going on

 

[ESPclipse]

I don't know if you went through all the trouble when you updated CCC to 15.7, but it's often recommended that AMD display driver users uninstall CCC, boot to safe, then run DDU to thoroughly uninstall display drivers. Then boot to normal, stop Windows from installing display driver for you, and then run the CCC installer. Just for future reference

 

[Solferin]

Heres the dump from blue screen viewer, hmmm i bolded the 2 parts, can you confirm its the gpu drivers?

Spoiler

ntoskrnl.exe fffff801`1020a000 fffff801`1099e000 0x00794000 0x550f41a6 23.3.2015. 0:26:46
hal.dll fffff801`1099e000 ffff801`10a0e000 0x00070000 0x538bade8 2.6.2014. 0:49:12
kdcom.dll fffff801`0f2b6000 fffff801`0f2bf000 0x00009000 0x5215f8bb 22.8.2013. 13:40:43
mcupdate.dll fffff800`e2276000 fffff800`e2291000 0x0001b000 0x5216068e 22.8.2013. 14:39:42
werkernel.sys fffff800`e2291000 fffff800`e229f000 0x0000e000 0x5215f8a8 22.8.2013. 13:40:24
CLFS.SYS fffff800`e229f000 fffff800`e2301000 0x00062000 0x54f656f9 4.3.2015. 2:51:05
tm.sys fffff800`e2301000 fffff800`e2323000 0x00022000 0x5215f875 22.8.2013. 13:39:33
PSHED.dll fffff800`e2323000 fffff800`e2338000 0x00015000 0x52346b3f 14.9.2013. 15:57:19 Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.3.9600.16384 (winblue_rtm.130821-1623) Microsoft Corporation C:\Windows\system32\PSHED.dll
BOOTVID.dll fffff800`e2338000 fffff800`e2342000 0x0000a000 0x5215f8aa 22.8.2013. 13:40:26 Microsoft® Windows® Operating System VGA Boot Driver 6.3.9600.16384 (winblue_rtm.130821-1623) Microsoft Corporation C:\Windows\system32\BOOTVID.dll
CI.dll fffff800`e2342000 fffff800`e23ca000 0x00088000 0x548276b0 6.12.2014. 5:23:28
msrpc.sys fffff800`e2200000 fffff800`e225d000 0x0005d000 0x5215f86a 22.8.2013. 13:39:22
Wdf01000.sys fffff800`e2499000 fffff800`e2568000 0x000cf000 0x5215f850 22.8.2013. 13:38:56
WDFLDR.SYS fffff800`e2568000 fffff800`e2579000 0x00011000 0x5215f857 22.8.2013. 13:39:03
acpiex.sys fffff800`e2579000 fffff800`e2591000 0x00018000 0x5215f80b 22.8.2013. 13:37:47
WppRecorder.sys fffff800`e2591000 fffff800`e259c000 0x0000b000 0x5215f87c 22.8.2013. 13:39:40
ACPI.sys fffff800`e2400000 fffff800`e2488000 0x00088000 0x54335e2e 7.10.2014. 5:29:50
WMILIB.SYS fffff800`e2488000 fffff800`e2492000 0x0000a000 0x5215f8a7 22.8.2013. 13:40:23
cng.sys fffff800`e2619000 fffff800`e26a4000 0x0008b000 0x55187b0d 30.3.2015. 0:22:05
msisadrv.sys fffff800`e26b2000 fffff800`e26bc000 0x0000a000 0x5215f857 22.8.2013. 13:39:03
pci.sys fffff800`e26bc000 fffff800`e2704000 0x00048000 0x53d0f1d4 24.7.2014. 13:45:24
vdrvroot.sys fffff800`e2704000 fffff800`e2711000 0x0000d000 0x5215f849 22.8.2013. 13:38:49
pdc.sys fffff800`e2711000 fffff800`e272d000 0x0001c000 0x543df950 15.10.2014. 6:34:24
partmgr.sys fffff800`e272d000 fffff800`e2745000 0x00018000 0x5434e912 8.10.2014. 9:34:42
spaceport.sys fffff800`e2745000 fffff800`e27ae000 0x00069000 0x54505527 29.10.2014. 4:47:03
volmgr.sys fffff800`e27ae000 fffff800`e27c3000 0x00015000 0x5215f889 22.8.2013. 13:39:53
volmgrx.sys fffff800`e259c000 fffff800`e25fb000 0x0005f000 0x5215f8a7 22.8.2013. 13:40:23
pciide.sys fffff800`e27c3000 fffff800`e27cb000 0x00008000 0x5215f893 22.8.2013. 13:40:03
PCIIDEX.SYS fffff800`e27cb000 fffff800`e27da000 0x0000f000 0x5215f87d 22.8.2013. 13:39:41
mountmgr.sys fffff800`e27da000 fffff800`e27f5000 0x0001b000 0x54333f58 7.10.2014. 3:18:16
atapi.sys fffff800`e27f5000 fffff800`e27ff000 0x0000a000 0x5215f8b7 22.8.2013. 13:40:39
ataport.SYS fffff800`e23ca000 fffff800`e23ff000 0x00035000 0x5215f87a 22.8.2013. 13:39:38
storahci.sys fffff800`e2841000 fffff800`e285e000 0x0001d000 0x5215f8b7 22.8.2013. 13:40:39
storport.sys fffff800`e285e000 fffff800`e28bc000 0x0005e000 0x5423822b 25.9.2014. 4:47:07
EhStorClass.sys fffff800`e28bc000 fffff800`e28d6000 0x0001a000 0x5215f827 22.8.2013. 13:38:15
fltmgr.sys fffff800`e28d6000 fffff800`e2932000 0x0005c000 0x53fbf00c 26.8.2014. 4:25:16
fileinfo.sys fffff800`e2932000 fffff800`e2948000 0x00016000 0x53089456 22.2.2014. 14:13:10
Wof.sys fffff800`e2948000 fffff800`e2973000 0x0002b000 0x53216bf1 13.3.2014. 10:27:29
WdFilter.sys fffff800`e2973000 fffff800`e29b6000 0x00043000 0x54cb5b0a 30.1.2015. 12:20:58
Ntfs.sys fffff800`e2a5a000 fffff800`e2c54000 0x001fa000 0x54387b6b 11.10.2014. 2:35:55
ksecdd.sys fffff800`e2c54000 fffff800`e2c70000 0x0001c000 0x54505548 29.10.2014. 4:47:36
pcw.sys fffff800`e2c70000 fffff800`e2c80000 0x00010000 0x5215cfea 22.8.2013. 10:46:34
Fs_Rec.sys fffff800`e2c80000 fffff800`e2c8b000 0x0000b000 0x5215cfe9 22.8.2013. 10:46:33
ndis.sys fffff800`e2c8b000 fffff800`e2da2000 0x00117000 0x54d01043 3.2.2015. 2:03:15
NETIO.SYS fffff800`e2e96000 fffff800`e2f0e000 0x00078000 0x546029c5 10.11.2014. 4:58:13
ksecpkg.sys fffff800`e2f0e000 fffff800`e2f3f000 0x00031000 0x558e14bf 27.6.2015. 5:13:03
tcpip.sys fffff800`e3088000 fffff800`e32f2000 0x0026a000 0x5579e059 11.6.2015. 21:24:09
fwpkclnt.sys fffff800`e32f2000 fffff800`e335e000 0x0006c000 0x5579e00a 11.6.2015. 21:22:50
wfplwfs.sys fffff800`e335e000 fffff800`e3383000 0x00025000 0x54602998 10.11.2014. 4:57:28
fvevol.sys fffff800`e2f3f000 fffff800`e2fd4000 0x00095000 0x534325db 8.4.2014. 0:25:31
volsnap.sys fffff800`e3383000 fffff800`e33d2000 0x0004f000 0x53a21598 19.6.2014. 0:41:28
rdyboost.sys fffff800`e3000000 fffff800`e3046000 0x00046000 0x53089474 22.2.2014. 14:13:40
mup.sys fffff800`e3046000 fffff800`e305d000 0x00017000 0x5215f8ac 22.8.2013. 13:40:28
intelpep.sys fffff800`e305d000 fffff800`e306c000 0x0000f000 0x543e1458 15.10.2014. 8:29:44
disk.sys fffff800`e33d2000 fffff800`e33ee000 0x0001c000 0x5215f883 22.8.2013. 13:39:47
CLASSPNP.SYS fffff800`e2e00000 fffff800`e2e56000 0x00056000 0x5434c9ff 8.10.2014. 7:22:07
crashdmp.sys fffff800`e306c000 fffff800`e3081000 0x00015000 0x5215f893 22.8.2013. 13:40:03
dump_storport.sys fffff800`e33ee000 fffff800`e33fa000 0x0000c000 0x5215f8a2 22.8.2013. 13:40:18
dump_storahci.sys fffff800`e2e56000 fffff800`e2e73000 0x0001d000 0x5215f8b7 22.8.2013. 13:40:39
dump_dumpfve.sys fffff800`e2e73000 ffffd801`e2e89000 0xffffe00100016000 0x530894b8 22.2.2014. 14:14:48

Spoiler

072315-21718-01.dmp
Bug check code: 0x00000124
parameter 1: 00000000`00000000
para 2: ffffe001`89e03038
para 3: 00000000`00000000
para 4: 00000000`00000000
caused by driver: ntoskrnl.exe
caused by adress: ntoskrnl.exe+5b5d2d
crash adress: ntoskrnl.exe+5b5d2d

 

[Solferin]

ran the sfc, did not found anything

 

[Solferin]

p.s. did not go through the whole process of installing and uninstalling drivers since i had clean installed win 8 on the partition that hasnt been formated yet. i left around 300 gb for just in case i need a new windows sometime in the future so i can just copy paste what i need from ssd. The win were clean install, no drivers nothing, i updated the windows first, then i installed 15.7 drivers for the gpu i downloaded just than, the rest win already had.

 

[Solferin]

oh another q, i got a loose plastic thingy that holds my gpu onto the mbo slot, when i put gpu in the slot i hear that shes in but the holder on the mbo slot is "not doing anything", its so loose it doesnt hold the gpu, gpu is fastened with 1 screw on one end and on the far end it fits almost perfectly on a "shelf" that should hold more than one dvd player, could it be that the gpu isnt fully in the slot or maybe under load it "falls out a bit" cause of the temp and faulty holder?

 

[Solferin]

hmm i can always try ddu, tho ddu does leave a few registry keys undeleted tho i had a stupid idea now, was it maybe because i controlled the gpu with sapphire trix app (for oc, didnt oc just set fans to 100%) but i didnt end the ccc and mom.exe in task and i didnt approve the oc mode in ccc in the first place?

 

[ESPclipse]

Well, you should do your best to keep the hardware in place and snug if you can help it. Odds are that if the card did not fit in to the PCI-e slot, then you would not have passed POST. If you had not installed display drivers prior to updating to 15.7, then you will not need DDU right now. In that first or second post I was only guessing at what the cause may have been but needed to see the minidump report.

Anywho, on to your case
Lots of kernel-y stuff crashed, which is to be expected I guess. That minidump is quite messy, so see if whocrashed can diagnose the crash before reading on. One possible source - bootvid.dll - is a part of a display driver. I do suggest thoroughly reinstalling display drivers (as in the DDU way) if you can, just to be safe. Make sure you are getting the right CCC installer from AMD, too. If that does nothing, then try following this method for manually replacing the bootvid.dll file.
To be honest, I do not really know what pshed.dll is, but I have seen BSODs from this file associated with a corrupt system registry, malware, and bad memory. You can test the memory with memtest86, and Linux live isos have memtest built into them too. I would run a Malwarebytes scan to check for malware that may be messing with system files. Try a simple registry repair as well to repair that registry. If none of these seem to fix anything, there is a guide for replacing pshed.dll.

 

[Solferin]

Ill try one thing at a time and see what does the trick. Before posting this i uninstalled amd overdrive and trixx and rebooted to bios, loaded default bios sttings. Enabled ocing in ccc and so far the thing works, played wow for about an hour, downoaded some stuff, watching youtube right now. Will play some more wow on ultra to see what happens when i stress the gpu s bit. But so far so good. If bsod happens ill first try ddu and driver reinstallement then the rest of the stuff

 

[Solferin]

Oh and thank you for the help

 

[Paul NZ]

If you can still get into windows upload the dmp files somewhere. Then post the link

A 0x124 stop error is / or can be cpu related. It can mean its overclocked, overheating, or faulty. Sometimes a BIOS update fixes this

 

[Solferin]

ufff im kinda of a noob for uploading stuff and semi noobish when it comes to other stuff. but before i get into uploading and all, im running prime95 right now and monitoring my cores via hw monitor and cpu seems fine. it acts normal, it underclock itself as soon as temp reaches 40 C as shown by hw monitor but that could very well be 50 C since temps shown by specy, hw monitor and core temp differs from temp shown by bios, around 10 C difference.

its stress testing for 15 min now, its still running in the background, all cores are at 100%, 4 ghz till temp reaches 40 C then back to 1.4 ghz as soon as it passes 40 C then back up, so my guess is its not overheating cause it would overheat already, right? can i be sure its not faulty since its running prime for 15 min with no bsods errors or some such?

 

[Solferin]

tho my rig is making funny sounds right now, cant detect if its vents or something, it sounds like some sort of writing sound or reading sound, high pitch in steady intervals every 5 secs for 3 secs, like when you put a cd in the cd rom and it starts to turn could be cooler hmmm

i think its cpu, everytime frequency jumps at 4ghz for all cores it starts to "squeal" and when the "squealing" stops the freq goes down to 1.4 ghz. Guessing not a good sign, but its funny

 

[Solferin]

ill try disabling cool and quiet now and that other thingy thats stopping cpu from reaching high temps in bios to see if itll bsod

 

[ESPclipse]

ill try disabling cool and quiet now and that other thingy thats stopping cpu from reaching high temps in bios to see if itll bsod

If you overclock an AMD CPU, disable C'n'C, C6-State modifiers, and Turbo Core

 

[Solferin]

Ok run prime for 6h over night, core 7 had a harware error stopped at 2h mark, run prime again this morning, core 6 got hardware error, test ended after almost 7h. Rest of the tests are still running, 12h so far. Hmm so is that kinda ok or?

 

[ESPclipse]

Ok run prime for 6h over night, core 7 had a harware error stopped at 2h mark, run prime again this morning, core 6 got hardware error, test ended after almost 7h. Rest of the tests are still running, 12h so far. Hmm so is that kinda ok or?

Overclocking? If so, then you need to reduce/remove the overclock. As you may suspect, it's not great if cores fail. If not overclocking, then the CPU is technically defective

 

[Solferin]

Crap, not overclocked. So its cpu causing bsods than? Eh while it works it works, dont have money or warranty, prime says Fatal error rounding was 0.5, expected less than 0.4, then hardware failure detected consult stress.txt, 28 tests completed etc etc.

 

[ESPclipse]

Crap, not overclocked. So its cpu causing bsods than? Eh while it works it works, dont have money or warranty, prime says Fatal error rounding was 0.5, expected less than 0.4, then hardware failure detected consult stress.txt, 28 tests completed etc etc.

Well, okay I jumped to conclusions because I thought you were surely overclocking. Cores can start to fail if they overheat. Cores can also fail if they do not receive the voltage that they require. If you can, load to optimized defaults for now in the BIOS and run an OCCT stress test instead. OCCT is nice because it monitors temperate, clock speed, and voltage, as well as great error-detection. It will stop testing if there is a problem. If you cannot pass this stress test at stock clock speed, with temps <80ºC, then I would believe the CPU to be defective. Just my thoughts...

 

[Solferin]

Started occt so far so good, really nice since it uses my built in hw monitor, so i just let it run for an hour (default setting)? Oh can i test gpu with it, i see theres an option gpu:3D?

 

[Solferin]

Ah it says infinite crap, so how long should i run it?

 

[Solferin]

Oh havent noticed it before but hmm or i didnt mind it since its so small a number but occt says original hz of cpu is 4ghz but when on full load it works on 4007,7 or in occt info its 0.2% oc. I noticed the number waaay back when i first oced the cpu over mbo and then changed it back to default but i thought it a missreading. But i highly doubt that 7.7 hz can make a rig unstable.