Kims BSOD Problem

[Kimberlee]

So this happens :

 

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.0.6002.2.2.0.768.3

Locale ID: 1033

 

Additional information about the problem:

BCCode: 1000007e

BCP1: FFFFFFFFC0000005

BCP2: FFFFFA6003E2A661

BCP3: FFFFFA60041ED9B8

BCP4: FFFFFA60041ED390

OS Version: 6_0_6002

Service Pack: 2_0

Product: 768_1

 

Files that help describe the problem:

C:\Windows\Minidump\Mini102211-02.dmp

C:\Users\Jay\AppData\Local\Temp\WER-40451-0.sysdata.xml

C:\Users\Jay\AppData\Local\Temp\WERA285.tmp.version.txt

 

Read our privacy statement:

http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

 

I used BlueScreenViewer and it came up with this information listed from the minidump for the last BSOD in red highlighted lines -

 

Filename: ntoskrnl.exe

Address in stack: ntoskrnl.exe+1918a0

From Address: fffff800`01a59000

To address: fffff800`01f71000

Size: 0x00518000

Time stamp: 0x4dfb5a33

 

FIlename: RTL8192u.sys

Address in stack: RTL8192u.sys+4ec42

From address: fffffa60`04050000

To address: fffffa60`040db000

Size: 0x0008b000

Time stamp: 0x49af508e

 

How does Kim fix it?

Edited October 23, 2011 by Kimberlee

[CommanderCrazy]

Check the afflicted files using this handy tool for starters, report results.

[robert01]

All depends on what you are doing when it happens... In Windows7 the BSOD is usually reserved for hardware issues. Unstable overclock maybe?

[Fonger]

did you ever contact customer support/service about your hardware

 

you've been having nothing but boils from that PC

[N3C14R]

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

(Click to consult the online MSDN article.)

A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem' date=' including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.[/b']

Which I think it means that the computer created/processed invalid/corrupt data and Windows didn't detect it. Thus, causing the kernel to become unstable and leading to the BSOD.

 

I don't know an exact way to correct it but I suggest doing a system restore to a point in time when the BSOD's didn't happen and see if it goes away.

Edited October 23, 2011 by N3C14R

[Kimberlee]

I have added additional information to the original problems as it seems that the BSOD keeps popping up its ugly head. Hopefully this will move me forward to a solution...

[Paxan_1]

Hi Kim,

 

such BSoD came mostly from a hardware / driver failure. For your code MS is writing this:

 

http://msdn.microsoft.com/en-us/library/ff557196%28v=VS.85%29.aspx

 

If you havent overclocked your system i would suggest to have a look into the smart values of your harddrive.

 

Sarah

[CommanderCrazy]

The RTL8192u.sys appears to be a driver for Realtek RTL8192u USB network adapter.

Try updating / reinstalling it.

Edited October 23, 2011 by CommanderCrazy

[MotoSxorpio]

I believe you have a very bad and determined dataminer. YOu should grab a new HD and OS install disc, remove that hdd you have and get usb kit for files transfer. The hook that is being used is leaking memory and CPu time, causing windows to think the kernel is breaking (kernel runs your hardware). The USB device is your network connection, the hook has hold of this device as well, causing memory/CPu time leaks while it tries to gobble data.