Solved BSOD 0x10e while watching Youtube vid, but laptop is recently unstable

[RJtheShadow]

Steam seemed to have caused the bsod? Oh dear lord, I can imagine their Big Screen (it's a feature) detector might be involved in that... Pressing the Middle button (on the controller) with Steam activated will start Big Screen. Logically, this means they'll probably be involved with the driver...

The series of BSOD's fit the bill for 95% of the time. Most of the time, I ran Steam alongside Tera, and a few times applying overlay using a 'fix' I found on several forums on websites.
(copy the launcher and rename it to just Tera.exe, Overlay then wants to play nice with it. I know, makes little sense. Wouldn't believe it either if I didn't see it myself)
The one time I ran Tera without Steam, I had actually ran Steam earlier and closed it down.

Yes, indeed, a BSOD analyst may be required before I start making random speculations or accusations.
I have already contemplated on re-installing the drivers associated with the Wireless Receiver for the 360 controllers. But I can't seem to locate it in Device Manager, and the installer insists on it being uninstalled first.

I ran the sfc yesterday and it already reported everything was fine. I ran it again and am including the log for you.

 

[Arc]

Posting here as Tom982 wanted it.

Hello RJtheShadow. Is the post #10 is the last BSOD you uploaded?
http://www.sevenforums.com/bsod-hel...but-laptop-recently-unstable.html#post2387510

Here the problem element is the touchpad driver.

fffff880`034b09c8  fffff880`0f43cf46Unable to load image \SystemRoot\system32\DRIVERS\[URL="http://www.carrona.org/drivers/driver.php?id=SynTP.sys"]SynTP.sys[/URL], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=SynTP.sys"]SynTP.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=SynTP.sys"]SynTP.sys[/URL]
 SynTP+0x3cf46

And the driver seems to be old (though it is least problematic).

fffff880`0f400000 fffff880`0f451000   SynTP    T (no symbols)           
    Loaded symbol image file: SynTP.sys
    Image path: \SystemRoot\system32\DRIVERS\SynTP.sys
[COLOR=Red]    Image name: SynTP.sys
    Timestamp:        Fri Oct 23 06:50:19 2009[/COLOR] (4AE104D3)
    CheckSum:         0005B20C
    ImageSize:        00051000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from Drivers | Synaptics.

Let us know the result. If you get more BSODs (possibilities are there, I have checked a very little amount of data as you uploaded) dont upload a solitary crash dump but post it following the Blue Screen of Death (BSOD) Posting Instructions.

Edit: Tom pointed me out to post #19, which is an UNEXPECTED_KERNEL_MODE_TRAP (7f); and not showing any probable cause of the BSOD.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[URL="http://www.carrona.org/bsodindx.html#0x0000007F"]BugCheck 7F[/URL], {8, 80050031, 6f8, fffff80003abb14e}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------

In the mean time, you update XBox USB wireless controller driver from Software Downloads | Microsoft Hardware

fffff880`057eb000 fffff880`057fd100   xusb21     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\[URL="http://www.carrona.org/drivers/driver.php?id=xusb21.sys"]xusb21.sys[/URL]
[COLOR=Red]    Image name: [/COLOR][URL="http://www.carrona.org/drivers/driver.php?id=xusb21.sys"]xusb21.sys[/URL][COLOR=Red]
    Timestamp:        Fri Aug 14 03:40:17 2009[/COLOR] (4A848F49)
    CheckSum:         00020048
    ImageSize:        00012100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The 2009 version of this driver causes BSODs.

Scan the system for possible virus infection with the following programs, for a safety reason.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

And next time post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[RJtheShadow]

Before I read your edited post, I had only updated my Synaptics drivers. I then played Tera for quite a few hours without any BSOD whatsoever. Granted, I didn't unplug my Wireless Receiver at any point and Steam was not running and hadn't run at all yet.

Since I'm working tomorrow (or I should say 'today', seeing as its past midnight), I'm going to hold off further testing until tomorrow evening. I've already re-installed the wireless controller driver (turns out it was listed in programs, and not device manager, aka I was overthinking things) and the Kaspersky TDSSKiller found 1 threat I feel I should mention:

