from win7 group from undercover snake named Ray aka Raytard

B

Big 666

Guest
ray wrote:

> This is too funny:

> ========================================

> undisclosed wrote:

>> Hello Everyone,

>>

>> I am running windows 7 and I have been on windows 7 for at least 2

>> months. However, I am getting a blue screen error and do not know what

>> to do. Please provide some input to a solution. Thank you

>>

>>

>> Problem signature:

>> Problem Event Name: BlueScreen

>> OS Version: 6.1.7600.2.0.0.256.1

>> Locale ID: 1033

>>

>> Additional information about the problem:

>> BCCode: 50

>> BCP1: FFFFFA90063598D0

>> BCP2: 0000000000000000

>> BCP3: FFFFF88004F667B7

>> BCP4: 0000000000000005

>> OS Version: 6_1_7600

>> Service Pack: 0_0

>> Product: 256_1

>>

>> Files that help describe the problem:

>> C:\Windows\Minidump\062610-33181-01.dmp

>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>

>> Read our privacy statement online:

>> 'Windows 7 Privacy Statement - Microsoft Windows'

>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>

>> If the online privacy statement is not available, please read our

>> privacy statement offline:

>> C:\Windows\system32\en-US\erofflps.txt

>>

>>

>> -----------------------------------------------------------

>> I downloaded blue screen view and came up with this below I do not

>> know what all this problematic stuff means from bluescreenview.

>>

>>

>> 062610-33181-01.dmp 6/26/2010 10:58:39

>> AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050

> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

> 00000000`00000005 nvlddmkm.sys nvlddmkm.sys

> +13b970 x64 C:\Windows

> \Minidump\062610-33181-01.dmp 2 15 7600

>> 062610-37299-01.dmp 6/26/2010 10:45:01

>> AM 0x00000124 00000000`00000000

> fffffa80`050c7038 00000000`b2000040 00000000`00000800

> hal.dll hal.dll+12903 x64 C:

> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>

>>

>> BELOW WAS HIGHLIGHTED IN PINK

>>

>>

>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>> 3:55:23 AM Microsoft® Windows® Operating System NT Kernel &

>> System 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft

>> Corporation C:\Windows\system32\ntoskrnl.exe

>> nvlddmkm.sys nvlddmkm.sys+13b970 fffff880`04ac2000

> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>> 2:02:29 PM

>>

>>

>

> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver

> is falling over. Use your search engine with that as a search term,

> to see examples of what other people have tried.

>

> You can try a different driver.

>

> Or you can review your hardware test strategy. For example, if

> you build your own computer, use memtest86+ and Prime95 stress

> test, to verify the CPU and RAM are properly adjusted and

> stable. Some people never had a stable hardware platform to begin

> with, and the symptoms can be one blue screen after another, with

> different error messages each time. If you are seeing relatively

> random errors, it could be a CPU/memory adjustment. If the errors

> stay within nvlddmkm.sys, it is also possible the graphics

> card is about to croak. If you have a super high powered

> graphics card, it might even be overloading the PSU at

> peak 3D play. In terms of hardware reasons, you've got a

> few things to consider.

>

> Before jumping to any conclusions, have a look at

> all your bluescreen errors to date, and see if they're

> random, or always the same error (i.e. always the same driver

> file). That kind of info can help you choose a strategy to fix it.

>

> Paul

> ===============================================================

>

> You're kidding me, right? "have a look at all your bluescreen errors" -

> and this is the best MS can do?



What a guy, what a saint and the snake in the grass he really is about.
 
On Sat, 26 Jun 2010 16:28:49 -0400, Big 666 wrote:



> ray wrote:

>> This is too funny:

>> ======================================== undisclosed wrote:

>>> Hello Everyone,

>>>

>>> I am running windows 7 and I have been on windows 7 for at least 2

>>> months. However, I am getting a blue screen error and do not know

>>> what to do. Please provide some input to a solution. Thank you

>>>

>>>

>>> Problem signature:

>>> Problem Event Name: BlueScreen

>>> OS Version: 6.1.7600.2.0.0.256.1

>>> Locale ID: 1033

>>>

>>> Additional information about the problem: BCCode: 50

>>> BCP1: FFFFFA90063598D0

>>> BCP2: 0000000000000000

>>> BCP3: FFFFF88004F667B7

>>> BCP4: 0000000000000005

>>> OS Version: 6_1_7600

>>> Service Pack: 0_0

>>> Product: 256_1

>>>

>>> Files that help describe the problem:

>>> C:\Windows\Minidump\062610-33181-01.dmp

>>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>>

>>> Read our privacy statement online:

>>> 'Windows 7 Privacy Statement - Microsoft Windows'

>>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>>

>>> If the online privacy statement is not available, please read our

>>> privacy statement offline:

>>> C:\Windows\system32\en-US\erofflps.txt

>>>

>>>

>>> ----------------------------------------------------------- I

>>> downloaded blue screen view and came up with this below I do not know

>>> what all this problematic stuff means from bluescreenview.

>>>

>>>

>>> 062610-33181-01.dmp 6/26/2010 10:58:39 AM

PAGE_FAULT_IN_NONPAGED_AREA

>>> 0x00000050

>> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

00000000`00000005

>> nvlddmkm.sys nvlddmkm.sys +13b970

x64 C:\Windows

>> \Minidump\062610-33181-01.dmp 2 15 7600

>>> 062610-37299-01.dmp 6/26/2010 10:45:01 AM 0x00000124

>>> 00000000`00000000

>> fffffa80`050c7038 00000000`b2000040 00000000`00000800 hal.dll

>> hal.dll+12903 x64 C:

>> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>>

>>>

>>> BELOW WAS HIGHLIGHTED IN PINK

>>>

>>>

>>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

>> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>>> 3:55:23 AM Microsoft® Windows® Operating System NT Kernel & System

>>> 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation

>>> C:\Windows\system32\ntoskrnl.exe nvlddmkm.sys nvlddmkm.sys

+13b970

>>> fffff880`04ac2000

>> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>>> 2:02:29 PM

>>>

>>>

>>>

>> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver is

>> falling over. Use your search engine with that as a search term, to see

>> examples of what other people have tried.

>>

>> You can try a different driver.

>>

>> Or you can review your hardware test strategy. For example, if you

>> build your own computer, use memtest86+ and Prime95 stress test, to

>> verify the CPU and RAM are properly adjusted and stable. Some people

>> never had a stable hardware platform to begin with, and the symptoms

>> can be one blue screen after another, with different error messages

>> each time. If you are seeing relatively random errors, it could be a

>> CPU/memory adjustment. If the errors stay within nvlddmkm.sys, it is

>> also possible the graphics card is about to croak. If you have a super

>> high powered graphics card, it might even be overloading the PSU at

>> peak 3D play. In terms of hardware reasons, you've got a few things to

>> consider.

>>

>> Before jumping to any conclusions, have a look at all your bluescreen

>> errors to date, and see if they're random, or always the same error

>> (i.e. always the same driver file). That kind of info can help you

>> choose a strategy to fix it.

>>

>> Paul

>> ===============================================================

>>

>> You're kidding me, right? "have a look at all your bluescreen errors"

>> - and this is the best MS can do?

>

> What a guy, what a saint and the snake in the grass he really is about.



Well, excuse me. It's simply that I have not had the equivalent of a

bluescreen in the 12 years I've been using Linux. Quite frankly, it makes

it sound like that is still quite common in the MS world.
 
ray wrote:

>

> Well, excuse me. It's simply that I have not had the equivalent of a

> bluescreen in the 12 years I've been using Linux. Quite frankly, it makes

> it sound like that is still quite common in the MS world.



You are an under cover snake and a double agent Raytard looking for a

pat on your head like the COLA lapdog that you are about and grinning in

faces in the MS NG(s) and forums.
 
"ray" <ray@zianet.com> wrote in message

news:88n7hgF8dsU10@mid.individual.net...

> On Sat, 26 Jun 2010 16:28:49 -0400, Big 666 wrote:

>

>> ray wrote:

>>> This is too funny:

>>> ======================================== undisclosed wrote:

>>>> Hello Everyone,

>>>>

>>>> I am running windows 7 and I have been on windows 7 for at least 2

>>>> months. However, I am getting a blue screen error and do not know

>>>> what to do. Please provide some input to a solution. Thank you

>>>>

>>>>

>>>> Problem signature:

>>>> Problem Event Name: BlueScreen

>>>> OS Version: 6.1.7600.2.0.0.256.1

>>>> Locale ID: 1033

>>>>

>>>> Additional information about the problem: BCCode: 50

>>>> BCP1: FFFFFA90063598D0

>>>> BCP2: 0000000000000000

>>>> BCP3: FFFFF88004F667B7

>>>> BCP4: 0000000000000005

>>>> OS Version: 6_1_7600

>>>> Service Pack: 0_0

>>>> Product: 256_1

>>>>

>>>> Files that help describe the problem:

>>>> C:\Windows\Minidump\062610-33181-01.dmp

>>>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>>>

>>>> Read our privacy statement online:

>>>> 'Windows 7 Privacy Statement - Microsoft Windows'

>>>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>>>

>>>> If the online privacy statement is not available, please read our

>>>> privacy statement offline:

>>>> C:\Windows\system32\en-US\erofflps.txt

>>>>

>>>>

>>>> ----------------------------------------------------------- I

>>>> downloaded blue screen view and came up with this below I do not know

>>>> what all this problematic stuff means from bluescreenview.

>>>>

>>>>

>>>> 062610-33181-01.dmp 6/26/2010 10:58:39 AM

> PAGE_FAULT_IN_NONPAGED_AREA

>>>> 0x00000050

>>> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

> 00000000`00000005

>>> nvlddmkm.sys nvlddmkm.sys +13b970

> x64 C:\Windows

>>> \Minidump\062610-33181-01.dmp 2 15 7600

>>>> 062610-37299-01.dmp 6/26/2010 10:45:01 AM 0x00000124

>>>> 00000000`00000000

>>> fffffa80`050c7038 00000000`b2000040 00000000`00000800 hal.dll

>>> hal.dll+12903 x64 C:

>>> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>>>

>>>>

>>>> BELOW WAS HIGHLIGHTED IN PINK

>>>>

>>>>

>>>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

>>> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>>>> 3:55:23 AM Microsoft® Windows® Operating System NT Kernel & System

>>>> 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation

>>>> C:\Windows\system32\ntoskrnl.exe nvlddmkm.sys nvlddmkm.sys

> +13b970

>>>> fffff880`04ac2000

>>> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>>>> 2:02:29 PM

>>>>

>>>>

>>>>

>>> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver is

>>> falling over. Use your search engine with that as a search term, to see

>>> examples of what other people have tried.

>>>

>>> You can try a different driver.

>>>

>>> Or you can review your hardware test strategy. For example, if you

>>> build your own computer, use memtest86+ and Prime95 stress test, to

>>> verify the CPU and RAM are properly adjusted and stable. Some people

>>> never had a stable hardware platform to begin with, and the symptoms

>>> can be one blue screen after another, with different error messages

>>> each time. If you are seeing relatively random errors, it could be a

>>> CPU/memory adjustment. If the errors stay within nvlddmkm.sys, it is

>>> also possible the graphics card is about to croak. If you have a super

>>> high powered graphics card, it might even be overloading the PSU at

>>> peak 3D play. In terms of hardware reasons, you've got a few things to

>>> consider.

>>>

>>> Before jumping to any conclusions, have a look at all your bluescreen

>>> errors to date, and see if they're random, or always the same error

