For the past few weeks I've been having occasional crashes while playing games or browsing the internet, and when I try to restart I get another blue screen before I can login to my computer. Today I've been getting multiple BSODs and having trouble starting up windows again, and startup repair can't fix whatever is wrong. If you need anymore info, I'll do my best to get it for you. Thanks in advance.
Right, the cause appears to be from Symantec Anti Virus. I also know this because you said it blue screened before you can log in. I had exactly the same issue except I was using Bullguard.
Please remove Symantec AV and all other Symantec products, then install Microsoft Security Essentials and Malwarebytes from these links.
Microsoft Security Essentials - Microsoft Windows
Malwarebytes | Free Anti-Malware & Internet Security Software
Note when installing Malwarebytes make sure you untick the box that starts a free trial of malwarebytes pro because the pro version is a real time scanner which could and most likely will conflict with MSE. The free version is an on demand scanner which should cause no conflicts
You also have fatal hardware bugchecks which can be caused by drivers as I have personally experienced.
Only do the following after you have uninstalled Symantec and the computer still crashes.
Please run some hardware stress tests to determine the faulty component (If it is hardware related which is most likely is)
Prime95 - This stresses the CPU.
Furmark - This stresses the GPU.
Memtest86 - This scans RAM for errors.
It is most likely the GPU because a different bugcheck indicates a display crash.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8006aa28f8, 0, 0} Probably caused by : hardware Followup: MachineOwner
A lot of 0x3B bugchecks are caused by GPUs (Driver or Hardware).Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff880047654ba, fffff8800a290c10, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+1e ) Followup: MachineOwner
Please post back the results.
Thank you for the reply, I've removed any signs of Symantec AV and installed the recommended items. I'll try to replicate the events of previous crashes and see if my pc can hold up. If anything happens, or doesn't happen for that matter, I'll be sure to let you know.
Had another crash no more than 30 minutes after playing a game, and spent roughly 15 minutes trying to get windows to load up again. I'll begin running the stress tests.
Make sure to upload new dump files every time you get one. Upload them in your next reply.
Sorry, uploading a new zip now. The stress tests from before went smoothly and didn't show anything wrong.
Right, windows is pointing to USBPORT.sys which normally means a driver is at fault. We can't identify which one though.
Please enable Driver Verifier by following these instructions.
Driver Verifier - Enable and Disable
Once enabled, it should force a BSOD, upload those dump files.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff88002f1b0f0, 0, 0, fffff8800437944e} Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_InterruptService+56 ) Followup: MachineOwner
Ran that while I was waiting for your reply, actually. If it means anything, it never got past Windows loading screen before crashing, and I had to run it in safe mode to turn off the verifier.
Can you go onto the start menu, type msconfig then go onto the startup tab and disable all programs that aren't necessary.
Then enable Driver Verifier again.
Nothing changed, other than being unable to use the internet until I enabled it again. I still got the error at the Windows loading screen, but it's because the verifier is reporting a driver. It's the same error as before, so it should be in the file I uploaded in the last post, shouldn't it?
Quote