I need help. Every time I try to play a game that isn't 1.6 or source I my monitors power down and my computer locks up. On restart I get an error like this:

Problem signature:
Problem Event Name: BlueScreen
OS Version:

Additional information about the problem:
BCCode: 101

I was getting a BCCode 116, but I uninstalled and reinstalled GPU drivers and that seemed to fix it that error.

Also I tried uninstalling my USB soundcard and it BSOD'd on me.

Help please! I just want to play Tribes and LoL.

what operating system? how much memory? what kind of video card? we need more info than this to help you out.

Also are you overclocking? From what ive read its a Vcore issue which means your cpu isnt getting enough voltage... It could also be a memory issue. You havent screwed around with the voltage or timings in the BIOS have you?

Make sure your CPU temp isnt getting to high. make sure the fan on the healsink is spining and make sure there isnt a bunch of dust and shit in between the blades on your heatsink.



Also:

Download BlueScreenView (in Zip file)
http://www.nirsoft.net/utils/blue_screen_view.html

No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Manufacturer:
Dell
OS:
Windows 7 64-bit
CPU:
2.66 GHz i7
Memory:
6 GB
Hard Drive:
640 GB
Video Card:
GT 220
Sound Card:
Creative X-Fi USB
Monitor:
ViewSonic G90fB

Also IDK if this helps, but I tried to uninstall the drivers for the USB soundcard and I got a BSOD error as well.


I also just cleaned all the dust from the computer and that lowered the temp inside. I thought that might have been the problem, because it did run a little hot, but I brought the temp down with no fix, and I have cold air coming from both sides of the tower.


--------------------------------------

From the minidump .dmp folder

MODULE_NAME: nt

FAULTING_MODULE: fffff8000305b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`035e73f8 fffff800`0312f8c9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`031d5180 : nt+0x7cc40
fffff880`035e7400 00000000`00000101 : 00000000`00000019 00000000`00000000 fffff880`031d5180 00000000`00000003 : nt+0xd48c9
fffff880`035e7408 00000000`00000019 : 00000000`00000000 fffff880`031d5180 00000000`00000003 33b933b9`eecceecc : 0x101
fffff880`035e7410 00000000`00000000 : fffff880`031d5180 00000000`00000003 33b933b9`eecceecc 00000003`00000000 : 0x19


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

Looks like a driver / corrupted file?

ntoskrnl.exe is a windows OS file.





step ahead of you...
I cleaned all the dust from my pc carefully, fans are spinning fast and I can feel cold air coming from the sides of the tower.
I've uninstalled the nvidia drivers and reinstalled them, and I no longer get BCCode 116, but I'm getting BCCode 101 now. I also just updated my BIOS, but I'm not sure if that has fixed it yet, I have yet to launch a game that crashes.

I can't adjust the vcore because I have a locked bios, and I'm not OCing anything.


Should I try taking my RAM out and making sure it's in right? I have 6 1GB DDR2 sticks.




I just find it weird it isn't BSODing on CS 1.6 / source.

What motherboard do you have? Can you try going to the BIOS manufacturer's website to see if there is a newer version that you can flash?

Your RAM placement is fine. If there was a contact issue it would've given you the beeps and the POST would've failed.

Also, try disconnecting everything except the bare essentials (keyboard & mouse, monitor) and try with just 1 stick of RAM in.

Motherboard is Dell Inc, 0R849J. I have the latest drivers and chipset drivers.

I really don't think it's a hardware problem, I am pretty sure it has to do with some sort of software gltich that has to do with: IMAGE_NAME: ntoskrnl.exe

It's hard to say if it's a hardware or software issue. You can try to eliminate the software suspect by getting into the windows recovery console (by booting from a windows cd), and running "chkdsk /r".

will try that later thanks.

chkdsk only checks NTFS integrity; he'd have other symptoms if this were filesystem corruption.

Good point. For a moment I forgot that he can boot into windows fine.

If the ntoskrnl file is truly corrupt, it might be worth a try to do a windows repair install or just make a backup of the file and replace the file from another working pc.

Maybe debugging the stack trace text via windows debugger will give some more info.

english (for athat last part)

Install windows debugging tool and generate a log of the dump file (located in c:\windows\Minidump\), and post it here.

Instructions to install it and generate the log - http://www.windowsbbs.com/general-discu ... tions.html

*Edit - Actually you don't need to. Geno's dump reader seems to be much better at giving some easier to understand info. I've only used windows debugging tool. But I'm curious to see what it shows.

I did, and I posted it above with the !analyze -v command.

Alright, there is no process name mentioned in the log, so it is definitely a hardware issue.

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC relates to the cpu.

Did you flash your bios to make sure it's the latest version? You need to get a BIOS update (it's different from a motherboard driver update) from Dell's website for your model. Once that is done, run Prime95 to stress test your cpu (http://www.mersenne.org/).

I updated my bios, and if you do a search in windows the file is there multiple times.

I was reading a few forums last night about this, and even at stock sometimes i7s still need more voltage. The vcore sounds like the most logical solution to deal with atm.

I have no idea to set it. I doubt it's even possible with a locked bios.

State, did you run Prime95? Do a CPU stress test and see if it crashes with any failure messages. If it does, the cpu is the culprit.

Don't increase the voltage for now even if you can. On the consumer Dell machines, everything is set together to work at the default configuration. Increasing the voltage in all likelihood will just increase the temps and make everything unstable.