Windows 10: BSODs trying to update graphics driver

The date on the driver is very old, 2011. Either uninstall Folder Lock or update it to a later level.[/quote] I think this did it. Uninstalled folder lock, then was able to install the latest audio drivers, no problems. Thank you for your help and your patience!

On a side note, because of all this, I decided to look into how to read dmp files with windows sdk, hopefully I can get to the point where I can help others!

 

I started about 6 months ago or so. I did a lot of dump reading back when I worked for IBM so was very familiar with the concept.
It just takes time and a willingness to do a lot of reading and looking at dumps handled by others. I've looked at lots and lots of threads handled by axe0, Arc and Essenbe.

It's fun most of the time though it gets a bit tedious when the dump doesn't contain anything useful for figuring out what is happening.

 

It is the same with many others, started to analyze dumps because they wanted to help others with their BSOD issues *Smile
Though I didn't wait with helping someone until I was at a certain level, I started immediately after I had the setup proper. Learning throughout the practice is a good method *Wink

 

Sorry to revive this, but I just got a new BSOD randomly, not doing anything out of the ordinary. Never had this BSOD before with this hardware (~5 years). Tried to look at dmp - is it suggesting it's caused by RAM errors? I don't remember exactly, but I'm pretty sure I ran memtest when I first got these sticks years ago and it was fine.

edit: after getting this BSOD a second time in the same day, decided to run memtest, immediately getting lots of errors. Never had memory problems until today.

BugCheck C1, {ffffcf8043262fb0, ffffcf804326239b, 330050, 32}
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+8a )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
Bugcheck Analysis
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: ffffcf8043262fb0, address trying to free
Arg2: ffffcf804326239b, address where one bit is corrupted
Arg3: 0000000000330050, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

 

That it is a hardware error is clear and good to know that you've found the cause, but why did you enable driver verifier?
Code: STANDARD FLAGS: [X] (0x00000000) Automatic Checks [X] (0x00000001) Special pool [X] (0x00000002) Force IRQL checking [X] (0x00000008) Pool tracking [X] (0x00000010) I/O verification [X] (0x00000020) Deadlock detection [X] (0x00000080) DMA checking [X] (0x00000100) Security checks [X] (0x00000800) Miscellaneous checks [X] (0x00020000) DDI compliance checking ADDITIONAL FLAGS: [ ] (0x00000004) Randomized low resources simulation [ ] (0x00000200) Force pending I/O requests [ ] (0x00000400) IRP logging [ ] (0x00002000) Invariant MDL checking for stack [ ] (0x00004000) Invariant MDL checking for driver [ ] (0x00008000) Power framework delay fuzzing [ ] (0x00010000) Port/miniport interface checking [ ] (0x00040000) Systematic low resources simulation [ ] (0x00080000) DDI compliance checking (additional) [ ] (0x00200000) NDIS/WIFI verification [ ] (0x00800000) Kernel synchronization delay fuzzing [ ] (0x01000000) VM switch verification [ ] (0x02000000) Code integrity checks [X] Indicates flag is enabled[/quote]

Nope, it is saying something caused memory corruption. Memory corruption isn't specific RAM:

From BSOD to Windows Crash

 

Nope, it is saying something caused memory corruption. Memory corruption isn't specific RAM:

From BSOD to Windows Crash[/quote] Thanks. I initially enabled driver verifier when I was having driver issues in the beginning of this thread. Didn't know what I was doing with it. Should I do anything with it now?

Can ram sticks "go bad" over time? I.e. I've never had problems with them until yesterday. I guess my next step is to isolate the sticks and figure out which of the sticks is bad, and try to contact manufacturer (lifetime guarantee) for new hardware?

 

All hardware go bad in a matter of time, it is why you can replace them *Wink

 

Sorry, I have to revive this again... I got 2 BSODs yesterday, and 1 more just now. Today's said resource not owned, and the dmp shows below, but not sure where to go from here. Is this related to my memory, or do I still have outdated drivers? Thanks in advance for the help!

Use !analyze -v to get detailed debugging information.
BugCheck E3, {ffffe001c2310be0, ffffe001c103d040, 0, 2}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3f46d )

 

Driver verifier enabled in all new dumps, in none is a driver flagged, 2 of them are 0x12B what basically indicates faulty memory.
A 0x3B which also is a memory issue in this case given the parameters. I'm less familiair with the 0xE3, so I wouldn't yet be able to say anything about it.

What I would suggest:
1. Cleanup your partitions, each partition needs at least 10-15% free space. 15% is to be on the safe side, 10% is an exception with large drives. Windows needs free space on each partition to perform background stuff without giving problems.
2. Check your SSD for firmware updates.
3. Remove this program, because it is using an extremely outdated driver that is known for causing BSODs
Code: 7/26/2008 8:29:37 AM \??\C:\Program Files\PhenomMsrTweaker\WinRing0x6[/quote]

What memory test exactly did you run?

Provided with the stacks I would also suggest some hard drive/partition diagnostics







Diagnostics Test

HDD TEST
*Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums



Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the error scan,
• the health,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.