>>> (i.e. always the same driver file). That kind of info can help you

>>> choose a strategy to fix it.

>>>

>>> Paul

>>> ===============================================================

>>>

>>> You're kidding me, right? "have a look at all your bluescreen errors"

>>> - and this is the best MS can do?

>>

>> What a guy, what a saint and the snake in the grass he really is about.

>

> Well, excuse me. It's simply that I have not had the equivalent of a

> bluescreen in the 12 years I've been using Linux. Quite frankly, it makes

> it sound like that is still quite common in the MS world.



CORRECTION: You haven't done anything useful with your computer in 12 years

so your computer can't crash! Oops.
 
ray wrote:

> On Sat, 26 Jun 2010 17:27:28 -0400, Big 666 wrote:

>

>> ray wrote:

>>> Well, excuse me. It's simply that I have not had the equivalent of a

>>> bluescreen in the 12 years I've been using Linux. Quite frankly, it

>>> makes it sound like that is still quite common in the MS world.

>> You are an under cover snake and a double agent Raytard looking for a

>> pat on your head like the COLA lapdog that you are about and grinning in

>> faces in the MS NG(s) and forums.

>

> Getting a little tight there, aren't you, frankie? Can't stand having me

> copy a post from one group to another!



This is not Frank you dumb *******, and I know the kind of low-life man

you really are Raytard. You'll knife a person in the back the first

opportunity you'll get. I wouldn't want to be in a foxhole with you.
 
On Sat, 26 Jun 2010 14:37:46 -0700, Mrs. Stan Starinski wrote:



> "ray" <ray@zianet.com> wrote in message

> news:88n7hgF8dsU10@mid.individual.net...

>> On Sat, 26 Jun 2010 16:28:49 -0400, Big 666 wrote:

>>

>>> ray wrote:

>>>> This is too funny:

>>>> ======================================== undisclosed wrote:

>>>>> Hello Everyone,

>>>>>

>>>>> I am running windows 7 and I have been on windows 7 for at least 2

>>>>> months. However, I am getting a blue screen error and do not know

>>>>> what to do. Please provide some input to a solution. Thank you

>>>>>

>>>>>

>>>>> Problem signature:

>>>>> Problem Event Name: BlueScreen

>>>>> OS Version: 6.1.7600.2.0.0.256.1

>>>>> Locale ID: 1033

>>>>>

>>>>> Additional information about the problem: BCCode: 50 BCP1:

>>>>> FFFFFA90063598D0

>>>>> BCP2: 0000000000000000

>>>>> BCP3: FFFFF88004F667B7

>>>>> BCP4: 0000000000000005

>>>>> OS Version: 6_1_7600

>>>>> Service Pack: 0_0

>>>>> Product: 256_1

>>>>>

>>>>> Files that help describe the problem:

>>>>> C:\Windows\Minidump\062610-33181-01.dmp

>>>>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>>>>

>>>>> Read our privacy statement online:

>>>>> 'Windows 7 Privacy Statement - Microsoft Windows'

>>>>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>>>>

>>>>> If the online privacy statement is not available, please read our

>>>>> privacy statement offline:

>>>>> C:\Windows\system32\en-US\erofflps.txt

>>>>>

>>>>>

>>>>> ----------------------------------------------------------- I

>>>>> downloaded blue screen view and came up with this below I do not

>>>>> know what all this problematic stuff means from bluescreenview.

>>>>>

>>>>>

>>>>> 062610-33181-01.dmp 6/26/2010 10:58:39 AM

>> PAGE_FAULT_IN_NONPAGED_AREA

>>>>> 0x00000050

>>>> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

>> 00000000`00000005

>>>> nvlddmkm.sys nvlddmkm.sys +13b970

>> x64 C:\Windows

>>>> \Minidump\062610-33181-01.dmp 2 15 7600

>>>>> 062610-37299-01.dmp 6/26/2010 10:45:01 AM 0x00000124

>>>>> 00000000`00000000

>>>> fffffa80`050c7038 00000000`b2000040 00000000`00000800 hal.dll

>>>> hal.dll+12903 x64 C:

>>>> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>>>>

>>>>>

>>>>> BELOW WAS HIGHLIGHTED IN PINK

>>>>>

>>>>>

>>>>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

>>>> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>>>>> 3:55:23 AM Microsoft® Windows® Operating System NT Kernel & System

>>>>> 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation

>>>>> C:\Windows\system32\ntoskrnl.exe nvlddmkm.sys nvlddmkm.sys

>> +13b970

>>>>> fffff880`04ac2000

>>>> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>>>>> 2:02:29 PM

>>>>>

>>>>>

>>>>>

>>>> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver

>>>> is falling over. Use your search engine with that as a search term,

>>>> to see examples of what other people have tried.

>>>>

>>>> You can try a different driver.

>>>>

>>>> Or you can review your hardware test strategy. For example, if you

>>>> build your own computer, use memtest86+ and Prime95 stress test, to

>>>> verify the CPU and RAM are properly adjusted and stable. Some people

>>>> never had a stable hardware platform to begin with, and the symptoms

>>>> can be one blue screen after another, with different error messages

>>>> each time. If you are seeing relatively random errors, it could be a

>>>> CPU/memory adjustment. If the errors stay within nvlddmkm.sys, it is

>>>> also possible the graphics card is about to croak. If you have a

>>>> super high powered graphics card, it might even be overloading the

>>>> PSU at peak 3D play. In terms of hardware reasons, you've got a few

>>>> things to consider.

>>>>

>>>> Before jumping to any conclusions, have a look at all your

>>>> bluescreen errors to date, and see if they're random, or always the

>>>> same error (i.e. always the same driver file). That kind of info can

>>>> help you choose a strategy to fix it.

>>>>

>>>> Paul

>>>> ===============================================================

>>>>

