BSOD error 0x000000d1

ThokeB · 12 Sep 2012

Hi, I've been having these strange BSODs with my Sony Vaio laptop at least 1-2 months for now.

I was directed here from Sony forums. For reference: Sony: Vaio unexpected shutdowns. There you can see bigger description about my BSODs.

Things that've been changed since then is that I've updated/deleted a few of my programs, and uninstalled and then clean installed my graphics card driver in hopes for solving the problem. But shutdowns still happen, and in both of my Windows accounts, just not all the time like before. Recently all of the shutdowns have happened with my new account but not with the administrator account.

I've attached the information the way you've guided me to.

If you require more information, I'm more than willing to help. Just to say in advance, I appreciate your help very much.

---

My observations:

* BSOD always happens when I'm running Program Accelerator by iolotools in Vaio Care. Program Accelerator - Overview. The computer either crashes after an hour or two when left idling with Program Accelerator running or under half an hour if I use the computer while Program Accelerator running in the background. Two days ago it took only few minutes for my computer to crash when I was surfing in the web while Program Accelerator was running. I usually leave my computer alone when Program Accelerator is running.
These BSODs happen frequently.

* Some BSODs have occured when dowloading huge file(s) from the internet. Most notable memory of this was when my computer crashed in middle of installing new version of Bitdefender (the installer installed and downloaded files simultaneously). I needed to do a rollback because Bitdefender was completely broken after the BSOD. These BSODs have happened a few times.

* Some BSODs have happened while normally surfing in the web (light use) with battery power. This usually happens if some page loads a long time. I think this happens only when my computer isn't attached to power source.

* Some BSODs have happened while using Vaio Care in general (not Program Accelerator). This is the rarest BSOD I've had, these have maybe happened only once or twice. BSOD occured when Vaio Care was fixing performance issues (using disk defragmenter, disk cleaner, registry defragmenter).

Strange thing is that these BSODs NEVER occur when the game CivIV:BtS is running (and the other potential BSOD causers are in the background). I've used this as an interim (so I can download files from the web, run Program Accelerator, etc)

koolkat77 · 12 Sep 2012

Welcome

Your dumps do not give a probable cause for the crash.

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

ThokeB · 12 Sep 2012

Hi!

...and wow! BSOD happened only within few minutes after enabling the driver verifier, and after that Windows didn't start at all except in safe mode. So the computer crashed 2 times. I got technical details from both of them and I'll also post a new zip.
Here are the technical details I got from the BSODs:

1st:
STOP: 0x0000001E
(0xFFFFFFFFC0000005,
0xFFFFF80003887484,
0x0000000000000000,
0xFFFFFFFFFFFFFFFF)

2nd:
STOP: 0x0000000A
(0xFFFFF9800E20EBA8,
0x0000000000000002,
0x0000000000000000,
0xFFFFF80003D2B2B9)

Anthony · 12 Sep 2012

Man do yourself a favor: Clean Reinstall - Factory OEM Windows 7

Far too much crap on there!!

Vir Gnarus · 12 Sep 2012

Having this kind of instability so early in a system's life means only one thing: hardware failure. Also so far I'm seeing data corruption about a byte in size in your CPU registers, which is highly conducive of hardware failure. In addition, I don't see that Driver Verifier was active at the time of Sept 12, 1:44 PM, so that won't be able to help us. DV may be causing the crashes, but they may be too early during bootup or involved with drivers necessary to produce crashdumps (disk I/O drivers) and therefore the dumps cannot be written.

If you want my recommendation, get the system replaced. There's an active warranty, and there's really no point fiddling with this any further when there's nothing to be lost by sending it for replacement, given how young the system is. Sony will probably stress on dealing with it one hardware piece at a time but it shouldn't be worth your time to do so, so you'll want to pressure them (respectfully of course) to replace it with a new system, instead of sending it for repairs that may happen over and over again.

EDIT: err, I misread your statement. I thought you said you've had the system 1-2 months. My apologies. In that case, assuming your system is older, you'll want to do some hardware tests, starting with Memtest overnight.

