SRL Archive - General Botting Help

Not sure if this is the correct section, sorry if it isn't.
Havent had this problem before today.
Started using a new script and when ever I stop it and restart it my computer will either restart or blue screen of death.
Has anyone had this problem or no the fix?

You should probably tell which script it is, there may be something malicious in it. I don't think I've ever gotten the BSOD from running any script.

From: Neva Banned
Not sure if this is the correct section, sorry if it isn't.
Havent had this problem before today.
Started using a new script and when ever I stop it and restart it my computer will either restart or blue screen of death.
Has anyone had this problem or no the fix?

You sure your video drivers are ok and rs doesnt crash in browser? I had once problems because instead of nvidia drivers there were 2 integrated hd drivers and windows 7 kept rewriting them over(with the wrong ones). But it was crashing no matter what i did, even doing nothing crashed :( Dont exzactly remember how i solved but i think through safe mode deleted all old ones and installed good ones and turned automatic updates off.

Get BlueScreenViewer and post the minidump.

sounds like ram or vram of gpu or gpu driver if that's exactly what happened tbh..

prob opengl crash driver

I cant get it to crash again because I never let a bsod fully dump. I am thinking everyone that said video driver is correct. There isn't anything malicious in the script I have gone through it multiple times and modified it a bit.

Here is what it did dump, I already used windows debugger but I didn't let it dump enough to show the culprit.

==================================================
Dump File : 020215-6406-01.dmp
Crash Time : 2/2/2015 8:12:05 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000018
Parameter 2 : 00000000`00000000
Parameter 3 : ffffd000`206a5180
Parameter 4 : 00000000`00000003
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14dca0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.3.9600.16452 (winblue_gdr.131030-1505)
Processor : x64
Crash Address : ntoskrnl.exe+14dca0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\020215-6406-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 262,144
Dump File Time : 2/2/2015 8:12:41 PM
==================================================

Caused By Driver : ntoskrnl.exe

wow thanks windows, now we know almost anything caused it!


do you have mcafee? that's a common cause

other than that any driver / bad memory can also cause.

I dont use antivirus and since I can't force it to happen again I have no clue, it happened 5 times last night, after the 4th time I updated my gpu driver and java which still didnt fix it. Thanks for all the help, and next time it happens I will let it fully dump.

Thanks all

Does the BSOD happen only when you start a stop a script or does it happen anywhere else? Also have you overclocked your CPU?

From: Neva Banned
I cant get it to crash again because I never let a bsod fully dump. I am thinking everyone that said video driver is correct. There isn't anything malicious in the script I have gone through it multiple times and modified it a bit.

Here is what it did dump, I already used windows debugger but I didn't let it dump enough to show the culprit.

snip

ntoskernel is the operating system itself, with which exactly a billion things could go wrong, so without the full log we're kinda stuck - get it to crash again and let it do a full dump

With just the minidump telling us it was a kernel panic and nothing else, it would be any number of things: RAM, video card, bad drivers, etc

You could try benching each of your components to see if anything fails, in the case that it does remember to save the full dump

From: Smidqe
Does the BSOD happen only when you start a stop a script or does it happen anywhere else? Also have you overclocked your CPU?

My I7 3770k is oced to 4.5ghz but I have stress tested it for 24 hours no flaws. It only happens when I start the script. I haven't had it happen again though, so I guess w/e was crashing fixed itself.

From: Neva Banned
My I7 3770k is oced to 4.5ghz but I have stress tested it for 24 hours no flaws. It only happens when I start the script. I haven't had it happen again though, so I guess w/e was crashing fixed itself.

yea I doubt it's a CPU overclock those rarely cause BSODs and more likely just shut down the system or the CPU just stops running at "max" they're so advanced these days

GPU's on the other hand… lol

but yea was probably just the driver.. GPU problems all over

I was able to force it to crash again but there wasn't any bsod, I am pretty sure its the gpu driver, I don't think removing all old drivers and most recent then reinstalling it will fix it. If it keeps happening I will just run it in a virtual machine that way the virtual machine is the only thing that should crash hopefully. Thanks for everyone trying to help me sort this out.

I am still thinking it's a unstable overclock.

0x00000101 BSOD code directs straight to CPU, not GPU. It's one of the few BSOD error codes that have a straight solution. Increase your v-core, and then test again by starting a script.

I had OC'd my i7 920 to 3.8GHz (stock 2.67Ghz) and sometimes it would BSOD with same error (0x00000101). What was more puzzling was the BSOD's were not consistent, it would crash while browsing or gaming instead of during stress testing. I had to increase v-core to 1.27 from 1.2675 (stock 1.25) to get it rock-solid.

@grats;
Sarcasm?

Overclocking always causes trouble, from BSOD to freezing and overheating until you find stable settings. Example you gave was just thermal throttling that occurs when CPU temps reach too high due to bad cooling and is not directly related to overclocking. Since OP has stress tested for 24 hours the thermal throttling can be excluded from this.

I'd try
A. remove bloat-ware
B. make sure script doesn't handle lower memory, usually for os, or write to read only memory
C. open command prompt as root, type "verifier", hit enter

From: Smidqe
I am still thinking it's a unstable overclock.

0x00000101 BSOD code directs straight to CPU, not GPU. It's one of the few BSOD error codes that have a straight solution. Increase your v-core, and then test again by starting a script.

I had OC'd my i7 920 to 3.8GHz (stock 2.67Ghz) and sometimes it would BSOD with same error (0x00000101). What was more puzzling was the BSOD's were not consistent, it would crash while browsing or gaming instead of during stress testing. I had to increase v-core to 1.27 from 1.2675 (stock 1.25) to get it rock-solid.

@grats;
Sarcasm?

Overclocking always causes trouble, from BSOD to freezing and overheating until you find stable settings. Example you gave was just thermal throttling that occurs when CPU temps reach too high due to bad cooling and is not directly related to overclocking. Since OP has stress tested for 24 hours the thermal throttling can be excluded from this.

They still rarely cause bsod. More likely cache of cpu or the clock messing up the memory it writes.

Now that he says it crashed again without bsod it sounds more hardware related than software and could even be 0 something simple like heat problem. So now try the overclock imo