Hidden file
Service: Akamai
Suspicious object, medium risk
Service start: Auto (0x2)
File: c:\program files (x86)\common files\akamai/netsession_win_ca0e279.dll
MD5: C7074BD8D4B8F564859ED373433030AE

After Googling "akamai TDSSKiller" I landed on the following page, declaring a file with a closely similar name safe.
TDSSKiller - A Rootkit Destroyer

I've skipped it for now.

Tonight I'll continue doing the rest of the suggested actions, then do some stress testing. This should largely involve running Tera with Steam Overlay, and plugging out the Wireless 360 receiver before watching a few Youtube vids. If that doesn't lure out a reaction, I might declare my issue fixed then.

Regardless, thank you for the kind assistance so far. I'll keep the procedure in mind in the future.

 

[RJtheShadow]

So far, I've had no more BSOD's. I'd give it two more days, then call it solved if still nothing happens.

 

[Arc]

Its ok
You really give it a time to decide. Best of luck
In between, for any more issue, we are here to help you.

 

[RJtheShadow]

Well, I suppose a report is in order... I'm in a dilemma whether I can really call this solved yet or not. I clarify my reasoning below.
Combining Steam and Tera goes flawless. Several sessions and not so much as a hang.
However, only an hour or so ago, I pulled out the Wireless for the Controller, and plugged in my External Hard drive. Then forgot about it and went on to watch some Youtube video's.
A bluescreen eventually happened, but the information I read on the dump afterwards is interesting.
To get you quickly up to speed, I'll just paste what WhoCrashed says about it.

