BSODs and such with NP9150

Hey guys.. I'm having a terrible time with my new 9150!

First off, I began to notice that the keyboard was missing keystrokes (The keyboard would frequently not register pressed keys), so I put in an RMA and got a replacement keyboard. But after installing it, I soon discovered that I still had frequently missed keystrokes.

Next, I've begun to have BSODs when coming out of hibernation/sleep or being on overnight.
Error:
Stop 0x0000007e (0xFFFFFFFFC0000005, 0x0000000000000000, 0xFFFFF880037A7988, 0XFFFFF880037A71E0)

It was a bear reinstalling and reconfiguring all of my programs on this PC and I really don't want to do it again, but I also don't want to be stuck with a lemon PC outside of its warranty..
I'm not sure where to go from here.. Also, for some strange reason my screen just flashed black and came back. What gives?!?!?!?!?!

 

download who crashed for my sig below and post the dump report for us. this give much more info than the onboard windows report.

ive noticed missing keys but strangely enough only after a gaming session and it doesnt last that long.

ive never used hibernation as its the first thing i delete on a new laptop. and i think ive only used sleep once so cant advise on that.
only thing i can think about a bsod overnight could be temperatures but if its a new lappy then it shouldnt be that. whats your ambient room temperature and also your cpu/gpu temps. software in same sig below to monitor temps.

why was it a pain loading and configuring your programs?
did you get the drivers cd with your lappy and was everything pre loaded or have you done a clean system install. drivers have to be loaded in the order they are on the disc or there can be conflicts.

the more info we have it will be easier for people to give advise.

edit. google only shows your 4 posts on different forums so thats no help

 

Hahahaha yes, I've been looking around furiously.

I actually have who crashed already, so here is the dump analysis:

Code:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 4/21/2013 8:22:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042113-9516-01.dmp
This was probably caused by the following module: netwsw00.sys (Netwsw00+0x1F93FD)
Bugcheck code: 0xDEADDEAD (0xF010012, 0x1A700AC, 0x12BC0000, 0x0)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\netwsw00.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: netwsw00.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation MANUALLY_INITIATED_CRASH1



On Sun 4/21/2013 8:22:53 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netwsw00.sys (Netwsw00+0x1F93FD)
Bugcheck code: 0xDEADDEAD (0xF010012, 0x1A700AC, 0x12BC0000, 0x0)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\netwsw00.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: netwsw00.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation MANUALLY_INITIATED_CRASH1




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. A third party driver has 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:

netwsw00.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)

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.

I don't think it's the temps, I've got good thermal paste, I keep an eye on them and leave it on a notebook cooler when on for long periods. CoreTemp also displays normal readings..
It was a bear setting things up because I've go many customized programs that I use regularly and I had to go through, install them all and then reconfigure them to my settings. (This keyboard is driving me NUTS right now!!)

I saw the dump report, so I uninstalled that network driver and installed the latest from Intel's site. So far no BSOD, but only time will tell if it's fixed.

 

never seen a manually initiated crash befor but its pointing to your wifi link adapter and its driver as the culprit.

 

Yea, I updated the driver.. So far no BSOD, but like I said only time will tell.
Also got an e-mail back from my reseller saying that they could send me another keyboard.. but I'm just praying this problem goes away..

 

Actually, I just received another BSOD. Here is the dump...

Code:

On Mon 4/22/2013 4:20:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042213-8424-01.dmp
This was probably caused by the following module: hdaudbus.sys (0xFFFFF88007F5896A)
Bugcheck code: 0x50 (0xFFFFF8802354C008, 0x0, 0xFFFFF88007F5896A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 4/22/2013 4:20:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hdaudbus.sys (HDAudBus+0x196A)
Bugcheck code: 0x50 (0xFFFFF8802354C008, 0x0, 0xFFFFF88007F5896A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I don't understand!

 

now thats audio drivers.

with these clevo's the drivers have to be loaded in a certain order or they could conflict. guessing thats what could be happening here.
have you got the original driver cd that came with the lappy to see which order they are in on the disc.

 

Could actually be bad memory. Bad modules will cause differing BSODs sometimes. Might wanna run MemTest on them - or test one module at a time by physically removing them to see if you can recreate the problem (physically removing them and testing one stick at a time is a more foolproof test method, as much as I like MemTest86+).

 

Seems like it happens when coming back from sleep/hibernate.. So would that more likely indicate bad memory?

And I'm currently updating the audio driver WhoCrash indicated.

$2500 laptop has been more stress than anything... super discouraging...

 

Doubtfully, but faulty memory causes all sorts of issues. If it's really driver related, usually the ACPI driver is the culprit when the rhyme/reason is from waking it up.

Also, WhoCrashed is helpful, but I think the Windows debugger tool might give you more info.

 

Updated my audio driver and tested my RAM overnight with no errors.
I'll keep updating..

 

Try updating your chipset driver as well. A tedious but perhaps definitive way to narrow it down to a particular driver is to simply uninstall one by one and try recreating the BSOD. Once you've found it, then you can reinstall the other drivers and look for an alternate driver for the problematic device driver (I've said driver so many times the word is losing meaning).

 

Thanks for the continued help Prostar!
So far I haven't had any BSOD after updating my HD Audio driver, which is comforting that it's not a rampant thing. I'll keep you posted

 

Nice! It wouldn't be the first time an audio driver caused it. I see similar issues posted on reddit, and it's usually either the audio driver, or the wireless NIC driver.

 

I have the same problem with the keyboard,keys not registering when pressed. Usually is a problem after I start the computer, but after it's been running for a while it seems to get better. Very strange. I'm not happy with it but have to deal as I don't want to go two weeks without a computer.

 

Aaaaaaaaaaaamen to that two weeks with no PC. Impossible for me!!
I'll just keep getting the deserved replacements from Sager until they do something legitimate about it

 

Sounds like something is wrong with the key matrix and the heat from the system (in an odd turn of events) is resolving it on a temporary basis. See if they can ship you a new keyboard. But if it just so happens to be the keyboard controller, that's board related and you will need to ship it to them under those circumstances.

 

I'm going to be getting my second keyboard replacement.. do you think this could also be the keyboard controller..?

 

It could be. I replaced a keyboard on an HP because of all the abuse it had taken; the user said specific keys wouldn't respond. I tested the replacement and same issue; uninstalled the Windows driver and rebooted, same problem. Shut her down, played with the cable, tried again: Success! ... for about 5 minutes. Turned out there was liquid damage, which was most likely the cause.

So if a brand new replacement didn't work, then yeah it's possible. Let's hope not though.