brand new np8265 bsod advice?

received a brand new sager np 8265 on friday from pro-star. trying to get the os going has been a nightmare.. Does anyone have any experience or clues as to how i can solve my problem??? I started out on friday morning installing windows 8.1. installs fine... at first. do my first boot and it begins. loads in 5 minutes into running windows update. bsod. load it back up bsod trying to log in. think maybe the disk i have could have been corrupted so i burned a new copy. load it up. boots fine do windows update and complete. everything is good. nvidia driver through windows update isn't the newest version (332.21) so i run it update. bsod once a friggin again. BTW 8.1 bsod sucks it gives zero information...

well it does give information but nothing of value. the only information it gave on each bsod was a different message everytime... Roll back the driver and decide to leave it as the "old" driver. and proceed to just browse the web etc... 20 minutes in bsod. and this time continual bsod on log in once again. run a roll back. yadda yadda yadda

Reinstall windows 8.1 once again! this time do not let windows update run. yeah thats right using my noggin. bring out the good ole drivers disk provided... load up any driver that is showing up as needing done in device manager.. get those installed.......... you guess it bsod.

reinstall windows yet again.. this time i figure ill install a driver. set a restore point do what i can/let it sit after each driver install. everything goes good until i get to the intel drivers... it seems the intel drivers are causing my bsods. so i do not install them after the system restore. all drivers are now installed from the disk with the exception of the intel mei, raid and another driver...) no bsod. or so i thought.

Alright so I have given up on windows 8.1 now lets do windows 7 ole faithful... here we go. grab a disk install and run... oh boy windows 7 caught almost none of the drivers to install including wifi and ethernet........ this will be fun. (oh and both disks that came with the laptop show "unsupported os" so i use the sager website to download the wlan driver. get it on the network and run windows update. woohoo got almost all of the drivers. create a restore point. and continue. download all the drivers i can. run into a 4 hour ordeal having issues getting th edriver for the sound blaster x-fi 3mb installed (turns out all drivers on sagers website show only support for windows 8 and 8.1.)

finally get the sound card going... download iobit to try and snag the rest of the drivers.. bsod.. UGHHH (this one was easy to figure out though.. iobit's "driver" for the bison camera is faulty) YAY one bsod issue with windows 7 so far!!! but wait theres more!

get windows 7 going as smooth as its gonna let me. I am still showing one driver not installed. i have tried everything and cannot find it!! universal serial bus usb controller (device 20)

alright so now i have been working on windows 8.1 starting at 11am on friday. worked continually until about 4 am saturday morning... and then after some snooze worked on it all night and finally around midnight started windows 7 install...

sunday rolls around get on the computer start messing around. bsod.......... didn't do anyhting... well now i am stuck at a bsod about once every hour to hour and a half in which the computer is used... sitting idle doesn't seem to cause anything. windows 7 has full information of the bsod though so after bsod number 5 today i have set it so that it wont automatically restart after the next one and ill get some codes to research... until then do any of you guys know what it could be?

side note! anyone else with an np8265 notice how crappy their mic sounds? mine sounds like im in a tunnel and its super quiet... any idea on it? i've tinkered with the noise cancellation mic boost levels and everything i can think of... (my old sager actually has a really good mic quality for build in. np5135. if the mic on the 8265 is just crappy is it possible to umm swap the mics???

 

hi
download who crashed which you can find in my sig below and post all the crash dump reports on here.

im guessing all clevo models are the same so drivers have to be loaded in a certain order or they can conflict.

you could also remove the base to see if anything is lose like the ram sticks due to transit.

 

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 1/13/2014 8:24:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011314-26551-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800F00C3E4)
Bugcheck code: 0xD1 (0xFFC00010, 0x2, 0x0, 0xFFFFF8800F00C3E4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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.
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 1/13/2014 8:24:43 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xC3E4)
Bugcheck code: 0xD1 (0xFFC00010, 0x2, 0x0, 0xFFFFF8800F00C3E4)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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.
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 1/13/2014 6:22:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011314-37783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3D (0xFFFFF80000B9BFA0, 0x0, 0x0, 0xFFFFF8000309D53C)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
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 appears very infrequently.
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 1/13/2014 6:20:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011314-40310-01.dmp
This was probably caused by the following module: rtsuvc.sys (rtsuvc+0x17CC5)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800C8DFCC5, 0xFFFFF880033770C8, 0xFFFFF88003376920)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\rtsuvc.sys
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.
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: rtsuvc.sys .
Google query: rtsuvc.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Mon 1/13/2014 5:50:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011214-45645-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF00003DF43E0, 0x2, 0x1, 0xFFFFF800030E207B)
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 Mon 1/13/2014 5:48:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011214-43929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 Mon 1/13/2014 5:11:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011214-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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
--------------------------------------------------------------------------------

7 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:

rtsuvc.sys

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

im no expert when it comes to reading the dumps but looking at them most are operating system errors and direcx graphics driver errors.
it might be a good idea to email these dumps to prostar tech support as they are the experts and would be able to advise what could be causing them.

these are the order drivers should be loaded. is this the order you loaded them in.

 

yes those are the drivers i installed.. If i recall the first 3 are my big concern ones.. the others I am pretty sure are from where I was trying to update the webcam driver..

btw you wouldn't happen to know anything about the mic onthis thing would you?

 

not sure about the mic as ive never used mine either so dont know if its a standard clevo fit or varies between models.

 

Generally the camera is by Bison.