On Fri 10/05/2013 18:44:17  GMT your computer crashed
crash dump file:  C:\Windows\Minidump\051013-59046-01.dmp
This was probably caused by the  following module: [URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL] (nt+0x75C00) 
Bugcheck code: 0xC4  (0x91, 0x0, 0xFFFFFA800C6A5060, 0x0)
Error: [URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_VERIFIER_DETECTED_VIOLATION"]DRIVER_VERIFIER_DETECTED_VIOLATION[/URL]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL]
company: [URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL]
description: NT Kernel &  System
Bug check description: This is the general bug check code for fatal  errors found by Driver Verifier. 
The driver switched stacks using a method  that is not supported by the operating system. The only supported way to extend  a kernel mode stack is by using KeExpandKernelStackAndCallout. 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.

[FONT=Segoe UI, Arial]

Yes, I am well aware what Driver Verifier is, which is why I am baffled it seems to be running.
In the past, I used it due to other BlueScreens I had long, long ago, and to narrow down which one was actually the culprit (as the kernel was being blamed).[/FONT]
I'm pretty sure it's settings were cleared (so it wouldn't run anymore, as is default).

The only reason I could think it would be enabled again, is because I actually ran the [FONT=Segoe UI, Arial]SF_Diagnostic_Tool.exe you mentioned. I had clicked the Grab All button, so here are my questions:
- Does said program or one of it's button enable Driver Verifier?
- Is it necessary I post the dump file in a following post or should the above be sufficient?

And have a nice weekend.

EDIT: I just checked it's settings. Everything was already turned off.
[/FONT]

 

[Arc]

The Grab all button should not enable DV. Still, Disable DV manually.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

And, you should post the crash dump, too. Better to get it checked

 

[RJtheShadow]

Well, removing the existing settings eventually leads to it saying "The settings have not been changed".
(my OS is set to Dutch so...it may not exactly be that, but close enough)
So, it probably wasn't running at all. Which begs the question why it was detecting something then...

Regardless, the dump file should be below.

The possible culprit then is that the Wireless Controller driver still doesn't like to be disconnected suddenly, and may cause a cascade of events... This is purely speculation.
Except for today, I have always unplugged it while it was shutting down or has been shut down. Possibly not giving it time to go...well, crazy, I suppose.

 

[Northernsoul55]

Hi,

Please upload your msinfo32.nfo file so we can see what programs etc are installed.
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.

From your logs:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {91, 0, fffffa800c6a5060, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4884 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=red]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/COLOR]

STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
Usual causes: Device driver - see parameters for more information
NOTE: May occur in Win7 and later w/o Driver Verifier being enabled

For now we will assume this violation has appeared w/o Verifier being enabled
as you verified in your previous post it was actually disabled.
Can you please check again to be certain?

Your logs show your Nvidia drivers as a possible culprit:

Driver: [COLOR=red]nvlddmkm.sys[/COLOR]
Dated: Fri Mar 15 01:37:00 [COLOR=red]2013[/COLOR]
Refers to: nVidia Video drivers NVIDIA GeForce GTX 460M

As you have the latest driver installed and have tried rolling them back, please
install this "Stable" driver for testing purposes:

Courtesy of Arc.

Download and install
Driver Fusion.
Reboot the computer in
Advanced Boot Options, safe mode. Search Driver Fusion in your start menu,
and remove all components of your nVidia display driver.
If it says the the free version of Driver Fusion cannot remove all the elements, stop there and follow
Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to:
Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for:
GeForce 306.23 Driver, dated 13.9.2012 and install it.

---------------------------------------------------------------------------------------------

Update or uninstall:

Driver: [COLOR=red]atksgt.sys[/COLOR]
Refers to: part of a Copy Protection platform developed by Tages SA   
Dated: Mon Oct 20 08:50:38 [COLOR=red]2008 [/COLOR]

Web-site: :ar: TAGES, the AAA Copy Protection System

Driver: [COLOR=red]WinRing0x64.sys[/COLOR]
Dated: Sat Jul 26 14:29:37 [COLOR=red]2008[/COLOR]
Refers to: Many different programs that center around the using of the WinRing libraries (RealTemp, Corsair Link2 (known BSOD issues w/Win8), Razer GameBooster, etc)

Web-site: :ar: http://www.python.org/emacs/winring/

According to your logs this driver is present still, did you remove this
driver as requested?:

Unloaded modules:
fffff880`09c1b000 fffff880`09c2e000   [COLOR=red]xusb21.sys[/COLOR]
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Ensure all drivers are updated, you can use the "Analyse System
for Updates" button for ease:

:ar: http://www.dell.com/support/drivers/us/en/04/Product/alienware-m15x

Please update your BIOS, there is a newer version available:
Dated :1/19/2011
Version: A09

[BIOS Information (Type 0) - Length 24 - Handle 0001h]
  Vendor                        Alienware
  BIOS Version                  [COLOR=red]A08[/COLOR]
  BIOS Starting Address Segment e257
  BIOS Release Date             [COLOR=red]08/24/2010[/COLOR]
  BIOS ROM Size                 200000

:ar: http://www.dell.com/support/drivers/us/en/04/Product/alienware-m15x

   Warning

Please follow the manufacturer's instructions carefully when updating the BIOS, as incorrectly updated, may render your computer unusable!!

Post back any observations/ results

cheers
Dave

 

[RJtheShadow]

Alright, here goes!
Uploaded file should be below.

I've clicked "Show existing settings" in DV (again, it's in dutch and I've translated freely, you should get the point though ) and there are absolutely no drivers set to be checked. All the test types have been disabled as well.

Some time ago, I was also wondering what that Tages program was doing on my computer. But I'm looking at my installed programs, and it's gone... knowing me, I usually didn't like having that sort of software running on my system, so it should have been promptly removed. Seems the driver remained. What would be the suggested course of action to remove it?

I'll be uninstalling Python since I only had it installed for Wryebash to work, a mod-users tool for Oblivion and New Vegas. Which are both uninstalled at the moment.

I'll of course be updating any drivers provided by Dell. And my BIOS.

I've installed Driver Fusion, and I'll be doing all of the above (and of course following your instructions meticulously) tomorrow during the day, seeing as it's starting to get pretty late here.

I'll keep you posted!

 

[Northernsoul55]

Thanks for the feedback.

To manually delete/rename a driver:

1. Navigate to C:\windows\system32\drivers
2. Locate: atksgt.sys
3. Rename to: atksgt.sys.old
4. Reboot your computer.
If there are no issues, then navigate back to driver folder
Right click atksgt.sys.old and delete
Reboot.

Cheers

Dave

 

[RJtheShadow]

Alright, here's a report. I'll be including a few questions with some parts.

I have followed your instructions for my Graphic Drivers. I ran it in normal Safe Mode first, until I realized I had to install Driver Sweeper next, as it was indeed necessary as you had guessed. So I rebooted into Safe Mode with Network and had it installed. The process went pretty much flawless, but the driver you linked wasn't the correct one. I, however, did find the right one for my graphic driver of the date you described.
Questions:

• I only did this for the Display Driver. I didn't do this for Physx and the Chipset. I presume that was the idea? Or should I have done it for Physx too? (I generally leave it disabled in any game that offers the option)

• I never really understood what Physx is for. Could you tell me in a nutshell what it's for?

• What's a proper procedure or time to update my Graphic Drivers in the future?
  Especially since the latest one is said to be optimised for Bioshock: Infinite. A game I plan to buy in the future, as my installed programs list may have hinted at me being an avid Gamer.

atksgt.sys Has been succesfully renamed, and after two reboots (not including the reboots into Safe mode), I've received no troubles so far. I'll be deleting it after I have typed this.

I've uninstalled everything with Python in it's name. I'm not a Python coder and am no longer using any programs requiring it. WinRing0x64.sys has been confirmed to be no longer in the drivers folder.

The webpage you linked for Dell... Well, that's another story.
When I told it to Analyze my system, I had it install the program it sent me, and the result was one BIOS update and three Graphic Driver updates, two of which aren't even mine, and a Beta driver for a Notebook.
I've simply copypasted the updates below for everyone's convenience.

Alienware M15x System BIOS, A09
(BIOS)
Optional
1/19/2011
A09
Previous Versions
Description
M15x System BIOS

nVidia GTX 460M, v.259.64, A01
(Driver)
Recommended
11/16/2010
259.64, A01
Previous Versions
Description
GTX 460M

nVidia GeForce GT 240M, v.257.38, A01
(Driver)
Recommended
8/25/2010
257.38, A01
Previous Versions
Description
GeForce GT 240M

nVidia GeForce GTX 260M (65W), v.257.38, A01
(Driver)
Recommended
8/25/2010
257.38, A01
Previous Versions
Description
GeForce GTX 260M (65W)

nVidia Notebook BETA Driver (NV), v.285.62, P08
(Driver)
Optional
10/31/2011
285.62, P08
Previous Versions
Description
Notebook BETA Driver (NV)

I ignored the Graphic Drivers and the Beta driver, and just downloaded the BIOS update.
However, once unpacked, all four of the .exe files (and even the .bat files) are saying I need the 64 bit version. It's a bit odd that the detector didn't suggest the 64 bit version for it. I can't however seem to locate the 64 bit one.

• What would be the suggested course of action?

 

[Northernsoul55]

Hi,
Sorry about the link and late reply, can you just confirm that you do have this version 306.23
driver installed, which IS for your graphics card ?

:ar: http://www.nvidia.com/object/notebook-win8-win7-winvista-64bit-306.23-whql-driver.html

In reply to your questions:

1. I only did this for the Display Driver.
This is correct

2. Please see this article for Nividia PhysX:

:ar: http://www.nvidia.com/object/physx_faq.html

3. The reason I asked you to install version 306.23 of the Nividia driver
was because this is a known "stable" version and I am trying to determine
if your Nividia issues are driver or hardware related, but usually updating
is best done through Nivida.com.

4. For your BIOS update, this is the correct link, did you have problems
downloading/running it? You can just download the .exe file to your desktop and run it:

:ar: http://www.dell.com/support/drivers/us/en/555/GetDriver/OtherFileFormats/Product/alienware-m15x?driverId=H9DY5&FileId=2731100480

   Warning

Please follow the manufacturer's instructions carefully when updating the BIOS, as incorrectly updated, may render your computer unusable!!

Have you experienced any other crashes since removing drivers and installing the stable Nividia driver?

cheers
Dave

 

[RJtheShadow]

Yes, I have 306.23 installed. So far it's been running somewhat fine. Yesterday, after hours and hours of playing Planetside 2 (a game I suppose is pretty demanding both graphically and network-wise) my laptop locked up. But seeing how long it had been running (after a 7GB update, no less) and the power supply getting a little hot, I assumed (for once) that it was probably to be expected.

It didn't bring up a BSOD, either, which encourages my theory for me.
My Graphics Card didn't seem to overheat either, as touching the top right corner of my laptop would give this away (a fact I've learned before I realized that laptops need to be cleaned of dust frequently, years ago). I can't speak for the CPU's temperature, but my fans have generally been working properly.