>>>> You're kidding me, right? "have a look at all your bluescreen

>>>> errors" - and this is the best MS can do?

>>>

>>> What a guy, what a saint and the snake in the grass he really is

>>> about.

>>

>> Well, excuse me. It's simply that I have not had the equivalent of a

>> bluescreen in the 12 years I've been using Linux. Quite frankly, it

>> makes it sound like that is still quite common in the MS world.

>

> CORRECTION: You haven't done anything useful with your computer in 12

> years so your computer can't crash! Oops.



Since MS apparently BSODs whether you're "doing anything useful" or not

(often during boot), I'm not sure what your point is! Oops.
 
ray wrote:

> On Sat, 26 Jun 2010 17:41:31 -0400, Big 666 wrote:

>

>> ray wrote:

>>> On Sat, 26 Jun 2010 17:27:28 -0400, Big 666 wrote:

>>>

>>>> ray wrote:

>>>>> Well, excuse me. It's simply that I have not had the equivalent of a

>>>>> bluescreen in the 12 years I've been using Linux. Quite frankly, it

>>>>> makes it sound like that is still quite common in the MS world.

>>>> You are an under cover snake and a double agent Raytard looking for a

>>>> pat on your head like the COLA lapdog that you are about and grinning

>>>> in faces in the MS NG(s) and forums.

>>> Getting a little tight there, aren't you, frankie? Can't stand having

>>> me copy a post from one group to another!

>> This is not Frank you dumb *******, and I know the kind of low-life man

>> you really are Raytard. You'll knife a person in the back the first

>> opportunity you'll get. I wouldn't want to be in a foxhole with you.

>

> Looks like a duck . . .





I am sure he will applicate it when he sees it. Apparently, he has blown

your mind.
 
ray wrote:

> On Sat, 26 Jun 2010 18:36:16 -0400, Big 666 wrote:

>

>> ray wrote:

>>> On Sat, 26 Jun 2010 17:41:31 -0400, Big 666 wrote:

>>>

>>>> ray wrote:

>>>>> On Sat, 26 Jun 2010 17:27:28 -0400, Big 666 wrote:

>>>>>

>>>>>> ray wrote:

>>>>>>> Well, excuse me. It's simply that I have not had the equivalent of

>>>>>>> a bluescreen in the 12 years I've been using Linux. Quite frankly,

>>>>>>> it makes it sound like that is still quite common in the MS world.

>>>>>> You are an under cover snake and a double agent Raytard looking for

>>>>>> a pat on your head like the COLA lapdog that you are about and

>>>>>> grinning in faces in the MS NG(s) and forums.

>>>>> Getting a little tight there, aren't you, frankie? Can't stand having

>>>>> me copy a post from one group to another!

>>>> This is not Frank you dumb *******, and I know the kind of low-life

>>>> man you really are Raytard. You'll knife a person in the back the

>>>> first opportunity you'll get. I wouldn't want to be in a foxhole with

>>>> you.

>>> Looks like a duck . . .

>>

>> I am sure he will applicate it when he sees it. Apparently, he has blown

>> your mind.

>

> "applicate" ?????????????????



Appreciate -- Raytard. Your problem Raytard is that you got caught with

your pants on the ground and your ass in the air, looking like fool with

your pants on the ground.



So, you're trying to post and lip service your way out of being a

low-life double agent snake that was caught while undercover.
 
ray wrote:



>> Appreciate -- Raytard. Your problem Raytard is that you got caught with

>> your pants on the ground and your ass in the air, looking like fool with

>> your pants on the ground.

>>

>> So, you're trying to post and lip service your way out of being a

>> low-life double agent snake that was caught while undercover.

>

> So, you think I'm a "double agent". Since I have always more or less

> shamelessly advocated Linux, I take it your contention is that although I

> outwardly advocate Linux, I am secretly plotting it's downfall.

>

> Interesting.



You're just a two-faced clown doing one thing here and doing something

else somewhere else.



Why didn't you have the damn guts to post to both NG(s) if your were

advocating something instead of making the single post to COLA?



You made a gutless post looking for a lapdog's pat on the back in COLA

and give the dog a bone, like most of your kind do in COLA.
 
ray wrote:

> On Sat, 26 Jun 2010 16:28:49 -0400, Big 666 wrote:

>

>> ray wrote:

>>> This is too funny:

>>> ======================================== undisclosed wrote:

>>>> Hello Everyone,

>>>>

>>>> I am running windows 7 and I have been on windows 7 for at least 2

>>>> months. However, I am getting a blue screen error and do not know

>>>> what to do. Please provide some input to a solution. Thank you

>>>>

>>>>

>>>> Problem signature:

>>>> Problem Event Name: BlueScreen

>>>> OS Version: 6.1.7600.2.0.0.256.1

>>>> Locale ID: 1033

>>>>

>>>> Additional information about the problem: BCCode: 50

>>>> BCP1: FFFFFA90063598D0

>>>> BCP2: 0000000000000000

>>>> BCP3: FFFFF88004F667B7

>>>> BCP4: 0000000000000005

>>>> OS Version: 6_1_7600

>>>> Service Pack: 0_0

>>>> Product: 256_1

>>>>

>>>> Files that help describe the problem:

>>>> C:\Windows\Minidump\062610-33181-01.dmp

>>>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>>>

>>>> Read our privacy statement online:

>>>> 'Windows 7 Privacy Statement - Microsoft Windows'

>>>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>>>

>>>> If the online privacy statement is not available, please read our

>>>> privacy statement offline:

>>>> C:\Windows\system32\en-US\erofflps.txt

>>>>

>>>>

>>>> ----------------------------------------------------------- I

>>>> downloaded blue screen view and came up with this below I do not

>>>> know what all this problematic stuff means from bluescreenview.

>>>>

>>>>

>>>> 062610-33181-01.dmp 6/26/2010 10:58:39 AM

