Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Frequent system-crashes in Windows 8.1 - Why?

by Mar 29, 2014 10:05PM PDT

My Sony Vaio Tap 11 (model: SVT1121C5E) runs very unstable ever since I bought it about 3 months ago.

Almost every day the system crashes, sometimes multiple times. Sometimes with prior bluescreen, Windows colleting data and then stopping at 100%.
Occasionally the device shuts down and automatically restarts.
Sometimes the screen becomes black and the device can be turned off only by holding the power-button for a few seconds.

I am running Windows 8.1 and all the current device-drivers, bios-update and Windows-updates are installed. I would really need some help here.

The event-viewer has some "Event41, Kernel-Power" entries in the category "critical" such as following:

<event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <system> <provider name="Microsoft-Windows-Kernel-Power" guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}"> <eventid>41</eventid> <version>3</version> <level>1</level> <task>63</task> <opcode>0</opcode> <keywords>0x8000000000000002</keywords> <timecreated systemtime="2014-03-06T10:01:05.426979800Z"> <eventrecordid>58462</eventrecordid> <correlation> <execution processid="4" threadid="8"> <channel>System</channel> <computer>Parinibbana</computer> <security userid="S-1-5-18"> </security></execution></correlation></timecreated></provider></system> - <eventdata> <data name="BugcheckCode">126</data> <data name="BugcheckParameter1">0xffffffffc0000005</data> <data name="BugcheckParameter2">0xfffff80077ebbb76</data> <data name="BugcheckParameter3">0xffffd00026b5b638</data> <data name="BugcheckParameter4">0xffffd00026b5ae40</data> <data name="SleepInProgress">0</data> <data name="PowerButtonTimestamp">0</data> <data name="BootAppStatus">0</data> </eventdata> </event>
Another frequently occurring error is "LoadPerf" with EventID: 3012 The general-tab says: "The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section."
In the details of the XML-view it says: <event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <system> <provider name="Microsoft-Windows-Kernel-Power" guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}"> <eventid>41</eventid> <version>3</version> <level>1</level> <task>63</task> <opcode>0</opcode> <keywords>0x8000000000000002</keywords> <timecreated systemtime="2014-03-06T10:01:05.426979800Z"> <eventrecordid>58462</eventrecordid> <correlation> <execution processid="4" threadid="8"> <channel>System</channel> <computer>Parinibbana</computer> <security userid="S-1-5-18"> </security></execution></correlation></timecreated></provider></system> - <eventdata> <data name="BugcheckCode">126</data> <data name="BugcheckParameter1">0xffffffffc0000005</data> <data name="BugcheckParameter2">0xfffff80077ebbb76</data> <data name="BugcheckParameter3">0xffffd00026b5b638</data> <data name="BugcheckParameter4">0xffffd00026b5ae40</data> <data name="SleepInProgress">0</data> <data name="PowerButtonTimestamp">0</data> <data name="BootAppStatus">0</data> </eventdata> </event>

Another frequently occurring error is "LoadPerf" with EventID: 3012
The general-tab says: "The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section."
In the details of the XML-view it says: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>3</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000002</Keywords> <TimeCreated SystemTime="2014-03-06T10:01:05.426979800Z" /> <EventRecordID>58462</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Parinibbana</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data Name="BugcheckCode">126</Data> <Data Name="BugcheckParameter1">0xffffffffc0000005</Data> <Data Name="BugcheckParameter2">0xfffff80077ebbb76</Data> <Data Name="BugcheckParameter3">0xffffd00026b5b638</Data> <Data Name="BugcheckParameter4">0xffffd00026b5ae40</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> </EventData> </Event>


In order to get a clearer picture of my system-crashes I downloaded a software called "WhoCrashed", clicked on "Analyse" and the following is the result of its log:

System Information (local) computer name: PARINIBBANA windows version: Windows 8 , 6.2, build: 9200 windows dir: C:\WINDOWS Hardware: SVT1121C5E, Sony Corporation, VAIO CPU: GenuineIntel Intel(R) Core(TM) i7-4610Y CPU @ 1.70GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 4185702400 total VM: 2147352576, free: 1916170240 Crash Dump Analysis Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer.

On Wed 19.03.2014 22:18:28 GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x9F (0x3, 0xFFFFE00008DC4410, 0xFFFFF80289209840, 0xFFFFE0000172C010) Error: DRIVER_POWER_STATE_FAILURE Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. 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 that cannot be identified at this time.

On Wed 19.03.2014 08:12:08 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\031914-5859-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36) Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00000F14880, 0xFFFFF800EDD7E860) Error: DRIVER_POWER_STATE_FAILURE file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. 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 that cannot be identified at this time.

On Sun 16.03.2014 15:16:25 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\031614-7609-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0) Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF802530BD533) Error: IRQL_NOT_LESS_OR_EQUAL 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 that cannot be identified at this time.

On Sun 16.03.2014 15:16:25 GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: nuserver64.sys (NUServer64+0x17C13) Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF802530BD533) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\drivers\nuserver64.sys product: Network USB Server company: Elite Silicon Technology Inc. description: Network USB Server 64bit Device Driver Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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: nuserver64.sys (Network USB Server 64bit Device Driver, Elite Silicon Technology Inc.). Google query: Elite Silicon Technology Inc. IRQL_NOT_LESS_OR_EQUAL

On Thu 06.03.2014 10:00:19 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\030614-7234-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0xADB76) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80077EBBB76, 0xFFFFD00026B5B638, 0xFFFFD00026B5AE40) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 06.03.2014 04:55:47 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\030614-6921-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0) Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF800060AE5D1) Error: IRQL_NOT_LESS_OR_EQUAL 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 that cannot be identified at this time.

On Thu 06.03.2014 03:58:36 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\030614-6015-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x425637) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803D029D637, 0xFFFFD000237F57D8, 0xFFFFD000237F4FE0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 26.02.2014 21:57:39 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\022714-5343-01.dmp This was probably caused by the following module: netwbw02.sys (0xFFFFF8000284FDFC) Bugcheck code: 0xD1 (0x40, 0x2, 0x0, 0xFFFFF8000284FDFC) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\drivers\netwbw02.sys product: Intel Wireless WiFi Link Adapter company: Intel Corporation description: Intel Wireless WiFi Link Driver Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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: netwbw02.sys (Intel Wireless WiFi Link Driver, Intel Corporation). Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

On Tue 25.02.2014 08:27:36 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\022514-7359-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x425637) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8023C840637, 0xFFFFD000397EA7D8, 0xFFFFD000397E9FE0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 26.01.2014 06:29:07 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\012614-6859-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0) Bugcheck code: 0x4E (0x9A, 0x1553B7, 0x6, 0x2) Error: PFN_LIST_CORRUPT 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 the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 21.01.2014 12:42:17 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\012114-6000-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x425637) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80120A2E637, 0xFFFFD00026ECC7D8, 0xFFFFD00026ECBFE0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion
32 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: netwbw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation) nuserver64.sys (Network USB Server 64bit Device Driver, Elite Silicon Technology Inc.) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. <div>End of "WhoCrashed"-Analysis.

For more information I have put the Windows event-viewer
a) application events,
b) system events,
c) Windows Power Shell logs,
as well as my dumbfiles list on my dropbox: https://www.dropbox.com/sh/l840x044kepyrna/aSIqO7PmqC
Please feel free to have a look at them too.
For comments and suggestions I would be very grateful.
Thanks
</div>

Discussion is locked

1 - 30 of 71 Posts
- Collapse + Expand Details
- Collapse -
Clarification Request
Is this a continuation of another post?
by r. proffitt Forum moderator Apr 8, 2014 12:35AM PDT

I don't see where you used the prior advice.
Bob

