BSOD: win32k.sys error

I have recently been experiencing system crashes/freezes again. BSOD says that win32k.sys has an error. I did experience them a few months back, but the crashes seem to have subsided since then, until now. I noticed that the crashes/freezes happen when I startup my laptop/wake up from sleep, use adobe premiere pro/google chrome (before, I experience crashes while using visual studio), and when I plug in/unplug my laptop charger. Also, the network connections icon in the taskbar sometimes reports that there is no internet connection even when there is, and I can't turn the wi-fi on/off (button is greyed out) from pressing Fn+F3 (i have an acer aspire 4750g laptop).

Here are system specs:
Windows 7 Home Premium x64
Original installed OS on the system
OEM

Hardware is 4 months old
OS is also 4 months old

i can supply any additional information that you may require. Please and thank you!

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

im sorry, but when I ran the BSOD Dump & System File Collection app that was posted here:

https://www.sevenforums.com/crashes-d...tructions.html

the dmp file in my \Windows\Minidump folder was deleted. My system is already set to making dmp files on crashes. I'm just following the posting instructions for BSOD problems. i already have my attachments in the previous post.

second, i am not overclocking.

third, i uploaded the msinfo you requested. thank you

Firepenguin said:

im sorry, but when I ran the BSOD Dump & System File Collection app that was posted here:

https://www.sevenforums.com/crashes-d...tructions.html

the dmp file in my \Windows\Minidump folder was deleted. My system is already set to making dmp files on crashes. I'm just following the posting instructions for BSOD problems. i already have my attachments in the previous post.

second, i am not overclocking.

third, i uploaded the msinfo you requested. thank you

The only thing in the upload is the msinfo file. We need to wait for the next BSOD. If you are running some sort of registry clean please stop because they delete the DMP files.

You can also upload the event viewer logs in the mean time so we can get the jump on this

Please provide us with your Event Viewer administrative logs by following these steps:


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

BTW it appears you have Avast and Avg installed and running. Not a good idea. I would remove both and replace with MSE

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide


Microsoft Security Essentials - Free Antivirus for Windows


http://files.avast.com/files/eng/aswclear5.exe

For the Windows_NT6_BSOD_jcgriff2 and perfmon file, please refer to my ORIGINAL post in this thread (both files are found on the "My Attachments.rar" attachment to the post).

No, I am not running any registry clean up program.

For the error viewer log, i have uploaded it in this post.

With regards to the antivirus programs, alright, i'll try MSE, but maybe after the potential source of this problem is found, or if it comes to a point where it really is needed to remove AVG and Avast from my laptop. Thank you :)

Ok the event viewer log had literally thousands of disk related errors. Both IDE controller, and IDE HD errors.

It also had hundreds of AVG related freezes.


I would remove the malware apps (AVG, Avast) and run a chkdsk on all the IDE drives.

We still need the DMPS

Disk Check

ok then, i'll remove the antivirus.

i'm just a bit confused, isn't the dmp file already included in the "Windows_NT6_BSOD_jcgriff2" file?

because when i BSOD'd, i immediately went to the windows/minidump folder and i found one dmp file there. following the instructions posted in this forum, i ran the BSOD Dump & System File Collection app, then the perfmon /report. I went back to the windows/minidump folder, and the one dmp file wasn't there anymore.

Firepenguin said:

ok then, i'll remove the antivirus.

i'm just a bit confused, isn't the dmp file already included in the "Windows_NT6_BSOD_jcgriff2" file?

because when i BSOD'd, i immediately went to the windows/minidump folder and i found one dmp file there. following the instructions posted in this forum, i ran the BSOD Dump & System File Collection app, then the perfmon /report. I went back to the windows/minidump folder, and the one dmp file wasn't there anymore.

No it wasnt and there can be several reasons why.


For dumps to be produced. . .
▪ Page file must be on OS drive
▪ Page file base allocation size must be > than installed physical RAM
▪ Windows Error Reporting (WER) system service should be set to MANUAL
▪ Set page file to system managed, OS drive

Set System Crash/ Recovery Settings to "Kernel Memory Dump" - this will produce. . .
--> a Full Kernel Memory Dump - c:\windows\memory.dmp
--> a Mini Kernel dump c:\windows\minidump

The Full Kernel is overwritten each BSOD; a new mini kernel dump is created w/ different name for each BSOD

To check your system's "Recoveros" (Recovery) and Page File settings via Windows Management Instrumentation (WMI), run the following -

HTML output - WMI - "Recoveros" and Page File Settings (HTML)
Text file output - WMI - "Recoveros" and Page File Settings (TEXT)

Thanks to jgriff2 @sysnative.com

ok i get it now. i'll just wait for the next BSOD then. Thanks.