Solved Driver Verifier BSOD's

usasma · May 9, 2012

Please make another set of jcgriff2 reports. That'll tell us if it's a BSOD that went by too quickly to see - or if it's an Event 41 shutdown (Windows shuts down without any reason).

dimitris21 · May 10, 2012

I attach the jcgriff2 + perfmon reports

edit: attached another dmp file

usasma · May 10, 2012

Lot's of Thermal events - but I can't seem to figure out exactly what they're telling us.
I suggest using this free hardware sensor monitor: CPUID - System & hardware benchmark, monitoring, reporting
See if it has an ACPI-THRM and a CPUTIN sensor - and watch them to see if they get too high just before the system shutdown.

dimitris21 · May 11, 2012

I am currently doing a reinstallation of the OS(using a win 7 + sp1 disc) just to make sure problems are not coming from the OS installation too

dimitris21 · May 11, 2012

compatibility check takes more than 2.5 hours.......!

dimitris21 · May 12, 2012

OK,after a lot of different errors coming up during the win 7 re-installation,it finally got through(been trying for more than a day!)

i attach a new jcgriff and perfmon report now that the os is newly reinstalled.
i'll continue with hardware stressing...

usasma · May 13, 2012

If errors continue with a "clean" install of Windows (from good installation media and fully updated) - it's usually an indication of a hardware problem.

With each additional 3rd party program installed, the likelyhood of a hardware problem decreases while the likelyhood of a 3rd party problem increases.

perfmon /report shows several issues with 3rd party items:
1 - several errors for VMWare networking. I've seen these a lot and don't usually worry about them. BUT, since we're troubleshooting your system I'd suggest uninstalling these devices - both from your system and from the VM's
2 - The unknown device belongs to your uGuru software/device. Please uninstall it also.
3 - Drivers for your G19 keyboard have not been installed.

Also, Windows Update is disabled - please enable it.
Only 3 updates after SP1. Most systems have more than 70. Please visit Windows Update and get all available updates.

Can't recall if I posted my SSD canned speech, so I'll post it here:

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

Click to expand...

No memory dumps in this upload. But previous dumps are suggestive of either a driver problem or a hardware problem.

Should the BSOD's recur, please run Driver Verifier according to these instructions: Driver Verifier Settings

dimitris21 · May 13, 2012

bsod while running blend in prime 95
i attach the minidump file and also the link to the memory.dmp(44mb) file

Download MEMORY.zip for free on uploading.com

usasma · May 14, 2012

Check temperatures while running Prime95 to ensure that the system isn't overheating (I like this free monitor: CPUID - System & hardware benchmark, monitoring, reporting ).

Run these 3 tests in Prime95:
- Small FFT's
- Large FFT's
- Blend (do it last because you know it crashed your system)

Measure the time until an error occurs in each one (and run them back to back). An error is either mentioned in the Prime95 output or the system crashes/goes crazy. Let us know the results. Just FYI - in general, getting errors fastest in the Blend test usually relates to RAM problems, while fastest errors in the other 2 tests relate to problems with the CPU cache or the memory controller (on either the motherboard or CPU - depending on your CPU model)

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
rr26xx.sys       Tue May 12 22:17:52 2009 (4A0A2DD0)
[Color=Red]SI3132.sys       Wed Oct 03 14:39:29 2007 (4703E1E1)[/Color]
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
[Color=Red]SiWinAcc.sys     Thu Jun 14 20:02:02 2007 (4671D6FA)[/Color]
[Color=Red]SiRemFil.sys     Wed Jun 20 15:42:10 2007 (46798312)[/Color]
trufos.sys       Wed Oct 19 05:10:43 2011 (4E9E9413)
vmnetbridge.sys  Mon Aug 10 08:05:58 2009 (4A800D26)
RtNdPt60.sys     Sun Jul 19 22:27:32 2009 (4A63D614)
LMouFilt.Sys     Fri Sep 02 02:23:15 2011 (4E607653)
VMkbd.sys        Sat Mar 26 01:31:22 2011 (4D8D7A2A)
LHidFilt.Sys     Fri Sep 02 02:23:09 2011 (4E60764D)
Rt64win7.sys     Wed Nov 23 10:00:40 2011 (4ECD0A98)
bdfwfpf.sys      Mon Nov 14 12:16:17 2011 (4EC14CE1)
bdvedisk.sys     Tue Jan 19 10:45:31 2010 (4B55D39B)
hcmon.sys        Sat Mar 26 00:40:38 2011 (4D8D6E46)
vmci.sys         Sat Mar 26 00:08:49 2011 (4D8D66D1)
vmx86.sys        Sat Mar 26 02:18:58 2011 (4D8D8552)
cpuz135_x64.sys  Wed Jan 19 11:42:06 2011 (4D37145E)
vmnetuserif.sys  Sat Mar 26 00:55:31 2011 (4D8D71C3)
vstor2-ws60.sys  Thu Aug 19 16:28:39 2010 (4C6D93F7)
appdrv01.sys     Wed Aug 25 08:03:46 2010 (4C7506A2)
cmudaxp.sys      Mon Jul 04 03:00:48 2011 (4E116520)
LGBusEnum.sys    Mon Nov 23 20:36:48 2009 (4B0B38B0)
kerneld.amd64    Wed Feb 17 13:47:03 2010 (4B7C39A7)
ALSysIO64.sys    Sat Jul 09 20:27:45 2011 (4E18F201)
DKRtWrt.sys      Mon Feb 14 05:03:42 2011 (4D58FDFE)
nvlddmkm.sys     Thu Feb 09 21:02:58 2012 (4F347AD2)
vmnetadapter.sys Mon Aug 10 08:04:53 2009 (4A800CE5)
VMNET.SYS        Mon Aug 10 08:04:50 2009 (4A800CE2)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051312-20750-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 13 12:14:26.677 2012 (UTC - 4:00)
System Uptime: 0 days 0:22:11.491
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+433 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  vsserv.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+433
Bugcheck code 0000000A
Arguments 00000000`00010082 00000000`00000002 00000000`00000001 fffff800`03290943
BiosVersion = 6.00 PG
BiosReleaseDate = 01/15/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz"
MaxSpeed:     2660
CurrentSpeed: 2660
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