> PAGE_FAULT_IN_NONPAGED_AREA

>>>> 0x00000050

>>> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

>>> 00000000`00000005 nvlddmkm.sys nvlddmkm.sys +13b970

> x64 C:\Windows

>>> \Minidump\062610-33181-01.dmp 2 15 7600

>>>> 062610-37299-01.dmp 6/26/2010 10:45:01 AM 0x00000124

>>>> 00000000`00000000

>>> fffffa80`050c7038 00000000`b2000040 00000000`00000800 hal.dll

>>> hal.dll+12903 x64 C:

>>> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>>>

>>>>

>>>> BELOW WAS HIGHLIGHTED IN PINK

>>>>

>>>>

>>>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

>>> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>>>> 3:55:23 AM Microsoft? Windows? Operating System NT Kernel & System

>>>> 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation

>>>> C:\Windows\system32\ntoskrnl.exe nvlddmkm.sys nvlddmkm.sys

> +13b970

>>>> fffff880`04ac2000

>>> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>>>> 2:02:29 PM

>>>>

>>>>

>>>>

>>> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver

>>> is falling over. Use your search engine with that as a search term,

>>> to see examples of what other people have tried.

>>>

>>> You can try a different driver.

>>>

>>> Or you can review your hardware test strategy. For example, if you

>>> build your own computer, use memtest86+ and Prime95 stress test, to

>>> verify the CPU and RAM are properly adjusted and stable. Some people

>>> never had a stable hardware platform to begin with, and the symptoms

>>> can be one blue screen after another, with different error messages

>>> each time. If you are seeing relatively random errors, it could be a

>>> CPU/memory adjustment. If the errors stay within nvlddmkm.sys, it is

>>> also possible the graphics card is about to croak. If you have a

>>> super high powered graphics card, it might even be overloading the

>>> PSU at peak 3D play. In terms of hardware reasons, you've got a few

>>> things to consider.

>>>

>>> Before jumping to any conclusions, have a look at all your

>>> bluescreen errors to date, and see if they're random, or always the

>>> same error (i.e. always the same driver file). That kind of info

>>> can help you choose a strategy to fix it.

>>>

>>> Paul

>>> ===============================================================

>>>

>>> You're kidding me, right? "have a look at all your bluescreen

>>> errors" - and this is the best MS can do?

>>

>> What a guy, what a saint and the snake in the grass he really is

>> about.

>

> Well, excuse me. It's simply that I have not had the equivalent of a

> bluescreen in the 12 years I've been using Linux. Quite frankly, it

> makes it sound like that is still quite common in the MS world.



When I tried to install Linux on old P150 Packerd Bell, it would give me a

Kernal Panic before it finished the install. My P4 3GHz, has problems with

Linux and Window XP, the only thing I can get to install on it was Windows

2000. I have had problems with nVidia's drivers and it would make

Windows XP crash, it was a motherboard problem and not a video card

problem, I found that out when I put in a new video card and it still gave

me errors. I have only had BSOD on XP when I had a hardware issue.

Though one time I did get Window 2000 to BSOD with a VB program, Window 98

had no problems with the program. What kind of warnings does Linux give

you when your hardware is about ready to die?
 
Quantum Leaper wrote:

> ray wrote:

>> On Sat, 26 Jun 2010 16:28:49 -0400, Big 666 wrote:

>>

>>> ray wrote:

>>>> This is too funny:

>>>> ======================================== undisclosed wrote:

>>>>> Hello Everyone,

>>>>>

>>>>> I am running windows 7 and I have been on windows 7 for at least 2

>>>>> months. However, I am getting a blue screen error and do not know

>>>>> what to do. Please provide some input to a solution. Thank you

>>>>>

>>>>>

>>>>> Problem signature:

>>>>> Problem Event Name: BlueScreen

>>>>> OS Version: 6.1.7600.2.0.0.256.1

>>>>> Locale ID: 1033

>>>>>

>>>>> Additional information about the problem: BCCode: 50

>>>>> BCP1: FFFFFA90063598D0

>>>>> BCP2: 0000000000000000

>>>>> BCP3: FFFFF88004F667B7

>>>>> BCP4: 0000000000000005

>>>>> OS Version: 6_1_7600

>>>>> Service Pack: 0_0

>>>>> Product: 256_1

>>>>>

>>>>> Files that help describe the problem:

>>>>> C:\Windows\Minidump\062610-33181-01.dmp

>>>>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>>>>

>>>>> Read our privacy statement online:

>>>>> 'Windows 7 Privacy Statement - Microsoft Windows'

>>>>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>>>>

>>>>> If the online privacy statement is not available, please read our

>>>>> privacy statement offline:

>>>>> C:\Windows\system32\en-US\erofflps.txt

>>>>>

>>>>>

>>>>> ----------------------------------------------------------- I

>>>>> downloaded blue screen view and came up with this below I do not

>>>>> know what all this problematic stuff means from bluescreenview.

>>>>>

>>>>>

>>>>> 062610-33181-01.dmp 6/26/2010 10:58:39 AM

>> PAGE_FAULT_IN_NONPAGED_AREA

>>>>> 0x00000050

>>>> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

>>>> 00000000`00000005 nvlddmkm.sys nvlddmkm.sys +13b970

>> x64 C:\Windows

>>>> \Minidump\062610-33181-01.dmp 2 15 7600

>>>>> 062610-37299-01.dmp 6/26/2010 10:45:01 AM 0x00000124

>>>>> 00000000`00000000

>>>> fffffa80`050c7038 00000000`b2000040 00000000`00000800 hal.dll

>>>> hal.dll+12903 x64 C:

>>>> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>>>>

>>>>> BELOW WAS HIGHLIGHTED IN PINK

>>>>>

>>>>>

>>>>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

>>>> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>>>>> 3:55:23 AM Microsoft? Windows? Operating System NT Kernel & System

>>>>> 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation

>>>>> C:\Windows\system32\ntoskrnl.exe nvlddmkm.sys nvlddmkm.sys

>> +13b970

>>>>> fffff880`04ac2000