- Collapse -
Answer
Did you read the conclusion
by Mar 29, 2014 11:55PM PDT

Did you read the conclusion, because it seems pretty clear to me:

Conclusion
32 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites.

- Collapse -
Pls see above
by Parinibbana Mar 30, 2014 10:10AM PDT

Did you read what I wrote above? Quote: "I am running Windows 8.1 and all the current device-drivers, bios-update and Windows-updates are installed."

Any further suggestions?

- Collapse -
Two
by Jimmy Greystone Mar 30, 2014 10:45AM PDT

Two as a matter of fact.

1: Don't rely on Sony's website, Windows Update (never, Ever, EVER take driver updates from Windows Update) or any driver finder type programs. According to the conclusion your wifi driver, from Intel, is causing problems along with some USB server device. Hopefully that makes sense to you, because I haven't the foggiest what that might be. Maybe an external HDD or something. Go to Intel's site and get the latest wireless drivers direct from them same with this Elite Silicon Technologies I've never heard of and figure out what you have that they produce and get the latest drivers for that.

If that doesn't solve it, see option #2.

2: File a warranty claim with Sony, make them fix it, because you've probably got some dodgy hardware. At 3 months you're well within the standard 1-year warranty. That was factored into the final cost of the unit, so you paid for it, may as well use it. If they can't fix it after 3-4 attempts, demand a refund for the full purchase price. When they refuse, take them to small claims court. They won't bother sending anyone to represent the company, you win by default judgment, and now there's a court order for them to cough up the money. Just be sure to include court fees in your remedies and keep in mind you will have to pay taxes on the full amount since the IRS will consider it the same as lottery or gambling winnings. Still, it'll be better than nothing.

- Collapse -
Wifi-driver update
by Parinibbana Mar 30, 2014 12:41PM PDT

To point 1:
a) Thanks. I think you are right. The driver updates that Sony provides are not the latest. I'm just downloading the new Wifi-drivers directly from Intel now.

b)The USB-server device is this: http://www.sharkoon.com/?q=en/content/usb-lanport-400-giga
It's a 4-port USB to Ethernet-hub, which allows me to drive my mouse, keyboard, thumb-drive, ext. HD over my WiFi-router. In this way I don't need to plug anything to my laptop apart from the power-cable.
It seems, that this device is responsible only for one out of all the system-crashes. The latest drivers and firmware are installed already.

I really hope that the Intel-Wifi driver will make a difference.

To point 2:
I am staying abroad, which makes warranty claims much more difficult, since Sony doesn't include international warranty by default. Of course I could send the laptop back to Austria where I bought it and get it repaired by Sony there, but considering shipment- and repair time, I'm in for a month without a laptop, which of course I'd like to avoid unless absolutely necessary.
If it turns out to be a hardware-issue, that's what I will do. If Sony makes any problems, it's good to have your guide from above on how to go about doing things using one's legal rights.
But for now I am not certain whether it's a hardware issue or just a driver-problem. (see above)

Anyways, after installation of the new Wifi-driver I'll keep you posted how it goes and whether there are still system-crashes. Thanks so far.

- Collapse -
Then I guess you're stuck
by Jimmy Greystone Mar 31, 2014 11:17AM PDT

Then I guess you're stuck deciding between shipping the thing back to Australia to be repaired or just sucking it up and getting a new laptop wherever it is you are now.

One thing I would try, however, is just for a day or two, removing the USB to ethernet hub. Since that driver was also fingered by the crash analysis, and it's network related, it's possible that it's sharing the same IRQ as the wifi card and what you're getting is a cascading error. I'll readily admit it's pretty firmly grasping at straws, but you could get lucky and what exactly do you have to lose by trying? If the problems persist you can always put it back and be no worse off than before.

- Collapse -
Trying now w/o USB to ethernet HUB
by Parinibbana Mar 31, 2014 3:20PM PDT

