BSoD's while playing WoW and forum trawling

Ztruker · 05 Nov 2016

but one of the cores of my cpu failed in the first minuet

Not a good sign. Sounds like you may need to replace the CPU to resolve this.

How are temps and voltages normally? Monitor them using Speedfan, CPUZ or similar.

allan2 · 06 Nov 2016

after having the verifer run for over 30 hours i got a bluescreen, i thought it was ment to tell me on the screen the name of the driver thats causing the problem, but it didnt uploading the dump file

Speedfan also gives this "WARNING: bad Winbond($5CA3,$C1) identify (NCT6793D,W83677HG-I)NCT6793D (ID=$C1) found (using SuperIO) on ISA at $290"

CPU temp hovers around 35C voltages i'm not sure where to get them from speedfan.

One other thing while doing the stress test on my CPU with prime95 my motherboard temperature was at around 89C at idle like now its around 28C

since i got the blue screen while running the verifier i have had 2 additional blue screens with different error codes to the usual machine check exception, they were krenal security check failure and clock watchdog timeout im attaching the log collector for those 2 BSoD's

Ztruker · 07 Nov 2016

I don't see anything useful in any of the 3 dumps.

Any chance the CPU is still under warranty? If yes, maybe you can RMA it?

allan2 · 07 Nov 2016

yes it should be, and what do u mean by "maybe you can RMA it"

Ztruker · 07 Nov 2016

RMA = Return Merchandise Authorization. Basically an OK from the manufacture to return it for replacement.

allan2 · 13 Nov 2016

im unconvinced its the cpu that's causing the bluescreens as i haven't had a machine check exception error since we last spoke, i got a few irql errors which i found that it was being caused by my graphics card and my audio drives being assigned the same irq, this was fixed by moving my graphics card.

tho im looking for some help with my latest bluescreen. it gave me the name of the drive that failed on the bluescreen but i wasn't fast enough to take down the name of it as i thought my problem is solved. from what i did catch of the name its a .sys drive or file that caused the problem

the dump your looking for is today's one

Ztruker · 13 Nov 2016

I'm not able to process the 14393.447 build dumps, symbol file problems. Previous build of 14393.351 was okay:

Code:

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*G:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*G:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff801`8881d000 PsLoadedModuleList = 0xfffff801`88b22060
Debug session time: Sun Nov 13 12:28:00.076 2016 (UTC - 5:00)
System Uptime: 0 days 3:50:24.756
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Looks like Microsoft has not made the symbols for the .447 build available so nothing I can do.

allan2 · 14 Nov 2016

dam thanks anyway there's nothing i can do either it seems as i don't want to delete the wrong system file, i guess i will need to be faster with a pen and bit of paper one other thing can i use the print screen button to capture the image of a BSoD?

thanks for looking tho

Ztruker · 14 Nov 2016

Print screen won't work. You could use your phone or a digital camera.

allan2 · 14 Nov 2016

for the verifier is there a period of time after 1 that i should wait before running it again?

as last night i got a kernel security check failure blue screen. The memory diagnostic didn't throw anything up neither did the system file checker which means its a driver most likely the same driver that caused the 1 i uploaded last night.

there's two things i can do now i can upload it and ask you to look at it when you have access to the symbols (not sure when that will be)

or i can run the verifer again and see if the driver crashes my system and throws the name up.

which would be the best course?