>>>> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>>>>> 2:02:29 PM

>>>>>

>>>>>

>>>>>

>>>> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver

>>>> is falling over. Use your search engine with that as a search term,

>>>> to see examples of what other people have tried.

>>>>

>>>> You can try a different driver.

>>>>

>>>> Or you can review your hardware test strategy. For example, if you

>>>> build your own computer, use memtest86+ and Prime95 stress test, to

>>>> verify the CPU and RAM are properly adjusted and stable. Some people

>>>> never had a stable hardware platform to begin with, and the symptoms

>>>> can be one blue screen after another, with different error messages

>>>> each time. If you are seeing relatively random errors, it could be a

>>>> CPU/memory adjustment. If the errors stay within nvlddmkm.sys, it is

>>>> also possible the graphics card is about to croak. If you have a

>>>> super high powered graphics card, it might even be overloading the

>>>> PSU at peak 3D play. In terms of hardware reasons, you've got a few

>>>> things to consider.

>>>>

>>>> Before jumping to any conclusions, have a look at all your

>>>> bluescreen errors to date, and see if they're random, or always the

>>>> same error (i.e. always the same driver file). That kind of info

>>>> can help you choose a strategy to fix it.

>>>>

>>>> Paul

>>>> ===============================================================

>>>>

>>>> You're kidding me, right? "have a look at all your bluescreen

>>>> errors" - and this is the best MS can do?

>>> What a guy, what a saint and the snake in the grass he really is

>>> about.

>> Well, excuse me. It's simply that I have not had the equivalent of a

>> bluescreen in the 12 years I've been using Linux. Quite frankly, it

>> makes it sound like that is still quite common in the MS world.

>

> When I tried to install Linux on old P150 Packerd Bell, it would give me a

> Kernal Panic before it finished the install. My P4 3GHz, has problems with

> Linux and Window XP, the only thing I can get to install on it was Windows

> 2000. I have had problems with nVidia's drivers and it would make

> Windows XP crash, it was a motherboard problem and not a video card

> problem, I found that out when I put in a new video card and it still gave

> me errors. I have only had BSOD on XP when I had a hardware issue.

> Though one time I did get Window 2000 to BSOD with a VB program, Window 98

> had no problems with the program. What kind of warnings does Linux give

> you when your hardware is about ready to die?

>

>



Linux black screen of death!
 
ray <ray@zianet.com> writes:



> On Sat, 26 Jun 2010 14:37:46 -0700, Mrs. Stan Starinski wrote:

>

>> "ray" <ray@zianet.com> wrote in message

>> news:88n7hgF8dsU10@mid.individual.net...

>>> On Sat, 26 Jun 2010 16:28:49 -0400, Big 666 wrote:

>>>

>>>> ray wrote:

>>>>> This is too funny:

>>>>> ======================================== undisclosed wrote:

>>>>>> Hello Everyone,

>>>>>>

>>>>>> I am running windows 7 and I have been on windows 7 for at least 2

>>>>>> months. However, I am getting a blue screen error and do not know

>>>>>> what to do. Please provide some input to a solution. Thank you

>>>>>>

>>>>>>

>>>>>> Problem signature:

>>>>>> Problem Event Name: BlueScreen

>>>>>> OS Version: 6.1.7600.2.0.0.256.1

>>>>>> Locale ID: 1033

>>>>>>

>>>>>> Additional information about the problem: BCCode: 50 BCP1:

>>>>>> FFFFFA90063598D0

>>>>>> BCP2: 0000000000000000

>>>>>> BCP3: FFFFF88004F667B7

>>>>>> BCP4: 0000000000000005

>>>>>> OS Version: 6_1_7600

>>>>>> Service Pack: 0_0

>>>>>> Product: 256_1

>>>>>>

>>>>>> Files that help describe the problem:

>>>>>> C:\Windows\Minidump\062610-33181-01.dmp

>>>>>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>>>>>

>>>>>> Read our privacy statement online:

>>>>>> 'Windows 7 Privacy Statement - Microsoft Windows'

>>>>>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>>>>>

>>>>>> If the online privacy statement is not available, please read our

>>>>>> privacy statement offline:

>>>>>> C:\Windows\system32\en-US\erofflps.txt

>>>>>>

>>>>>>

>>>>>> ----------------------------------------------------------- I

>>>>>> downloaded blue screen view and came up with this below I do not

>>>>>> know what all this problematic stuff means from bluescreenview.

>>>>>>

>>>>>>

>>>>>> 062610-33181-01.dmp 6/26/2010 10:58:39 AM

>>> PAGE_FAULT_IN_NONPAGED_AREA

>>>>>> 0x00000050

>>>>> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

>>> 00000000`00000005

>>>>> nvlddmkm.sys nvlddmkm.sys +13b970

>>> x64 C:\Windows

>>>>> \Minidump\062610-33181-01.dmp 2 15 7600

>>>>>> 062610-37299-01.dmp 6/26/2010 10:45:01 AM 0x00000124

>>>>>> 00000000`00000000

>>>>> fffffa80`050c7038 00000000`b2000040 00000000`00000800 hal.dll

>>>>> hal.dll+12903 x64 C:

>>>>> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>>>>>

>>>>>>

>>>>>> BELOW WAS HIGHLIGHTED IN PINK

>>>>>>

>>>>>>

>>>>>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

>>>>> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>>>>>> 3:55:23 AM Microsoft® Windows® Operating System NT Kernel & System

>>>>>> 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation

>>>>>> C:\Windows\system32\ntoskrnl.exe nvlddmkm.sys nvlddmkm.sys

>>> +13b970

>>>>>> fffff880`04ac2000