That's exactly what I am doing right now. Thanks 4 the advice.

- Collapse -
On your USB device make sure your
by orlbuckeye Apr 2, 2014 9:32PM PDT

using the correct version of USB. Is the device USB 2.0 or 3.0? Are you plugged the device into a USB 2.0 or 3.0 port? Also why is it a big deal to plug everything into your PC? Think about this you have all those devices plugged into 1 USB port on the PC. I hope your hub has it's own power. I've used those hubs before and it works better when you plug each device into it's own port rather then sharing one port with multiple devices.

- Collapse -
USB-HUB
by Parinibbana Apr 3, 2014 9:30AM PDT

Thanks Orlbuckeye for your suggestions.
To answer your questions: As far as I know one can plug USB 2.0 devices at USB 3.0 ports - no problem. One can also plug USB 3.0 devices at USB 2.0 ports - no problem, but you won't get the full speed that the device could operate at.

The big deal about not plugging everything into a PC is, that the Sony Vaio Tap 11 is no PC!
As an ultra-thin notebook (tablet) it has only a single USB-port. In order to get rid of cables on my workplace, I have chosen not to use even this single USB-port, but to connect my USB-devices to a USB-LAN-HUB ( http://www.sharkoon.com/?q=en/content/usb-lanport-400-giga), which is connected to my WiFi-router. Thereby I get my mouse, external HD etc. to work wirelessly. The USB-LAN-HUB has it's own power source of course.

My latest testing has revealed that the crashes are not caused by the USB-LAN-HUB at all!
Even when it's disconnected, the crashes continue.

For testing purpose I have now turned off my WiFi-router (TP-Link 3020 3G-4G Wireless Router), connecting to the internet over another hotspot. Since then, two days ago, I have no more crashes. I'll continue testing this for another two days and will then use the Wifi-router again, to make sure it's really the source of my frequent system-crashes.

But I would be somewhat surprised to find out that a device that does not even install anything on the local machine, no drivers - no software, can cause such a major impact on the system. It's firmware, however, is up to date.

Does anyone have an explanation how that works?

- Collapse -
Just to be absolutely sure
by Jimmy Greystone Apr 3, 2014 11:38AM PDT

Just to be absolutely sure, don't just disconnect the USB hub, get rid of any associated software for it. It would hardly be the first time a POS driver caused problems.

If that still doesn't do it, you're looking at either shipping the thing back to Australia to be fixed or buying something new where you are now. Or just putting up with the crashing.

- Collapse -
data corruption or clash
by James Denison Apr 21, 2014 4:25AM PDT

probably due to two wifi in the area using the same wifi channel. Check the wifi signals in the area, find a channel that is clear for you to use.

- Collapse -
Answer
The conclusion seems to nail it.
by Forum moderator Mar 30, 2014 1:49AM PDT

But at 3 months time to ask sony for a fix or refund.
Bob

- Collapse -
It can take weeks to get a laptop repaired by service-center
by Parinibbana Mar 30, 2014 10:40AM PDT

Since I was too expecting this to be a driver issue, I was hoping for an update to be released which would fix this issue sooner or later. Therefore I did not return the laptop to Sony, which often can take weeks until you get it back.

But all driver-updates that were released so far, including Wifi-drivers and Bios-update, have not made any difference to my system-crashes.

That's why I am now trying to seek help from people more knowledgeable than myself, hoping that someone has an idea of how to fix that issue.

- Collapse -
Just where did you get these
by itsdigger Mar 30, 2014 10:52AM PDT

driver updates from? Windows is notorious for giving BUM Driver Updates.
Get the updates from each of the mfgs. and than see if you have these crashes.
The only thing you want Windows to update is Windows.

Digger

- Collapse -
Drivers from the Sony-update page
by Parinibbana Mar 30, 2014 12:44PM PDT

Got them from the Sony-update page, as well as by their update-tool.
However, I just realised that there is a much newer version of my Wifi-driver available directly on the Intel website.

Just downloading it and will try it out.

Will keep you posted about the results. Thanks so far.

- Collapse -
Drivers from where? And besides.
by r. proffitt Forum moderator Mar 30, 2014 12:06PM PDT

if it is that new and crashed that early, I would be in the face of the seller, maker and such. If they delay too long I move to returning it.
Bob

- Collapse -
Answer
Reading all this
by Mar 30, 2014 11:47PM PDT

Just read all suggestions and answers. It doesn't seem you have reached any conclusion yet. Can't you just take a backup and format the windows. Although the crash issue seems familiar to graphics dump or RAM memory dump errors, that your hardware are unable to adjust for the OS.

- Collapse -
Wifi updated - another crash a few hours later
by Parinibbana Mar 31, 2014 9:39AM PDT

I think for now I'll take a more gradual approach, but if really nothing helps that's what I will do. Thanks for the advice Cisshadab.

Yesterday I have updated the Intel Wifi-drivers, a few hours later I had another crash.
Now I have disconnected the 4-port USB to ethernet HUB (http://www.sharkoon.com/?q=en/content/usb-lanport-400-giga) from my router. Let's see whether it makes a difference.

- Collapse -
Fresh installation of Windows
by Parinibbana Mar 31, 2014 11:16PM PDT

I guess that's what I will do.

I'll create a system-image first, so that I can go back to the present state afterwards in case it is really a hardware-issue. Otherwise I'd have to re-install all the programs manually, which would take quite some time.

- Collapse -
Answer
Now that we know something isn't stock. Shark thing?
by Forum moderator Mar 31, 2014 10:04AM PDT

Win 8.1 has been one of the most stable systems Ms has produced (at least IMO) and I've run it on loads of machines (all different).

I suspect your hardware might be faulty - if not restore the system to the "Factory" state and try again.

That is, don't add the shark software.
Bob

- Collapse -
Answer
Another crash - this time w/o HUB - relationship to surfing?
by Mar 31, 2014 3:56PM PDT

Just had another crash - this time without the USB to LAN-HUB being connected to the router.

From the last few crashes I noticed smthg. interesting: All of them happened when the browser (Chrome) tried to load a website. Which site didn't matter, it even happened with this CNET-forum, as well as other highly reliable sites.

Therefore the following scenarios come to mind:
1. a problem with my wifi-router (which provides the internet connection)
2. a problem with the wifi-drivers of the laptop (but they are up to date now)
3. a problem with the browser

What do you guys think?

- Collapse -
Worth a try
by Jimmy Greystone Mar 31, 2014 11:53PM PDT

Worth a try at least, to download Firefox and see if that helps. One of my thoughts is that the custom version of Flash bundled with Chrome might be problematic on your system. You could also download memtest86+ and let that run overnight.

But if you're getting this error with an absolutely stock configuration, hardware and software, I'm still inclined to think hardware failure.

- Collapse -
Memtest86+; Firefox; No more dumpfiles
by Parinibbana Apr 5, 2014 11:22PM PDT

I ran memtest86+ yesterday night, but it didn't produce any errors.
I'm using Firefox now - had it installed anyways - just didn't use it as my regular browser. We'll see what it brings.

Today I checked the dumpfiles of my machine. It seems that I had frequent crashes ever since I got the computer 4 months ago, from the first day onwards. I already forgot about that, that's how used I got to it. Wink

I am not sure however, whether it is still the same error as back then. At that time I usually had a blue screen and after the system-shutdown I had a dumpfile.
But nowadays usually the screen gets black, unresponsive and I need to shut down by long-pressing the Power-button. After that there will be no dumpfile.

- Collapse -
And did you
by Jimmy Greystone Apr 5, 2014 11:29PM PDT

And did you completely remove all traces of the USB hub device and test that out for a couple of days?

- Collapse -
Remove all traces of the USB hub
by Parinibbana Apr 6, 2014 12:10PM PDT

Yes, I uninstalled the software and afterwards manually removed remaining registry-entries.

- Collapse -
Then you have two options
by Jimmy Greystone Apr 7, 2014 10:25AM PDT

Then you have two options as I see it.

You can try reloading the software to factory spec and just using it with the absolute bare bones level of software you need to manage for 1-2 days. The fewer programs you install from factory condition the better. If the problems go away, add programs back one at a time, one every 2-3 days so you have time to see if the problem shows up after installing some program. If you can pin it on a specific program, great, you can find an alternative, look for an update or just dump it entirely. If you get all your software reinstalled and the problem doesn't come back, even better. If it comes back before you do much of anything, you've pretty well established it's a hardware issue.

So if you pin it down to a hardware issue, your choices are to either live with it, buy a new computer where you're currently residing or ship the thing back to where it can be serviced under warranty. Or you could potentially sell it on eBay or something, though unless you explicitly mentioned that it had a hardware issue it would be rather unethical, potentially illegal depending on local laws.

Looks like I am in good company after skimming a few of the later posts in this thread. If the factory setup doesn't solve the issue, it's almost certainly hardware related.

- Collapse -
Answer
Windows 8 forum: Frequent system-crashes in Windows 8.1 - Wh
by Apr 1, 2014 6:56AM PDT

update everything , and try again....

seems like you need critical upgrades

- Collapse -
(NT) I doubt it.
by Kees_B Forum moderator Apr 6, 2014 1:21AM PDT
- Collapse -
Answer
Latest Dumpfile and Dumpfile summary
by Apr 6, 2014 6:04PM PDT

Dear Friends,

Just had another system-crash. This time it was preceded by a blue-screen and a dumpfile was created. How lucky we are. I uploaded it into the folder 2014-04-07 of my dropbox-link, in case anyone would like to have a look at it: https://www.dropbox.com/sh/l840x044kepyrna/aSIqO7PmqC

I also put a summary of my previous dumpfiles (List of Dumpfiles over long period.jpg) into the same folder, which gives us a good overview of the long-term crash-patterns.


WhoCrashed's Analysis came up with the following report:

On Mon 07.04.2014 07:26:56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040714-11468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0000FB2D320, 0xFFFFF802C3CEB840, 0xFFFFE000095054B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 that cannot be identified at this time.

On Mon 07.04.2014 07:26:56 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0000FB2D320, 0xFFFFF802C3CEB840, 0xFFFFE000095054B0)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 that cannot be identified at this time.


Again the error occurred while browsing the web. This time, however, I used Firefox. So now we can also dismiss the Google-Chrome theory from above.

One question: What is this ntoskrnl.exe anyways, in which 90 % of my crashs happen? Can't it simply be replaced by another version of this file?

I need to add a big THANK YOU for your continuous support and suggestions so far. Even though we still haven't solved the issue (yet?), I do really appreciate your help and efforts.

- Collapse -
Re: NTOS kernel
by Kees_B Forum moderator Apr 6, 2014 6:26PM PDT
https://en.wikipedia.org/wiki/Ntoskrnl tells what it is: the innermost part of the OS. And so is ntkrnlmp.

http://www.sevenforums.com/bsod-help-support/26960-ntkrnlmp-exe-related-bsod.html has an example where removing and replacing the laptop battery seems to solve the issue. Amazing, if it's true (never really sure, until it stays the same for a few days or weeks).

What I should do is in line with suggestions above:
1. Go back to factory conditions (both hardware and OS)
2. If that doesn't help, use the warranty to have the laptop repaired or replaced. If that takes weeks, so be it.

Kees
Back to Windows 8 forum

CNET Forums

Operating Systems
Software
Electronics & Gadgets
Hardware
Tablets & Mobile Devices
General Help
Brand Forums
Roadshow Autos
Off Topic

Other Forums

Forum Info