FredeGail · 12 Sep 2012

Information

Just a quick jump-in by a request

EDIT: Seems like we all posted at once, feel free to do all of our steps

Hello Thoke and thank you very much for choosing Seven Forums.

* What diagnoses have you done so far?
* Have you installed anything new recently?
* How does your computer act in safe-mode?

BSOD ANALYSE

Updating System Specs will give us a better sight of
how your system is put together. It's simply done.

Code:

0: kd> !verifier
fffff80003a61ac0: Unable to get verifier list.

Not sure if Driver Verifier is enabled at this point. Are you able to upload any new dump with verifier enabled upon it?

Best Regards,
Frederik.

Vir Gnarus · 12 Sep 2012

Analysts:

What appears to be a few corrupted bytes in CPU registers and in RAM, which has evidently corrupted the instruction pointer, causing the bad instruction. I'm not able to ascertain from minidumps where the corruption originated from:

Code:

TRAP_FRAME:  fffff80000b9c290 -- (.trap 0xfffff80000b9c290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8006a9c2b8
rdx=ffff4d8006a9c1a0 rsi=0000000000000000 rdi=0000000000000000
rip=ffffa88001975160 rsp=fffff80000b9c428 rbp=0000000000000000
 r8=00000000596ac533  r9=0000000001cd8530 r10=fffff80003a0ee80
r11=fffff80000b9c400 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ffffa880`01975160 ??              ???
Resetting default scope

STACK_TEXT:  
fffff800`00b9c148 fffff800`0389b769 : 00000000`0000000a ffffa880`01975160 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`00b9c150 fffff800`0389a3e0 : fffffa80`405c0088 fffff880`04d97530 fffffa80`071296f0 fffff800`00b9c4f0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c290 ffffa880`01975160 : fffff800`038a6e3c 00000000`00000000 00000000`00000007 00000000`00000006 : nt!KiPageFault+0x260
fffff800`00b9c428 fffff800`038a6e3c : 00000000`00000000 00000000`00000007 00000000`00000006 fffff800`00b9c500 : 0xffffa880`01975160
fffff800`00b9c430 fffff800`038a6cd6 : fffffa80`06a9a278 00000000`0006cfdc 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`038a6bbe : 00000010`370f3d63 fffff800`00b9cb18 00000000`0006cfdc fffff800`03a12e08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`038a69a7 : 00000003`cac487c7 00000003`0006cfdc 00000003`cac48789 00000000`000000dc : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`03893eca : fffff800`03a0ee80 fffff800`03a1ccc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiBugCheckDispatch+69
fffff800`0389b769 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiBugCheckDispatch+69

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiBugCheckDispatch+69

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiBugCheckDispatch+69

Followup: MachineOwner

This is from the first crashdump. The newest one from today looks to have the stack trashed by a bunch of garbage. They're not ASCII so it's probably some kind of data or code.

ThokeB · 12 Sep 2012

If I clean re-install Windows, is my computer still recognised as the same computer? I'm asking this because I have some 1-computer-licences and if they become unusable after clean install, I will have a lot of financial problems afterwards . My uncle had problems with licenses after some hardware components of his computer were changed, could the same happen with this? And it doesn't void the warranty, I think? My common sense says no...

OK, it seems I got a ton of advice

Yes, I have warranty left. I bought this computer 6th of June this year and the warranty is 2 years starting from that date. My computer started crashing approximately after 1 month of usage. EDIT: actually after 1-3 weeks after thinking it more.

So, should I continue trying to repair this or contact Sony warranty support?

And now I really must go to sleep. I'll check these forums tomorrow as soon as I can.

Dave76 · 13 Sep 2012

It will depend on the programs, most will allow re-installation on the same system.

Not alot to go on with these dumps.
Crash info.

Code:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
IMAGE_NAME:  ntkrnlmp.exe
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
IMAGE_NAME:  ntkrnlmp.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!ViPendingCompleteAfterWait+49

Drivers that need updating or removed.
ArcSoftKsUFilter.sys Mon May 25 2009 - ArcSoft Magic-i Visual Effect - Out of date, update or remove

Unloaded modules, these are failed drivers/devices.

Code:

LHidFilt.Sys - Logitech SetPoint HID Filter Driver
LMouFilt.Sys - same as above
btath_rcp.sy - Atheros Bluetooth Driver
hidbth.sys - Microsoft Bluetooth Miniport Driver for HID Devices
BthEnum.sys - Bluetooth Bus Extender
BTHUSB.sys - Bluetooth Miniport Driver
btfilter.sys - Atheros Bluetooth Driver
mouhid.sys - HID Mouse Filter Driver

Are you using a Logitech mouse or keyboard?
If you are, disconnect them and check if you are still having crashes.
Disconnect all USB devices, check for stability.
Turn off your bluetooth for testing.

Have you updated your drivers from the Sony support site?
If not, update all drivers with a newer date than yours.

App Event Log.

Code:

Event[81]:
  Log Name: Application
  Source: Microsoft-Windows-WMI
  Date: 2012-06-14T08:50:15.000
  Event ID: 10
  Task: N/A
  Level: Virhe
  Opcode: N/A
  Keyword: Perinteinen
  User: N/A
  User Name: N/A
  Computer: Tuukan-Vaio
  Description: 
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

This indicates a problem with your CPU, could be overheating.
Check your CPU temps.
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

If your CPU temps are ok, we can run a CPU test.

ThokeB · 13 Sep 2012

FredeGail said:

Hello Thoke and thank you very much for choosing Seven Forums.

* What diagnoses have you done so far?

Hi.
I'll post my observations here:

* BSOD always happens when I'm running Program Accelerator by iolotools in Vaio Care. Program Accelerator - Overview. The computer either crashes after an hour or two when left idling with Program Accelerator running or under half an hour if I use the computer while Program Accelerator running in the background. Two days ago it took only few minutes for my computer to crash when I was surfing in the web while Program Accelerator was running. I usually leave my computer alone when Program Accelerator is running.
These BSODs happen frequently.

* Some BSODs have occured when dowloading huge file(s) from the internet. Most notable memory of this was when my computer crashed in middle of installing new version of Bitdefender (the installer installed and downloaded files simultaneously). I needed to do a rollback because Bitdefender was completely broken after the BSOD. These BSODs have happened a few times.

* Some BSODs have happened while normally surfing in the web (light use) with battery power. This usually happens if some page loads a long time. I think this happens only when my computer isn't attached to power source.

* Some BSODs have happened while using Vaio Care in general (not Program Accelerator). This is the rarest BSOD I've had, these have maybe happened only once or twice. BSOD occured when Vaio Care was fixing performance issues (using disk defragmenter, disk cleaner, registry defragmenter).

I think these BSODs are cumulative. If I'd use Program Accelerator AND download huge files from the web BSOD would occur lightning fast I bet.

Other strange thing is that these BSODs NEVER occur when the game CivIV:BtS is running and the other potential BSOD causers are in the background. I've used this as an interim (so I can download files from the web, run Program Accelerator, etc)

* Have you installed anything new recently?

Bitdefender Internet Security 2013 (I had 2012 before), and I also clean-installed Nvidia graphics card driver 301.42 WHQL (newest driver that should support my laptop).

* How does your computer act in safe-mode?

It is very stable.Though I don't know enough to say if anything unusual happens while my computer is in safe mode. Everything seems normal.

BSOD ANALYSE

Updating System Specs will give us a better sight of
how your system is put together. It's simply done.

Ok, I'll do this.

Code:

0: kd> !verifier
fffff80003a61ac0: Unable to get verifier list.

Not sure if Driver Verifier is enabled at this point. Are you able to upload any new dump with verifier enabled upon it?

Best Regards,
Frederik.

I actually disabled the Driver Verifier after the BSODs happened. Should I enable it again and do a crash report with SF Diagnostic Tool in safe mode? I can't do it in normal mode because Windows won't start in that mode after Driver Verifier has caused the first BSOD.