Solved Multiple random BSOD

X

xaverious

New Member
Messages
3
Hello and thanks in advance:

Ever since I purchased this PC with Windows 8 installed(haven´t updated to 8.1) I´ve been getting multiple BSODs at random times, and the error messages seem to be different. I am attaching the file generated by SF diagnostic tool. Please help, also ve very specific as I am not used to troubleshooting PCs.

Thanks
 

My Computer

System One

  • OS
    Windows 8

Only 114 WindowsUpdates installed. Most systems have 160 or more. Please visit Windows Updateand get ALL available updates (it may take several trips to get them all).


Out of 10 memory dumps there were 6 different BSOD error codes. The differing error codesare usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate theproblem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. Ifuncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics fromInitial Hardware Diagnostics or Hardware Diagnostics ).
(Analyse based on canned speech of John Carrona)
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Code: 
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]BugCheck 1A, {41792, fffff680003b9c80, 8000000000000000, 0}[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Probably caused by : memory_corruption ( ONE_BIT )[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Followup: MachineOwner
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]BugCheck 3B, {c0000005, fffff803910b16b6, fffff8801e483ca0, 0}[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Probably caused by : ntkrnlmp.exe ( nt!ObCloseHandleTableEntry+56 )[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Followup: MachineOwner
---------
*************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]BugCheck 24, {b50019060b, fffff8801be29528, fffff8801be28d60, fffff88001af16b4}[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Probably caused by : Ntfs.sys ( Ntfs!NtfsUninitializeNtfsMcb+a4 )[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Followup: MachineOwner
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]BugCheck 50, {fffff8a080066050, 0, fffff88001bc8d6b, 2}[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenExistingPrefixFcb+6b )[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Followup: MachineOwner
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]BugCheck 109, {a3a039d8a3e547aa, b3b7465ef663e2de, fffff88001d17f88, 0}[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Probably caused by : ndis.sys ( ndis!WPP_ea986f46a233dbc01ee20ca12b754d7a_Traceguids+10 )[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Followup: MachineOwner
---------
-*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]BugCheck 3B, {c0000005, fffff800e3ab697e, fffff8801818dda0, 0}[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+23357 )[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Followup: MachineOwner
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]BugCheck 50, {fffffaa00fd74920, 1, fffff8023fd17dfe, 2}[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDecrementCombinedPte+1e )[/FONT][/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=3][COLOR=black][FONT=Arial][COLOR=#3e3e3e][FONT=Verdana]Followup: MachineOwner
---------
-----[/FONT][/COLOR][/FONT][/COLOR][/SIZE]

4 Dumpfiles mentioned memory corruption, so I advice you to check your memory with Memtest 86+.

2 Dumpfiles mentioned NFTS.sys and in your WER there are a few mentions of:
Firma del problema:
P1: iastordatamgrsvc.exe
Click to expand...


So this could point to a faulty Harddisk. Check your harddisk also..

You can get ahead start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus
Thanks alot for the reply, I´ll begin with the windows updates and the hardware tests. I didn´t mention my system specs before, here they are in case it helps:

Windows 8 Pro 64 bits(No 8.1 update yet)
Motherboard: Gigabyte Z87M-D3H
Proc: Intel 4770 (No O.C.)
Graphics: Intel HD 4600 (No Graphics card yet)
SSD: Kingston sv300
RAM:ADATA 8GB DDR3

I´ll post results later.

Thanks
 

My Computer

System One

  • OS
    Windows 8
Solved!

Turns out it was the SSD firmware causing the BSODs

I updated to the latest frimware and my system is now stable. If anyone has similar problems with BSODs and has a Kingston sv300 SSD, I would recommend updating the firmware.

Thanks alot Lifetec to pointing out that the dumps indicated a problem with my harddrive!
 

My Computer

System One

  • OS
    Windows 8
You must log in or register to reply here.
Back
Top