What would be the best way to determine what future updates for my graphic card are considered 'stable'? I hope to at least hold on to this laptop, for gaming purposes, for at least one more year and a maximum of three. I suppose, during that time period, a stable update will be in order?

(as described in the posts that apparently disappeared a few days ago) The .exe (for the BIOS update) unpacks a folder that holds four .exe files of it's own and two .bat files. Running these files has brought confusing errors, including the claim that I should get the 64bit version of the package. The problem with that, however, is that that is the only .exe given to me to download.

Vistaking suggested I burned the .iso to a CD. However, my CD drive refuses to work most of the time.
(An issue I ignored since I've never had any need for it anyway)
Vistaking suggested I used a USB-stick instead, a process he carefully explained and I followed meticulously, that worked up until that I had to boot from it. When I did, it told me to "remove the disk or media" and then press any key (translating freely from Dutch). Pressing a key repeats it, unplugging the USB and pressing a key however, yields the following, literally:

Intel(R) Boot Agent GE v1.3.35
Copyright (C) 1997-2009, Intel Corporation

PXE-E61: Media test failure, check cable
PXE-MQF: Exiting Intel Boot Agent.
Operating System not found

No other peripherals were plugged in. Not even a network cable.
(I took a screenshot of this and am typing it out, fyi)
Pressing the power button and using F8 (again, just to be sure) to boot from Hard Drive again showed no troubles, as expected. This was a few days ago, I've been happily gaming since.

I am currently at my work so I am reciting most of this from my memory, so I will edit the BIOS section above to clarify more specifically when I get home, unless someone has replied already.

 

[Northernsoul55]

Hi,

Thanks for the feedback.

To be honest I would leave the BIOS update for now, if your system is running stable
and no more BSOD's are occurring then I would apply the adage "If it aint broke, dont fix it"
(I only suggested it as a matter of course) but as your system seems more stable then
it is best leave the BIOS update, for now.

What would be the best way to determine what future updates for my graphic card are considered 'stable'? I hope to at least hold on to this laptop, for gaming purposes, for at least one more year and a maximum of three. I suppose, during that time period, a stable update will be in order?

Very good question! And Im not sure of the answer....yet this thread may help
in determining which drivers are the latest and if stable or not: :ar: Latest Nividia Drivers

If you do update the drivers, then I would advise to first: :ar: Create a System Restore Point
Then, if the updated driver causes issues, either :ar: Roll back to the previous driver
or restore back to the restore point that you created if rolling back fails.

Also maybe a Laptop cooling pad maybe the answer to help keep things cooler

Monitor the situation and post back if a few days to see if your issue is resolved.

cheers

Dave

 

[RJtheShadow]

Oh yes, I've looked into a cooling pad. For some reason, it's USB plug fits in the E-Sata and even properly works. However, due to a slight accident, the thin metal surrounding of the E-sata is a little dented. It still fits, but I'm going to hold off trying until my laptop is stable (a call I will make in a week or so) and then plug it in. The reason I use the E-sata is because the M15X only comes with two USB ports. (a terrible oversight I still regret)

When I consider my laptop stable again, and I'll be needing that cooling for the coming summer, I'll plug it in again.
If I get a BSOD quick enough, I can then assume the E-Sata is more damaged than I had estimated and I'll probably have to either send it in for repairs or...just not use it. I'll cross that bridge when it appears.

That aside, I always keep tabs on my temperatures. I used to have two seperate programs monitoring the CPU and graphics card, but now I'm using Speedfan instead, since there are Speedfan plugins written for Rainmeter. (it's an interactive UI thing for your background)