Your dumps reflect varying causalities; a trend in BSODs containing different error messages tends to point to faulty memory (not always, but very possible). The issue could also be the hard drive.

Since they vary so widely and you seem to have installed your drivers correctly, it seems less likely to be software related.

 

You could try running off one stick of ram.

 

I ran memtest86 last night and it showed my ram was all good? could the ram still be faulty?

I actually redid everything yet again on monday night. it went the entire day without bsod. and then last night bsod'd twice. Jeff at prostar has my crash dumps atm. hopefully he can get me lined out :/ its kind of frustrating having this sort of issue with a brand new computer. especially after that much is paid for it.

 

2 bsod's today :'( attached is a dump of all crashes since redoing it

https://www.dropbox.com/s/m2fvrymqp2rc0ed/bsod.zip

 

This machine might need to go back to the reseller.
Personally, I wouldn't trust it with all those BSOD's. I never had BSOD's on any of my laptops and driver issues are just a lame excuse for this.
- you tried 2 different OS (win7 and win8)
- you did many reinstalls
- you tried different drivers
- you checked the RAM for errors
- you checked the HDD for errors

...and you still get BSOD's.

Solution: contact your reseller and send them the machine back. Tell them you want a new one (make sure you note the old one's serial number) and this should be the end of your ordeal.
Its just outrageous, you pay a lot of cash for some high performance system and you get a nerveous breakdown from instability. Not just instability, but plain unusability from blue screens.
I hope all goes well from here on!! (cant get any worse, thats for sure!)

 

bob1man is spot on. this amount of errors isnt right especially for a new machine.
i had the same for 19 days with alienware and then got a refund and bought a clevo.

 

I had a similar experience with a laptop - this is 99.9% a bad RAM stick. Contact your reseller.

 

Memory test applications are not bullet proof and memory is a common cause of BSODs. Whether this is hardware related at all or not, I agree in that your reseller should bite the bullet and help you out.

 

ProStar you are the reseller

kadam5 have you tried running the system with just one stick of RAM as Meaker suggested. You can also try different RAM slots to make sure its not the motherboard either.

 

When I had the issue, I ran RAM tests for a full week, and nothing. I gave it to techs at the company I bought it from, and lo and behold, it was still a bad RAM stick, so I kinda doubt these tests' reliability.

 

alright so it has 4 sticks of 4 gigs of ram. do i take all of them out except for 1 stick? or do it 2 at a time?

btw nice catch there hutsady

I guess the second question in the whole thing is... what do i do to access the 2 that aren't "user upgrade-able?" i think sager said something about it being under the computer cover??

 

there are two sticks under the keyboard and 2 in the base.

 

>_< I guess ill try removing the 2 from under the base first... it says those are the primary. This really is gunna suck if i have to send it back though. I bought it on christmas eve. and because of holidays, order fulfillment process, weekends and a weather delay. it took 2 almost 3 weeks to arrive. Now it'll take another 2 weeks because of course it'll have to be sent both ways via ground and I'm in the midwest, which is 4-5 days shipping.

 

If you can find the bad stick of RAM you can ask for a cross shipment where you can just send in the bad stick and continue to use the computer with 12GB of RAM in the mean time.

 

is there any programs to easily strain test ram? I'm going to have to pull the computer apart to get them all out.

Also is there a guide anywhere that shows how to access the 2 under the keyboard? I'm pretty proficient with working on computers. Just want to sort of know where exactly to pull apart etc and knowing where the ribbon cables are so I don't mess them up.

 

The way least likely to scratch is to push a screwdriver through the hole in the pcb next to the gpu fan and push the cover above the keyboard off (make sure the screen is open).

 

WAIT does the top speaker grill just pop off and remove 2 screws to get to the keyboard? heres the image i found
http://www.notebookcheck.net/fileadmin/Notebooks/Schenker/W503/innen1.jpg

and i think i found the answer to my question.

 

That way can scratch the casing. I recommend my way unless you have plastic implements.

 

I see your way as well now. Stumbled across the exact details on another post about disabling the backlight on the "gaming" tier of this computer... pretty amazing how easily it is to access everything on this laptop.

 

That's a big benefit of these models yes, very refreshing

 

well i've got 2 of them out now. time to wait and see if i bsod. on the flip side though i actually ran that windows update for drivers AND my mic is perfect now!

 

Let us know how you get on, glad the MIC is working.

 

took the 2 ram sticks out of the bottom out. and not one crash since then. here in a bit i think i am going to move them from the top to bottom and see if i get any crashes that way... and after that i guess ill swap them out if all goes well.

 

moved the ram sticks from top to bottom and left them in for about 4 days and zero BSOD.... now I've got the 2 i had taken out in and last night i swapped the out the 2 ram sticks for the one's i originally. So far no bsod with that. I'm going to give it a few days of that and then slowly start putting the ram back in...

 

Lets hope the ram is faulty, rather than the motheraboard.
There is definetely something wrong, its gonna be either one of the two.

 

It could be a timing issue having all 4 in.

 

If you put the RAM back in and you get BSOD, take that stick back out and move one that has been working fine over to that same slot to see what happens.

 

OK Meaker you're thoughts sound 120% the issue..... Ok so update. I swapped out sticks swapped sections and never any bsod's. BUT as soon as i put all 4 back in... two bsod back to back within an hour of it being turned on.... so next question.. how do i fix??? I REALLY don't want to send it back to pro-star/sager and be without a computer for 2 weeks...

 

Best thing to do now is to contact your reseller to ask them what your options are.

 

here is my ram timings...