New
#11
BSOD again. This time UNEXPECTED_KERNEL_MODE_TRAP, 0x0000007F. I'm beginning to suspect my processor might be having issues.
Attached dump as per usual.
BSOD again. This time UNEXPECTED_KERNEL_MODE_TRAP, 0x0000007F. I'm beginning to suspect my processor might be having issues.
Attached dump as per usual.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
_______________________________________________________
Code:BugCheck 7F, {8, 80050033, 406f8, fffff800038b9ac7} Probably caused by : memory_corruption Followup: memory_corruption ----------------------------------------------------- BugCheck 3B, {c0000005, fffff96000127814, fffff8800dd8db20, 0} Probably caused by : win32k.sys ( win32k!NtUserGetThreadState+b4 ) Followup: MachineOwner ---------
Did 9 passes on MemTest, no errors. Did FurMark test as instructed by tutorial, no red lines or obvious graphical artifacts, ran test until temps evened out at 75-76C. Only noticable thing was what appeared to be the test attempting to insert white text at the bottom of the screen, about where you'd see subtitles in a movie. They were illegible.
Attached log from burn-in test, just in case it is helpful. Will enable Driver Verifier tonight.
Another bluescreen while I was preparing to start Driver Verification. Posting dump.
The BSOD indicates to Intel USB3 driver.
But it is the latest one as per ECS Web Site > Z87H3-A2X EXTREME (V1.0)Code:*** WARNING: Unable to verify timestamp for iusb3hub.sys *** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff88005849a3b, fffff88005fb5908, fffff88005fb5160} Probably caused by : iusb3hub.sys ( iusb3hub+49a3b ) Followup: MachineOwner ---------
So it may not be the real reason.
Upload the list of all the third party drivers Using NirSoft DriverView :
- Download and execute Driverview
- View > Hide Microsoft Drivers
- Edit > Select all
- File > Save Selected Items
- In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
- Zip the .txt file and upload it.
Also let us know what are the USB devices you have attached to the system.
Enabled driver verifier, immediate BSODs before getting to desktop. Went to Safe Mode to use SF. Attached dumps.
Attached driverview as requested.
Current USB attachments are as follows:
*****
brother DCP-7060D MFC All-in-One Laser Printer
StarTech 35FCREADBK3 USB 2.0 Internal Card Reader (attached to USB header on motherboard)
CM Storm Sentinel Advance 2 Mouse
Microsoft Comfort Curve Keyboard 2000
Kensington 33902 Bluetooth USB Micro Adapter
Logitech 980186-0403 Silver USB Microphone
Last edited by anthonylert; 04 Mar 2014 at 02:05.
You havent done the driverview properly. It shows only one driver, whereas there are a lot.
Have another try.
But some important result came out from the latest crash dump. The MotioninJoy simulate Xbox 360 controller (virtual Xinput device) is causing the BSOD.
It is a very common scenario with the driver version that you have installed. Uninstall it, and install an earlier version of the driver from Playstation 3 controller(Dualshcok 3 or Sixaxis) driver for windows | MotioninJoyCode:BugCheck C2, {9b, 1, 20, fffff88005a393eb} *** WARNING: Unable to verify timestamp for MijXfilt.sys *** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys Probably caused by : MijXfilt.sys ( MijXfilt+1c3eb ) Followup: MachineOwner ---------
Let us know the result.
Added proper Driver View text. Added latest BSOD that occurred prior to rolling back MotionInJoy driver.
It is strange that how frequently the bugcheck codes and probable causes are changing.
It is the display driver this time.
Install the http://www.nvidia.com/object/win8-wi...ql-driver.html only, as a test.Code:BugCheck 1E, {0, 0, 0, 0} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+27e1b3 ) Followup: MachineOwner ---------
- Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
- GeForce Xperience
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).- Now follow Drivers - Clean Left over Files after Uninstalling
- Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
But the frequent changing pattern is not feeling good at all. Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Let us know the results.