dimitris21 · May 14, 2012

Hopefully the stress will show what's going on - the problem, however, is i am getting a few event 41 and 6008's....which can mean too many different things - i actually just got a 6008 few mins ago and system went black and restarted - only thing i was doing i had firefox open and browsing the forums....

usasma · May 14, 2012

Event 41's simply mean that the system is shutting down - and Windows doesn't know why.
This means (IMO) that 3rd party programs and Windows stuff is ruled out - leaving hardware as the cause.

Prime95 failing on the Blend test indicates (to me) that it's a memory problem. Either RAM, CPU cache, or the memory controller. That's why I requested that you run the small FFT's, large FFT's, and Blend test. Running them together keeps the consistency of error reporting more constant (which is essential if we're trying to decide what's at fault).

dimitris21 · May 14, 2012

running small fft's now

(just a note - 3 different monitor programs give me 3 different temperature readings - core temp,cpuid and everest ultimate - pic attached)
btw. since prime95 allocates a certain amount of ram for its use -leaving maybe 5-10% free ram,could it be possible that if an application requests ram at the same time,a system crash would occur since there is not enough free memory? or it would just slow down until the memory is available?

and also, i am running the ram at 1 speed down - the sticks are pc2-8500 and i am running them at 400mhz-pc2-6400(only one stick at the moment) and at more relaxed timings(5-5-5-18-53) instead of (5-5-5-15-43).
last night,memtest86 concluded 5 passes of this particular stick with no errors.
however if the problem is at the memory controller,and not at the actual ram-stick,would the memtest give out an error?

usasma · May 14, 2012

Memory is a complicated issue but it's not likely that the Windows Memory Manager would allow any program to take too much RAM (although a corrupted program could conceivably do this indirectly). IME the system just slows to a crawl until Prime95 is stopped by the user.

I haven't messed around with RAM timings/settings/voltages since my overclocking days (back around 2000/2001). So I'm not familiar with the specs/performance of modern day RAM. That being said, Memtest is better at testing RAM than Prime95 - but Prime95 is better at stressing RAM than Memtest is. A small difference, but a significant one none the less. It's possible (and happens fairly frequently) that RAM will pass Memtest, but will fail on Prime95.

dimitris21 · May 14, 2012

ok small fft completed 2 full loops - no errors
moving to large fft's

dimitris21 · May 14, 2012

bsod while running large fft's but it's probably a driver

usasma · May 14, 2012

How soon until the crash? Faster or slower than in Blend?

dimitris21 · May 15, 2012

well the crash while running large fft's occured much longer than the first blend run.however the condition of the pc,regarding installed programs,running services etc was different,so i am running the blend test again now to compare the two tests with the same conditions

usasma · May 15, 2012

FYI - your memory controller is contained in the Northbridge on your motherboard.
This means that failing the large FFT's and the Blend test means that it's most likely RAM, but can be the motherboard.

The "test" here is to test the memory sticks individually with Prime 95 in both Blend and Large FFT's - to see how long it takes to error out with each stick (and also trying them in different slots).

dimitris21 · May 15, 2012

blend test failed in 20 mins(much faster than large fft's which crashed after 3 hours or so) - with the following bsod: an attempt was made to write to read only memory
attached is the dump file of the blend test bsod.
also,i attach a dump of a bsod which happened afterwards while watching a movie(using Splayer)

ok i will try each stick to all slots - then move to the next stick

usasma · May 15, 2012

With Blend failing faster it's most likely that one or more of the sticks is at fault (but the slots can be defective also and can give similar results - that's why I asked that you rotate them through the tests also).

What we need here is a stick/slot combo that doesn't spit errors in Prime95. That will confirm that the other, error causing sticks/slots are to blame.

If you don't get a distinct problem stick/slot, then it's uncertain if this is a RAM or mobo problem. As Blend fails faster I'd have to guess RAM, but it's not my wallet that's involved in the next step.

Check to see if you can return your RAM under warranty to OCZ and get a new set. That'll help to rule out the RAM with the least cost.

Good luck!

Solved Driver Verifier BSOD's

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer