Hello,
Lately I've been experiencing many BSOD's while doing various things. For example, I could be playing a game and my PC will crash. I could be producing a song and the PC will crash. It happens at random- although one known warning sign of my crash coming is Google Chrome crashing and loading the "Aw Snap" page. Are there any solutions for this? Thank you in advance!
Welcome to SevenForums
Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.
Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.
One of your recent .dmps show lot of NTFS errors.
If you have a SSD, update to the latest firmware for it.
Upload a screenshot of your hard disk using crystal disk info:
- CrystalDiskInfo - Software - Crystal Dew World
- Screenshots and Files - Upload and Post in Seven Forums
Run Disk Check on your hard disk for file system errors and bad sectors on it:
Hard drive test both short and long with:
And the DOS version of seatools at last:
- SeaTools for DOS
- Here's a guide:
SeaTools for DOS tutorial
Stop any sort of overclocking if you are.
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Let us know the results.The goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
Alright, here are the results.
I ran the chkdsk utility multiple times, and found no errors. I've uploaded the msinfo.txt file also. Everything seems normal- and there are no firmware updates for my SSD, which is where I run windows off of. Could it possible be a driver issue? There have been an onslaught of new driver updates, and I noticed it started happening around that time.
Thank you for your help.
Please uninstall the following software: (with Free Revo Uninstaller - Advanced mode)
Your other .dmp shows lot of errors with NVIDIA.Code:
- Start Menu\Programs\GIGABYTE Public:Start Menu\Programs\GIGABYTE Public
- Start Menu\Programs\GIGABYTE\AutoGreen Public:Start Menu\Programs\GIGABYTE\AutoGreen Public
- Start Menu\Programs\GIGABYTE\EnergySaver2 Public:Start Menu\Programs\GIGABYTE\EnergySaver2 Public
- Start Menu\Programs\GIGABYTE\ET6 Public:Start Menu\Programs\GIGABYTE\ET6 Public
- Start Menu\Programs\GIGABYTE\Smart 6 Public:Start Menu\Programs\GIGABYTE\Smart 6 Public
The latest drivers for NVIDIA are a little problematic as I've heard. Click on the Start► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA Reboot the system. Now delete remnants of its drivers using Driver Fusion/Sweeper. Reboot if required
Download and install the drivers from the link of Filehippo bellow:
Video Card - Stress Test with Furmark
Monitor your temps with Speccy during these tests
Let us know the results.
ALright, I uninstalled what you asked with the said programs you stated. I also re-installed all of the NVIDIA components, and did not update to the latest drivers since they seem to be buggy. Video stress tests came out excellent so no problems there. Since I've done these steps, I have experienced no new BSOD's and I've been testing my computer on various tasks from gaming, video editing, music production, word processing, web browsing- everything. Everything seems A ok. Thank you Koolkat77!
I think we can mark this as solved :)
Are you still having problems with your pc? Let us know.
You should also take memtest as mentioned.
Alright, I had issues with this a few months ago, and now the exact same issues are back! I've ran some memory tests and stress tests, and none of these results indicate that hardware is the issue-- I'm thinking my unknown BSOD's are due to a weird software driver error, as stated in the WhoCrashed results.
Thank you for your help in advance-- I hope I can solve this issue once and for all, and if not, well, there's always a clean install option! :)
Can you run Driver Verifier and let it crash the system some, then send us the new crashdumps? Thanks. Remember to restart the system cleanly (at least shut down cleanly) otherwise the settings are lost.
Hello,
I've been doing some troubleshooting since last night. I ran the startup repair utility which did nothing, and even BSOD's in safe mode when trying to test some other things. I also ran another memtest which came up with no errors, and a chkdsk which also had no errors.
I ran driver verifier, and it started crashing my computer before I even got to the Windows desktop. I have uploaded an updated copy of everything from the SF Diagnostic Tool, and have taken some extra precautions and backed up my files with Knoppix as my backup OS. Hopefully I won't have to do a fresh re-install, but at this point, the BSOD's are hindering my work (and also play) and I'm willing to re-install if it's strongly recommended!
I launched WhoCrashed and these are a few of the reports I have gotten in the past 24 hours:
On Mon 2/4/2013 5:41:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-26941-01.dmp
This was probably caused by the following module: gdrv.sys (gdrv+0x1809)
Bugcheck code: 0xC4 (0xF6, 0xE0, 0xFFFFFA801AC3AB30, 0xFFFFF8800B794809)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gdrv.sys .
Google query: gdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Mon 2/4/2013 5:40:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-33212-01.dmp
This was probably caused by the following module: gdrv.sys (gdrv+0x1809)
Bugcheck code: 0xC4 (0xF6, 0xE0, 0xFFFFFA801B446640, 0xFFFFF8800A55F809)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gdrv.sys .
Google query: gdrv.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Mon 2/4/2013 8:41:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-20888-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3284F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880059CE84F, 0xFFFFF88002B464F8, 0xFFFFF88002B45D50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Google query: dxgmms1.sys Microsoft Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 2/4/2013 8:37:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020413-20592-01.dmp
This was probably caused by the following module: fastfat.sys (fastfat+0x1D82)
Bugcheck code: 0x23 (0xE0107, 0xFFFFF88004DA5038, 0xFFFFF88004DA4890, 0xFFFFF800025116B5)
Error: FAT_FILE_SYSTEM
file path: C:\Windows\system32\drivers\fastfat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Fast FAT File System Driver
Bug check description: This indicates that a problem occurred in the FAT file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Google query: fastfat.sys Microsoft Corporation FAT_FILE_SYSTEM
On Mon 2/4/2013 7:44:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-28017-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFF918019853D80, 0x0, 0xFFFFF800024B76B5, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 2/4/2013 6:50:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020313-10280-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800AEF4BF8, 0xFFFFF8800AEF4450, 0xFFFFF880018FCC91)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Let me know if you need any other information.
Note: At the time of the FAT.sys crash, I had an external hard-drive plugged in that is in FAT32.
Quote