>>>>> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>>>>>> 2:02:29 PM

>>>>>>

>>>>>>

>>>>>>

>>>>> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver

>>>>> is falling over. Use your search engine with that as a search term,

>>>>> to see examples of what other people have tried.

>>>>>

>>>>> You can try a different driver.

>>>>>

>>>>> Or you can review your hardware test strategy. For example, if you

>>>>> build your own computer, use memtest86+ and Prime95 stress test, to

>>>>> verify the CPU and RAM are properly adjusted and stable. Some people

>>>>> never had a stable hardware platform to begin with, and the symptoms

>>>>> can be one blue screen after another, with different error messages

>>>>> each time. If you are seeing relatively random errors, it could be a

>>>>> CPU/memory adjustment. If the errors stay within nvlddmkm.sys, it is

>>>>> also possible the graphics card is about to croak. If you have a

>>>>> super high powered graphics card, it might even be overloading the

>>>>> PSU at peak 3D play. In terms of hardware reasons, you've got a few

>>>>> things to consider.

>>>>>

>>>>> Before jumping to any conclusions, have a look at all your

>>>>> bluescreen errors to date, and see if they're random, or always the

>>>>> same error (i.e. always the same driver file). That kind of info can

>>>>> help you choose a strategy to fix it.

>>>>>

>>>>> Paul

>>>>> ===============================================================

>>>>>

>>>>> You're kidding me, right? "have a look at all your bluescreen

>>>>> errors" - and this is the best MS can do?

>>>>

>>>> What a guy, what a saint and the snake in the grass he really is

>>>> about.

>>>

>>> Well, excuse me. It's simply that I have not had the equivalent of a

>>> bluescreen in the 12 years I've been using Linux. Quite frankly, it

>>> makes it sound like that is still quite common in the MS world.

>>

>> CORRECTION: You haven't done anything useful with your computer in 12

>> years so your computer can't crash! Oops.

>

> Since MS apparently BSODs whether you're "doing anything useful" or not

> (often during boot), I'm not sure what your point is! Oops.





Meanwhile people are left with dead Debian and Ubuntu machines because

grub2 failed to init properly or the move to UUIDS failed.



Raytard, you lose more credibility with every fanboi post.
 
On 6/26/2010 11:37 PM, Mrs. Stan Starinski wrote:



> CORRECTION: You haven't done anything useful with your computer in 12

> years so your computer can't crash! Oops.



CORRECTION: Wrong! Most BSODs (if not all) are a result of hardware

problems. It has nothing to do with useful or useless usage of a computer.



--

Alias
 
ray wrote:



> Well, excuse me. It's simply that I have not had the equivalent of a

> bluescreen in the 12 years I've been using Linux. Quite frankly, it makes

> it sound like that is still quite common in the MS world.



You would think they would change randomly change the color of these

crash screens, just for a little variety.



--

RonB

"There's a story there...somewhere"
 
RonB wrote:

> ray wrote:

>

>> Well, excuse me. It's simply that I have not had the equivalent of a

>> bluescreen in the 12 years I've been using Linux. Quite frankly, it

>> makes it sound like that is still quite common in the MS world.

>

> You would think they would change randomly change the color of these

> crash screens, just for a little variety.

>



Ron Bambi you can go stand in front of headlights, instead of licking

up someone's COLA droppings.
 
On 27/06/2010 10:18, RonB wrote:

> You would think they would change randomly change the color of these

> crash screens, just for a little variety.



Something poetic about the "Brown screen of death"!



(Sorry to have posted that to you directly RonB, thats 3 times today I

did that... maybe I should start using the reply BUTTONS instead of the

pop-up menu)



--

Whenever the black fox jumped the squirrel gazed suspiciously.
 
ray wrote:



> On Sat, 26 Jun 2010 16:28:49 -0400, Big 666 wrote:

>

>> ray wrote:

>>> This is too funny:

>>> ======================================== undisclosed wrote:

>>>> Hello Everyone,

>>>>

>>>> I am running windows 7 and I have been on windows 7 for at least 2

>>>> months. However, I am getting a blue screen error and do not know

>>>> what to do. Please provide some input to a solution. Thank you

>>>>

>>>>

>>>> Problem signature:

>>>> Problem Event Name: BlueScreen

>>>> OS Version: 6.1.7600.2.0.0.256.1

>>>> Locale ID: 1033

>>>>

>>>> Additional information about the problem: BCCode: 50

>>>> BCP1: FFFFFA90063598D0

>>>> BCP2: 0000000000000000

>>>> BCP3: FFFFF88004F667B7

>>>> BCP4: 0000000000000005

>>>> OS Version: 6_1_7600

>>>> Service Pack: 0_0

>>>> Product: 256_1

>>>>

>>>> Files that help describe the problem:

>>>> C:\Windows\Minidump\062610-33181-01.dmp

>>>> C:\Users\JT\AppData\Local\Temp\WER-53757-0.sysdata.xml

>>>>

>>>> Read our privacy statement online:

>>>> 'Windows 7 Privacy Statement - Microsoft Windows'

>>>> (http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409)

>>>>

>>>> If the online privacy statement is not available, please read our

>>>> privacy statement offline:

>>>> C:\Windows\system32\en-US\erofflps.txt

>>>>

>>>>

>>>> ----------------------------------------------------------- I

>>>> downloaded blue screen view and came up with this below I do not know

>>>> what all this problematic stuff means from bluescreenview.

>>>>

>>>>

>>>> 062610-33181-01.dmp 6/26/2010 10:58:39 AM

> PAGE_FAULT_IN_NONPAGED_AREA

>>>> 0x00000050

>>> fffffa90`063598d0 00000000`00000000 fffff880`04f667b7

> 00000000`00000005

>>> nvlddmkm.sys nvlddmkm.sys +13b970

> x64 C:\Windows

