Solved BSOD win32k.sys Win7 64-Bit

[cimerians]

After going through SDk7.1 and trying to read the dump files myself using winDBG etc. I'm getting a little frustrated so I think if I ask for some help I won't feel bad about being able to read those things cause I really can't atm. Although I know I'm on the right track.

I'm getting a BSOD SYSTEM_SERVICE_EXCEPTION with a win32k.sys error maybe 3 or 4 times a week.
Eventviewer shows an error and I have it disabled to reboot automatically when it dumps.

It doesn't happen too often but I noticed the last time it did my fan was really loud when I turned the machine on. I'm not sure if it's a fan issue but thats the only thing I physically noticed. The fan never does that normally on boot up but once in a while (twice a month) when I power on it's loud as hell and then slows down to normal.

Anyway, it could be something else but wanted to mention that. I've attached a mini dump (memory.dmp is 300MB). If anyone can help I would really appreciate it. I will go back to try and read these dump files in the meantime. I'm in IT, I should be doing this myself!

I also ran SFC /SCANNOW and it came up ok.
Did not run driver verifier although I think I ran the automated one from Microsofts website the other day. (The "fix it" exe with a GUI) It only told me to enable my NIC (which I have disabled and dont use)

Updated my ASUS motherboard BIOS as well but that didn't seem to help. I don't do overclocking or anything but I do have a dual-boot Win7/WinXP machine with the help of this website if I remember.

Thanks for hearing me out. My first post here. Sadly its for a BSOD.
Any help I'll gladly take.



Another note:
I can post my pc specs or anything if its needed.
Whenever this BSOD happens In event viewer it shows:
Critical Error Kernel-Power Event ID 41

+ System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2010-06-29T12:33:48.080015100Z

EventRecordID 31507

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Hellas

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0xfffff960000cab1d
BugcheckParameter3 0xfffff88009cc01c0
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

 

[JMH]

After going through SDk7.1 and trying to read the dump files myself using winDBG etc. I'm getting a little frustrated so I think if I ask for some help I won't feel bad about being able to read those things cause I really can't atm. Although I know I'm on the right track.

I'm getting a BSOD SYSTEM_SERVICE_EXCEPTION with a win32k.sys error maybe 3 or 4 times a week.
Eventviewer shows an error and I have it disabled to reboot automatically when it dumps.

It doesn't happen too often but I noticed the last time it did my fan was really loud when I turned the machine on. I'm not sure if it's a fan issue but thats the only thing I physically noticed. The fan never does that normally on boot up but once in a while (twice a month) when I power on it's loud as hell and then slows down to normal.

Anyway, it could be something else but wanted to mention that. I've attached a mini dump (memory.dmp is 300MB). If anyone can help I would really appreciate it. I will go back to try and read these dump files in the meantime. I'm in IT, I should be doing this myself!

I also ran SFC /SCANNOW and it came up ok.
Did not run driver verifier although I think I ran the automated one from Microsofts website the other day. (The "fix it" exe with a GUI) It only told me to enable my NIC (which I have disabled and dont use)

Updated my ASUS motherboard BIOS as well but that didn't seem to help. I don't do overclocking or anything but I do have a dual-boot Win7/WinXP machine with the help of this website if I remember.

Thanks for hearing me out. My first post here. Sadly its for a BSOD.
Any help I'll gladly take.



Another note:
I can post my pc specs or anything if its needed.
Whenever this BSOD happens In event viewer it shows:
Critical Error Kernel-Power Event ID 41

Cimerians Hi and welcome


This crash was probably caused by memory corruption. In order to test your ram you will need to download a 3rd party application called memtestx86. Burn that to a cd, and run it for at least 5 passes.

Let us know the results please and tell us if you require further assistance.

Thanks

Jan

+ System 

  - Provider 

   [ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4} 
 
   EventID 41 
 
   Version 2 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000000000000002 
 
  - TimeCreated 

   [ SystemTime]  2010-06-29T12:33:48.080015100Z 
 
   EventRecordID 31507 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  8 
 
   Channel System 
 
   Computer Hellas 
 
  - Security 

   [ UserID]  S-1-5-18

- EventData

BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0xfffff960000cab1d
BugcheckParameter3 0xfffff88009cc01c0
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 08:31:26.096 2010 (GMT-4)
System Uptime: 0 days 0:05:33.062
BugCheck 3B, {c0000005, fffff960000cab1d, fffff88009cc01c0, 0}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x3B
PROCESS_NAME:  sidebar.exe

 

[cimerians]

I figured out how to read the dump file a bit. Probably Caused by: Memory_Corruption
Module name: nt

I couldnt really find much info after googling for a bit.
I have a sinking feeling its Windows 7 or my memory sticks.

 

[cimerians]

Jan thanks a whole bunch for the reply, like I said I appreciate it. I removed the huge text of the dump file in my post above. If anyone wants it I can post it back since we may be zeroing in on what the issue is.

Whew...I'll do exactly as you say and post it here.

 

[zigzag3143]

I figured out how to read the dump file a bit. Probably Caused by: Memory_Corruption
Module name: nt

I couldnt really find much info after googling for a bit.
I have a sinking feeling its Windows 7 or my memory sticks.

cimerians

It is either your memory or your motherboard slot. Chances are good its memory. The first parameter listed is for a memory exception and that is backed up by the bugcheck as well.

It is a simple enough thing as my esteemed colleague Jan suggested to run memtest and you will know within a short (relatively) time if it is that.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Let us know if you need help with this.

Ken

 

[cimerians]

Hmmm....I ran the memtest at least 7 passes (it ran overnight). I didnt get any errors at all. Could be the slots but would the memory checker know that? I think it only tests the sticks.

I attached the remaining mini dumps. The early onese show hardware causes and then some nt files are shown in the remainder.

 

[ttran]

If you already run the memtestx86 for at least 7 passes with no error-->that's good Ram stick, then as Ken mentioned, you can test that stick on other slots to find out which slots are bad.
The earlier dump files point to code 124, hardware, you may want to read this article:
http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

BugCheck 1000007E, {ffffffffc0000005, fffff80002ee5ba8, fffff880033e0888, fffff880033e00f0}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6a8 )

Followup: MachineOwner
---------
BugCheck A, {708006e33a50, 2, 0, fffff80002f29a2f}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )

Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002e6af2e, fffff88006179d08, fffff88006179570}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::AcquireDdiSync+c9 )

Followup: MachineOwner
---------

BugCheck 124, {0, fffffa8006c584f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

 

[cimerians]

Thanks, I'll try removing some of the sticks. It's basically x3 2G sticks for a total of 6G. I'll remove all except one and go from there. You know the other thing on my mind is the dual boot setup. I got the machine around April 14th and the first dump is dated May 8th. I remember doing the dual boot around this time possibly May 1st. I tracked the dates down from my invoice April 7th and the document I created on how to do a dual boot and saved those instructions after I did it on the May 1st.

I saw from the article above that a code 124 could still possibly be a windows issue. Now I'm wondering if its my dual boot. Hard to beleive that because the dumps specifically say Hardware in them.

 

[cimerians]

Update:
Just an update, thankfully it looks like it's one of the memory sticks even though the mem tests didn't show anything initially:
Installed one memory stick (out of 3) and it bluescreened twice in a day. I removed it and then inserted a different stick and all was well. I then added a second stick and so far so good. I kept the bad one on the side and I can send it back.

It's been about 4 days now with the two good sticks and the PC turned on 24 hours a day. No blue screens or any issues at all.

The brands are OSZ's I'll be replacing the one stick.

Thanks again for the reply's and all. Just wanted to close the thread in case anyone reads this stuff.

 

[JMH]

Update:
Just an update, thankfully it looks like it's one of the memory sticks even though the mem tests didn't show anything initially:
Installed one memory stick (out of 3) and it bluescreened twice in a day. I removed it and then inserted a different stick and all was well. I then added a second stick and so far so good. I kept the bad one on the side and I can send it back.

It's been about 4 days now with the two good sticks and the PC turned on 24 hours a day. No blue screens or any issues at all.

The brands are OSZ's I'll be replacing the one stick.

Thanks again for the reply's and all. Just wanted to close the thread in case anyone reads this stuff.

Great news.

Thanks for reporting back.

Jan.

 

[thefabe]

Glad to hear it is sorted out, just remember to get the exact same memory as the 2 aticks your using now to avoid an future conflicts or issues. Probably didn't need to be mentioned but thought i would anyway. Fabe

 

[cimerians]

Thanks again, appreciate it!