First BSOD

[Albo]

Originally Posted by Bman212121

what's your time offset? It might be possible that it is displaying GMT time for some reason.

Eastern, so -5.

[Albo]

Originally Posted by lduguay

Wait

Is there something wrong?

[JasonPC]

Have you ever installed Daemon tools before the last time? I ask because I believe when you uninstall it, the sptd component driver is left behind and it can make a lot of problems particularly with copy protection. Good idea to make sure it's removed just for good measure.

[Albo]

Alright, 3rd BSOD, 3rd time on CS:S.

This time, when Windows opened up, it showed the 'Windows has recovered from an unexpected shutdown" This time though, I clicked on more infomation, and i found out that it has created 3 dump files for the 3 BSOD in the minidump folder in the windows folder. Anyways, the window tells me the following information on the bluescreen:

Problem signature:
Problem Event Name: BlueScreen
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 96C864A0
BCP3: 8B1E3BF0
BCP4: 00000000
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070410-18751-01.dmp
C:\Users\*\AppData\Local\Temp\WER-44631-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

[Albo]

Also, the whocrashed file that Gray_1 posted, states the following on the crash.

On Sun 7/4/2010 7:30:31 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x96C864A0, 0x8B1E3BF0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\070410-18751-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

[nekrosoft13]

win32k.sys is microsoft system driver responsible for "multi-user win32 enviroment" it can also be caused by a driver.
also note: that if a driver caused the win32k.sys to cause BSOD, it can either be driver issue or hardware issue.

first check your file, it should be version 6.1.7600.16585 size of 3,122,176 bytes.

then go to run box (windows key + R) and type verifier and enter

keep the "select standard settings" and next on "select what drivers to verify" plage, first select "automatically select drivers build for older versions of windows" and next

and take screenshot and post it
and go back and select "automatically select unsigned drivers"
and take screenshot and post it

don't click "finish" that will kick your PC in debuging driver mode, and sometimes it can be hard to get out from.

also follow this http://www.sevenforums.com/tutorials...e-checker.html

to verify if any of your system files are corrupt.

[Albo]

Originally Posted by nekrosoft13

win32k.sys is microsoft system driver responsible for "multi-user win32 enviroment" it can also be caused by a driver.
also note: that if a driver caused the win32k.sys to cause BSOD, it can either be driver issue or hardware issue.

first check your file, it should be version 6.1.7600.16585 size of 3,122,176 bytes.

then go to run box (windows key + R) and type verifier and enter

keep the "select standard settings" and next on "select what drivers to verify" plage, first select "automatically select drivers build for older versions of windows" and next

and take screenshot and post it
and go back and select "automatically select unsigned drivers"
and take screenshot and post it

don't click "finish" that will kick your PC in debuging driver mode, and sometimes it can be hard to get out from.

also follow this http://www.sevenforums.com/tutorials...e-checker.html

to verify if any of your system files are corrupt.

It's not, it's 2.21 MB (2,326,528 bytes)





EDIT:
here are the photos

Also, verifying the windows files, (the last step that you said)

[Albo]

Also, in the middle of the last scan sfc part, windows explorer crashed. When I tried to redo the scan it said cannot scan, because there is another windows repair function is going on, like a scan was being taken or something? It won't let me scan. Also after windows explorer cam back up, all my programs were closed except for Kaspersky.

[ViN86]

Originally Posted by Albo

It's not, it's 2.21 MB (2,326,528 bytes)





EDIT:
here are the photos

Also, verifying the windows files, (the last step that you said)

Mine is 2.21MB on my laptop, which is Win7 x86.

[Albo]

Originally Posted by ViN86

Mine is 2.21MB on my laptop, which is Win7 x86.

Same, but he said it should be like 3 MB, so IDK, maybe he has x64?

[ViN86]

Originally Posted by Albo

Same, but he said it should be like 3 MB, so IDK, maybe he has x64?

Yes, that's what I was thinking, hence why I posted my file size on my laptop which has x86.

[Albo]

Another day, another BSOD. AGAIN it was while I was playing CSS. When it happened, I tried reading the screen for anything that it said, it said something about video adapters, but I don't know if it says that for each BSOD. Anyways, the whocrashed app, it says the same thing as last time,

On Mon 7/5/2010 4:46:20 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x96C864A0, 0x8B1E3BF0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\070510-23010-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

So I'm pretty sure it's that file. I'm reading up on it now. Any further suggestions?

EDIT: I was convinced that it was a nvidia driver issue because it always occurred during CSS and CSS crashes often. when looking at the driver site, it said 257.21, right now, I have 195.62- Wow, I'm far behind, lol. I'm updating now.