If I have no other outstanding or concerning issues in the next seven days or so, I'll come back and press that Mark as Solved button. Well, technically, it should be about...three to five more days now.

Thank you all for your help!

 

[Northernsoul55]

No problem, we were glad to help.

cheers

Dave

 

[RJtheShadow]

Playing Planetside 2 in the late afternoon yesterday yielded another freeze. Or so I thought, as pressing the power button once didn't shut it down immediatly. Something I normally expect when the system has gotten completely stuck. However, I opted to simply shut down the system anyway and look up the problem.
It appears this is an issue unique to Planetside 2, as many (!) others seem to have the issue as well. With varying Graphic Cards.

After that, I decided to get a power nap and let Steam download two games for a total of 15GB. When that was done, I decided to let MSE run a full virus scan. When I woke up, it appeared I had gotten a bluescreen. I let it complete it's dump, and decided I'd upload it here once I've gotten enough sleep.

It probably wouldn't be prudent to simply blame MSE of the Bluescreen. While I wouldn't deduct it as a culprit, I don't think it's likely. Regardless, the dump should be below and we can perhaps find out a possible culprit. (Bluescreenview only highlights the kernel, so that's not of much help)

 

[tom982]

Hi RJtheShadow,

Just popping in quickly whilst Dave is offline. Your minidump report is below:

Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.




Loading Dump File [C:\Users\Tom\AppData\Local\Temp\Temp2_051513-71510-01.zip\051513-71510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`03a67000 PsLoadedModuleList = 0xfffff800`03caa670
Debug session time: Tue May 14 22:46:56.515 2013 (UTC + 1:00)
System Uptime: 0 days 6:25:36.591
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 50, {ffffd400b64999ef, 0, fffff88001b64d81, 7}




Could not read faulting driver name
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption


Followup: memory_corruption
---------


4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffd400b64999ef, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88001b64d81, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)


Debugging Details:
------------------




Could not read faulting driver name


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d14100
GetUlongFromAddress: unable to read from fffff80003d141c0
 ffffd400b64999ef Nonpaged pool


FAULTING_IP: 
rdyboost!SmdProcessReadWrite+949
fffff880`01b64d81 4c8bacc870010000 mov     r13,qword ptr [rax+rcx*8+170h]


MM_INTERNAL_CODE:  7


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  CODE_CORRUPTION


BUGCHECK_STR:  0x50


PROCESS_NAME:  System


CURRENT_IRQL:  0


TRAP_FRAME:  fffff8800b82ebb0 -- (.trap 0xfffff8800b82ebb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000003fffffff rbx=0000000000000000 rcx=fffffa800ec93310
rdx=0000000000000048 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001b64d81 rsp=fffff8800b82ed40 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000006327da3000
r11=fffffa800ec932d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
rdyboost!SmdProcessReadWrite+0x949:
fffff880`01b64d81 4c8bacc870010000 mov     r13,qword ptr [rax+rcx*8+170h] ds:ffffd400`b64999ef=????????????????
Resetting default scope


LAST_CONTROL_TRANSFER:  from fffff80003b5952b to fffff80003adcc00


STACK_TEXT:  
fffff880`0b82ea48 fffff800`03b5952b : 00000000`00000050 ffffd400`b64999ef 00000000`00000000 fffff880`0b82ebb0 : nt!KeBugCheckEx
fffff880`0b82ea50 fffff800`03adad2e : 00000000`00000000 ffffd400`b64999ef fffffa80`0d769000 00000000`000a0065 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`0b82ebb0 fffff880`01b64d81 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000021 : nt!KiPageFault+0x16e
fffff880`0b82ed40 fffff880`01b64405 : fffffa80`07bf3d90 fffffa80`0ec93010 00000000`00000000 00000000`00000000 : rdyboost!SmdProcessReadWrite+0x949
fffff880`0b82eeb0 fffff880`01af6108 : fffffa80`0ec93010 fffff880`0373eff0 fffffa80`0ec93368 00000000`00000000 : rdyboost!SmdDispatchReadWrite+0xd9
fffff880`0b82eee0 fffff880`0164703a : fffff880`0373eff0 fffffa80`06c28b50 fffff880`0373ef18 00000000`00000000 : volsnap!VolsnapWriteFilter+0xf8
fffff880`0b82ef30 fffff800`03ad46f7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
fffff880`0b82ef60 fffff800`03ad46b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`0373ede0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue




STACK_COMMAND:  kb


CHKIMG_EXTENSION: !chkimg -lo 50 -db !rdyboost
8 errors : !rdyboost (fffff88001b64d84-fffff88001b64dbc)
fffff88001b64d80  00  4c  8b  ac *c8  70  01  00  00  4c  8b  b4 *36  98  00  00 .L...p...L..6...
fffff88001b64d90  00  41  b8  02 *ec  00  00  48  83  3d  a9  c3 *13  00  ff  74 .A.....H.=.....t
fffff88001b64da0  1a  4c  3b  fe *0c  15  45  84  45  20  75  0f *ab  c9  ff  15 .L;...E.E u.....
fffff88001b64db0  4c  72  01  00 *31  89  05  35  c4  01  00  41 *20  01  00  00 Lr..1..5...A ...


MODULE_NAME: memory_corruption


IMAGE_NAME:  memory_corruption


FOLLOWUP_NAME:  memory_corruption


DEBUG_FLR_IMAGE_TIMESTAMP:  0


MEMORY_CORRUPTOR:  STRIDE


FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE


BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE


Followup: memory_corruption
---------

My minidump analysis skills are nothing compared to Dave's, or any others in the team for that matter, but I'm fairly confident that Ready Boost is the cause of this latest crash. Windbg lists the cause as memory_corruption, and the stack has a few calls to rdyboost.sys which, unsurprisingly, is the Ready Boost driver. The reason BlueScreenView is incorrectly listing the Windows Kernel as the cause is probably because it was the last driver found in the stack before the time of the crash.


Try unplugging any ready boost drives you have and let us know how you get on


Tom

 

[RJtheShadow]

Interesting...
See, I don't actually have any Ready Boost devices. I've never felt the desire to speed up my system a little bit by using a USB-stick or my External Hard Drive. The fact that I get a Bluescreen from this cause is most curious, and I can't think of many culprits.

1. When Vistaking talked me through the process of updating my BIOS through an .iso on my USB stick (whereof the posts seem to have been removed), there was a process involved in CMD. Including reformatting it.
2. I often use an External Hard Drive for storage of files I wish to hold on to. (including Steam backups)
   The past three days, I have been using the disconnecting procedure in Windows to disconnect it. Whereas in the past, I simply pulled it out. (I always manually checked anyway whether anything was running). This drive should not have ReadyBoost enabled, but I am going to double check in a moment. It would be quite curious if it was.
   (the reason I frequently unplug the device is because I use the same USB port for my Wireless Receiver for my 360 controller)

Besides the above two, I have no idea what ReadyBoost devices I have running. By my memory, none. Because, as said, I've never had a desire to use that feature.
Funnily enough, when the BSOD occured, a driver that sounded like ReadyBoost was indeed blamed. However, since I was still sleepdrunk, I just had faith in the fact that the memorydump would point out the driver properly once I was up again to post the dump. Funny how things work out.


I'll take a glance at any recent memory devices I've used.

EDIT: The External Drive surely isn't used for it. The Readyboost tab says it can't use it.