>>> \Minidump\062610-33181-01.dmp 2 15 7600

>>>> 062610-37299-01.dmp 6/26/2010 10:45:01 AM 0x00000124

>>>> 00000000`00000000

>>> fffffa80`050c7038 00000000`b2000040 00000000`00000800 hal.dll

>>> hal.dll+12903 x64 C:

>>> \Windows\Minidump\062610-37299-01.dmp 2 15 7600

>>>>

>>>>

>>>> BELOW WAS HIGHLIGHTED IN PINK

>>>>

>>>>

>>>> ntoskrnl.exe ntoskrnl.exe+ef801 fffff800`02a4c000

>>> fffff800`03028000 0x005dc000 0x4b88cfeb 2/27/2010

>>>> 3:55:23 AM Microsoft® Windows® Operating System NT Kernel & System

>>>> 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation

>>>> C:\Windows\system32\ntoskrnl.exe nvlddmkm.sys nvlddmkm.sys

> +13b970

>>>> fffff880`04ac2000

>>> fffff880`055e5180 0x00b23180 0x4ac791b5 10/3/2009

>>>> 2:02:29 PM

>>>>

>>>>

>>>>

>>> The "0x00000050 nvlddmkm.sys" tells you your Nvidia graphics driver is

>>> falling over. Use your search engine with that as a search term, to see

>>> examples of what other people have tried.

>>>

>>> You can try a different driver.

>>>

>>> Or you can review your hardware test strategy. For example, if you

>>> build your own computer, use memtest86+ and Prime95 stress test, to

>>> verify the CPU and RAM are properly adjusted and stable. Some people

>>> never had a stable hardware platform to begin with, and the symptoms

>>> can be one blue screen after another, with different error messages

>>> each time. If you are seeing relatively random errors, it could be a

>>> CPU/memory adjustment. If the errors stay within nvlddmkm.sys, it is

>>> also possible the graphics card is about to croak. If you have a super

>>> high powered graphics card, it might even be overloading the PSU at

>>> peak 3D play. In terms of hardware reasons, you've got a few things to

>>> consider.

>>>

>>> Before jumping to any conclusions, have a look at all your bluescreen

>>> errors to date, and see if they're random, or always the same error

>>> (i.e. always the same driver file). That kind of info can help you

>>> choose a strategy to fix it.

>>>

>>> Paul

>>> ===============================================================

>>>

>>> You're kidding me, right? "have a look at all your bluescreen errors"

>>> - and this is the best MS can do?

>>

>> What a guy, what a saint and the snake in the grass he really is about.

>

> Well, excuse me. It's simply that I have not had the equivalent of a

> bluescreen in the 12 years I've been using Linux. Quite frankly, it makes

> it sound like that is still quite common in the MS world.



Bullshit.

With Linux, there is no Blue Screen, just a completely frozen PC where

only the power button will get you out.



Apparently you haven't used Windows in 12 years.



--

Vita brevis breviter in brevi finietur,

Mors venit velociter quae neminem veretur.
 
So much for your character complaing about the 3 Alias and

Myself.



I'm not a retard that will pull posts from COLA into the

Windows7 group like this thread here....5 of them actually.

You decided to reply, then added the Win7 group to it ?



So you saying.......



"Ron Bambi you can go stand in front of headlights, instead of

licking up someone's COLA droppings."



"This is not Frank you dumb *******, and I know the kind of

low-life man you really are Raytard. You'll knife a person in

the back the first opportunity you'll get. I wouldn't want to

be in a foxhole with you."



"Appreciate -- Raytard. Your problem Raytard is that you got

caught with your pants on the ground and your ass in the air,

looking like fool with your pants on the ground."



........shows how upstanding you are and appalled by name-

calling and the like ????



To me, it looks like your a two-face rat ******* preaching one

thing and doing another.......just like Frank.
 
DanS wrote:



>So much for your character complaing about the 3 Alias and

>Myself.

>

>I'm not a retard that will pull posts from COLA into the

>Windows7 group like this thread here....5 of them actually.

>You decided to reply, then added the Win7 group to it ?

>

>So you saying.......

>

>"Ron Bambi you can go stand in front of headlights, instead of

>licking up someone's COLA droppings."

>

>"This is not Frank you dumb *******, and I know the kind of

>low-life man you really are Raytard. You'll knife a person in

>the back the first opportunity you'll get. I wouldn't want to

>be in a foxhole with you."

>

>"Appreciate -- Raytard. Your problem Raytard is that you got

>caught with your pants on the ground and your ass in the air,

>looking like fool with your pants on the ground."

>

>.......shows how upstanding you are and appalled by name-

>calling and the like ????

>

>To me, it looks like your a two-face rat ******* preaching one

>thing and doing another.......just like Frank.



The cola Wintrolls are ****, basically. Plonk them all, and you'll

miss nothing of value.



--

"There are loads of fat smelly basement dwellers with greasy hair and

pizza crumbed beards who use dumpster HW in the Linux community." -

"True Linux advocate" Hadron Quark
 
DanS wrote:

> calling and the like ????

>

> To me, it looks like your a two-face rat ******* preaching one

> thing and doing another.......just like Frank.

>



You had best see if you can handle Frank as he pushes your button to

hell and back. You can't push my button. I have pushed your button, so

here is the result of the button pushed, as you go off the deep-end. :p
 

Similar threads

T
BSOD fails with my new computer need help!!!
Replies
0
Views
109
thetravis0916
T
U
Blue Screen- Dont know what to do!
Replies
12
Views
436
Dave
D
N
Blue screen - DRIVER POWER STATE FAILURE
Replies
0
Views
38
NewsBot
N
C
0xA ntoskrnl.exe BSOD
Replies
0
Views
58
Cyberat
C
N
I get a BSOD every time I press the side buttons of my Razer Naga
Replies
0
Views
53
NewsBot
N
Back
Top