Overclock.net › Forums › AMD › AMD - General › Just got BSOD O.o
New Posts  All Forums:Forum Nav:

Just got BSOD O.o

post #1 of 3
Thread Starter 
Ok so my system randomly restarted after the screen went completely black, I saw no blue screen or error message but on the restart I got a message which popped up and said.

Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7600.2.0.0.256.48
Locale ID:1033

Additional information about the problem:
BCCode:1000008e
BCP1:C0000005
BCP2:91A702A7
BCP3:9EC81794
BCP4:00000000
OS Version:6_1_7600
Service Pack:0_0
Product:256_1

Files that help describe the problem:
C:\\Windows\\Minidump\\010711-16879-01.dmp
C:\\Users\\Juganot\\AppData\\Local\\Temp\\WER-48875-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\\Windows\\system32\\en-US\\erofflps.txt

Any idea about what this BSOD was caused by?
Main Rig
(15 items)
 
Linux PC
(7 items)
 
 
CPUMotherboardGraphicsRAM
i5 2500k 4.3 GHz @1.28v Gigabyte GA-Z68X-UD3P Intel Z68 (REV B3) 2x Sapphire HD 6870 16GB Mushkin Blackline 1600MHz 
Hard DriveHard DriveHard DriveOptical Drive
1x Mushkin Chronos 120gb 2x Samsung F3 1TB  1x Segate 500gb Samsung SH-S223C 
OSMonitorPowerCase
W7 Home Premium 64 bit BenQ 22"  Corsair TX750 NZXT Phantom White V2 
CPUMotherboardGraphicsRAM
Phenom II 955 4.0GHz Asrock extreme3 880g Onboard 4gb Corsair XM3 1600MHz 
Hard DriveOSMonitor
Segate 500gb Ubuntu 18" CTX 
  hide details  
Reply
Main Rig
(15 items)
 
Linux PC
(7 items)
 
 
CPUMotherboardGraphicsRAM
i5 2500k 4.3 GHz @1.28v Gigabyte GA-Z68X-UD3P Intel Z68 (REV B3) 2x Sapphire HD 6870 16GB Mushkin Blackline 1600MHz 
Hard DriveHard DriveHard DriveOptical Drive
1x Mushkin Chronos 120gb 2x Samsung F3 1TB  1x Segate 500gb Samsung SH-S223C 
OSMonitorPowerCase
W7 Home Premium 64 bit BenQ 22"  Corsair TX750 NZXT Phantom White V2 
CPUMotherboardGraphicsRAM
Phenom II 955 4.0GHz Asrock extreme3 880g Onboard 4gb Corsair XM3 1600MHz 
Hard DriveOSMonitor
Segate 500gb Ubuntu 18" CTX 
  hide details  
Reply
post #2 of 3
win32k.sys is a Windows OS drivers and OS drivers are usually too general to be of much diagnostic help. However, both error codes are 0x8E and these are almost always caused by hardware
and are a good indicator that the issue might be corrupted memory.

Therefore we advise running memtest on your RAM.

See the link below and follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
    
CPUMotherboardGraphicsRAM
Intel i7 980x ~ 4.4Ghz @ 1.375v EVGA E758SLI x58 2 x Nvidia GTX 295 Reference in quad sli G.Skill Trident 6GB 2000Mhz 
Hard DriveOptical DriveOSMonitor
2 x Raptor on RAID 0, 1TB Seagate in IcyDock ext. Pioneer 12x Blu-ray RW Windows 7 x64 3 x Alienware OptX AW2310 in Surround Vision 
KeyboardPowerCaseMouse
Enermax Aurora (black) Antec TPQ 1200w Antec p182 w/ black p180b panels Saitek Cyborg R.A.T. 7 
Mouse Pad
Steelseries QcK (cloth) 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel i7 980x ~ 4.4Ghz @ 1.375v EVGA E758SLI x58 2 x Nvidia GTX 295 Reference in quad sli G.Skill Trident 6GB 2000Mhz 
Hard DriveOptical DriveOSMonitor
2 x Raptor on RAID 0, 1TB Seagate in IcyDock ext. Pioneer 12x Blu-ray RW Windows 7 x64 3 x Alienware OptX AW2310 in Surround Vision 
KeyboardPowerCaseMouse
Enermax Aurora (black) Antec TPQ 1200w Antec p182 w/ black p180b panels Saitek Cyborg R.A.T. 7 
Mouse Pad
Steelseries QcK (cloth) 
  hide details  
Reply
post #3 of 3
Quote:
Originally Posted by thisizbrian View Post
win32k.sys is a Windows OS drivers and OS drivers are usually too general to be of much diagnostic help. However, both error codes are 0x8E and these are almost always caused by hardware
and are a good indicator that the issue might be corrupted memory.

Therefore we advise running memtest on your RAM.

See the link below and follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.
Excellent simple advice on how to use Memtest.
+1 rep to you.
Master
(14 items)
 
  
CPUMotherboardGraphicsRAM
8320 FX Sabertooth 990FX 2x EVGA GTX580 4 gig G.Skill Flares 
Hard DriveCoolingOSPower
Patriot Inferno SSD Custom Water XP PCP&C 750 
  hide details  
Reply
Master
(14 items)
 
  
CPUMotherboardGraphicsRAM
8320 FX Sabertooth 990FX 2x EVGA GTX580 4 gig G.Skill Flares 
Hard DriveCoolingOSPower
Patriot Inferno SSD Custom Water XP PCP&C 750 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD - General
Overclock.net › Forums › AMD › AMD - General › Just got BSOD O.o