Originally Posted by elephantnut Sometimes two might happen immediately after one another, and then Windows says it can't boot and system restores. :/ When you get "Windows can't boot" - does Still trying to resolve - ugh!Microsoft Windows 10 Home (64-bit)Intel Core i5-4690K 3.5GHz Quad-Core ProcessorAsus MAXIMUS VII GENE Micro ATX LGA1150 MotherboardKingston HyperX Fury Blue 8GB (2 x 4GB) DDR3-1600 MemoryCrucial You running 361.75 nvidia driver? I have had all of these things installed and running on both computers when they crashed. http://digitalsurgeon.net/windows-7/windows-7-bsod-8e-win32k-sys.html
Process ID: 1664 Start Time: 01d005064af4e32c Termination Time: 3 Application Path: C:\Users\Public\IForm\pvbridge.exe Report Id: 17d155d0-70fa-11e4-b516-f6355f53ce6f Error: (11/20/2014 04:09:14 PM) (Source: Application Hang) (User: ) Description: The program pvbridge.exe version 126.96.36.199 so far i think it happen randomly as long as sth is connected to the front usb ports, which is kind of lame and annoying, seeing things get connected there a now i restored successfully. MiniToolBox by Farbar Version: 30-11-2014 Ran by amswickard (administrator) on 10-12-2014 at 16:12:01 Running from "C:\Users\amswickard\Downloads" Microsoft Windows 7 Home Premium (X64) Boot Mode: Normal *************************************************************************** ========================= Event log https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-win32ksys-systemserviceexception/3665e85b-03a4-4066-ba20-42d6e1f52d05
Another question: The driver-verifier should not crash system if everything is fine or working ? Go to the even viewer and take note of yellow triangles and Red Xs. Now I'm getting the SYSTEM_SERVICE_EXCEPTION blue screen instead.
Since we've encountered situations where crashes do not occur under Driver Verifier, I adopted the 36 hour rule. BUGCHECK_STR: 0x7E FAILURE_BUCKET_ID: X64_0x7E_athrx+f2061 BiosReleaseDate = 04/08/2011 SystemManufacturer = System manufacturer SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` My System Specs System Manufacturer/Model Number Self Built OS Windows 7 Home Premium 64bit The memory could not be %s. What does the Blue Screen say when you run Driver Verifier? __________________ John Carrona, Microsoft MVP - Windows Expert - Consumer Driver Reference Table ` ` BSOD Index 02-04-2011, 12:28
May try reinstalling the updates. Then, restart your computer, and BEFORE the Windows Logo shows, access your BIOS (usually through F2). Try the following: A. https://forums.techguy.org/threads/solved-win32k-sys-bsod.1129624/ I suggest to do the same if you have this problem.
Windows 7: Frequent BSOD mostly with STOP code 3B and win32k.sys Page 1 of 3 1 23 > 22 Jun 2011 #1 fslateef Windows 7 Professional x64 (Dell OEM but Ive been on 50/50 before and have never had this problem because of that. Also for testing purposes disconnect all external devices except keyboard, mouse and monitor Please post back when you have done this and also include in your post please - the make Screen-shot attached. -- Now first time boot after full 8GB RAM memtest gave me BSOD; attaching log/minidump.
I will also try to post dump again tonight according to what forum rules says.
or read our Welcome Guide to learn how to use this site. Now I'm getting the SYSTEM_SERVICE_EXCEPTION blue screen instead. Error: (12/08/2014 06:54:59 PM) (Source: EventLog) (User: ) Description: The previous system shutdown at 6:27:55 PM on 12/8/2014 was unexpected.
for me it works... http://digitalsurgeon.net/windows-7/win32k-sys-bsod-0x50-windows-7.html BUGCHECK_STR: 0x3B PROCESS_NAME: sidebar.exe FAILURE_BUCKET_ID: X64_0x3B_win32k+8490b BiosReleaseDate = 04/08/2011 SystemManufacturer = System manufacturer SystemProductName = System Product Name ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` My System Specs System Manufacturer/Model Number Self Built OS Windows 7 Home Also, many security professionals have released source code that shows how to hack into the unpatched version of windows. The detailed error message is provided below.
The memory could not be %s. Thread Status: Not open for further replies. anyway, will post if another bsod comes my way and i manage to get any dumps. this content After the BSODs kept happening, I ran Memtest86+ for 12 hours (4 passes, 0 errors).
Show Ignored Content Page 1 of 2 1 2 Next > As Seen On Welcome to Tech Support Guy! This makes me feel like the update has caused the issue. Did you go to the Evenet Viewr and if so what did you find in ways of yellow triangles and red x's?
thank you . Worth a read, http://www.sevenforums.com/bsod-help-support/328401-win32k-sys-ntoskrnl-exe-0x3b-bsod.html. Whilst I was following these instructions I experienced 8 BSOD crashes and now have started up in safe mode with networking. Sorry about that.
Please search Google/Bing for the driver if additional information is needed. I would like you to run a system file check to make sure there are no corrupted Windows files SFC /SCANNOW Command - System File Checker BSOD BUGCHECK SUMMARY Code: Built The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way. have a peek at these guys Does seem to implicate the updates though.
In case you want to give it a try, install an old driver like 358.91. May try reinstalling the updates.