New
#1
Help New Skylake build getting random bosd after waking up from sleep
Hey everyone,
just sign in only to ask you guys about my problems, i have been searching for answer almost 2 day in row but no good result.
Here is the problem
I bought about month ago , new CPU , RAM , and MOBO,
CPU : i7 SKylake 6700
MOBO : Msi - Gaming Pro z170a
Ram : Crossair vengeance 2 x 8 gb
After build into my case , i installed windows 10 64 bit then followed with installing nvidia drivers, and Mobo drivers (downloaded lastest from MSI web). the system went well no BOSD no error almost 2-3 hours.
after couple hour browsing and playing games , i put my computer sleep but not to shut it.
Then after came back, and quit from sleep mode i get BOSD with some error. So after my computer restarted i try to put my computer to sleep and wake it up. Then as i thought i got some BOSD again with different error. i did it a couple time and some time it took about 5-10 minutes before getting BOSD.
i get frustrated , i formatted windows 10 again ( clean install ) then only install my NVIDIA drivers and went to sleep mode and waking it. It still give me BOSD.
In this momment i dont know what to do again , the only option is your helps , anyone of you have same problems as me please share your method to solve this.
Im really sick of this , i am affraid either my new MOBO or CPU is broken.if it so i will return it asap
FYI
1. i did memtest86 5 hours and no eror found in my ram
2. i did SSD test and my ssd still good and healthy
3. i have formatted my windows 10 like a couple times like 10 times with different file OS (avoid my OS corrupted) in other machine and still not solve.
4. I also took away my VGA and using integrated graphics from my mobo and then install windows 10 again , but the result is still the same
In conclusion
1. My VGA is nothing to do with this issues
2. HDD , RAM , PSU also works well
3. i thinks either my ram ( even without error in memtest86) is bad
4. Or lastly either my new mobo or cpu is bad
really need your help guys!!
any suggestions would be appreciated,
sorry my English is bad
this is my dump files
Attachment 52952
this is from whocrashed
this is just a copule BOSD i got from the last windows 10 i used, as i mention i did like 10 times clean install to try sleep mode and it got a lot of random BOSD, sometimes it is new and different with the one i have from the latest.
System Information (local)
Computer name: DESKTOP-55I5GNJ
Windows version: Windows 10 , 10.0, build: 10240
Windows dir: C:\Windows
Hardware: MS-7984, MSI, Z170A GAMING PRO (MS-7984)
CPU: GenuineIntel Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8548741120 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 12/11/2015 4:43:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121015-4093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x1A (0x402, 0xFFFFC0019208A018, 0x8000000193BD1880, 0xFFFBC0019208A018)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Fri 12/11/2015 4:43:10 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1BEC19)
Bugcheck code: 0x1A (0x402, 0xFFFFC0019208A018, 0x8000000193BD1880, 0xFFFBC0019208A018)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 359.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 359.06
Bug check description: This indicates that a severe memory management error occurred.
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation MEMORY_MANAGEMENT
On Fri 12/11/2015 4:35:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121015-4640-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0x8F060)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF961DE48F060, 0xFFFFD000234B8E50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 12/11/2015 4:20:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121015-4390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8032BD64166, 0xFFFFE000F0808840, 0x7FFFC001C0A14180)
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 Fri 12/11/2015 3:47:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121015-3625-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x236E9F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000094, 0xFFFFF801F3776E9F, 0xFFFFD00180296D48, 0xFFFFD00180296560)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 359.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 359.06
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Fri 12/11/2015 3:33:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121015-4062-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x3F273)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF961B5BCF273, 0xFFFFD000223280F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 12/11/2015 3:08:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121015-6859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x1A (0x5002, 0xFFFFF79940000000, 0x3631, 0x1003634FFFFFFE)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.
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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 359.06 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
Quote