BSOD numerous different messages even after a fresh install of win7

[monkey314]

So I've had my computer running fine for about a year and a half. No problems other than a really slow start time. I've always had a random stutter/freeze/looping audio problem that will last for a second and it wouldn't matter what I was doing. Would happen about once every three hours or so. So about a month ago I would get blue screens with various different messages. During each blue screen I would get artifacts and the looping audio situation (during the blue screen). I even got a blank blue screen.

Three times I got a blue screen after a message popped up about ati's CCC failed to do something (couldn't read it fast enough). And one of those times I even got a blank blue screen. After the blue screen my computer would restart and 50% of the time it would assumingly fail post and my motherboard speaker would beep rapidly, no pattern. If the restart did succeeded I would start windows normally. 75% it would fail and do a restart. Turning off the computer completely (flipping the switch on the PSU) for failed starts will have a successful start chance of about 90%. When windows failed to start it does the "starting windows". Eventually the colored balls show up and form the windows logo. Goes to black for about 40-60 seconds (it normally does this) and then I'm met with the logon screen. When it fails it goes to black for about 20 seconds then reboots with the motherboard logo with the boot options. And occasionally when it reboots the motherboard beeps with no pattern. Just very rapid beeping.

I ran memtest86 and it said everything was fine. So I just left my computer running and never shut it down in fear of it never starting again. It ran for weeks no problems. I did everything I normally did (hours of gaming included). No problems. I tried playing a demo on steam and all three times within two minutes of playing the game I would get a blue screen (IRQL driver) I decided it was time for a fresh install because maybe something in the registry is messed up from all the installs and uninstalls.

I did a fresh reinstall of windows 7 64 home professional so far everything was running great when it crashed after playing TF2 for 10 minutes with a blue screen "fault in page in a nonpage area". I did a memtest that's available in the windows repair/recovery and it said there was a hardware error after only 6% of completion. So I took out all my stick of RAM except for one and am running on that for now(I have no idea if that's the real problem).

I have yet to see any real definitive pattern. Event viewer only comes up with kernel power, event id 41, task category (63) every single time. THERE HAVE BEEN NO HARDWARE CHANGES.

I attached my zip file created from the BSOD instructions page.

Please help. My computer and my car are the only thing I own of value and I need my computer for college (I have computer related summer classes)

Thank you

 

[writhziden]

Problem Devices:

Universal Serial Bus (USB) Controller	PCI\VEN_1033&DEV_0194&SUBSYS_50071458&REV_03\4&304316D0&0&00E2	The drivers for this device are not installed.
Ethernet Controller	PCI\VEN_10EC&DEV_8168&SUBSYS_E0001458&REV_06\4&43FAD29&0&00E1	The drivers for this device are not installed.

The above drivers should be included with your motherboard support. Check your motherboard support site for the most up to date versions. If you need help, and even if you do not, we recommend filling in your system specs on your profile (not in a post in this thread). http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html can help with filling in the system specs.


Security Software: ??? I recommend either of these two setups:

• Microsoft Security Essentials - Free Antivirus for Windows
  
  
• http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

Download and install the security setup of your choice, update the software, and then run a full scan of your system for viruses and malware. If you only install MSE, I would also suggest installing and updating Malwarebytes : Free anti-malware, anti-virus and spyware removal download, but do not start the free trial/full version of Malwarebytes. Run a full scan with Malwarebytes after updating it. Post back the results.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\monkey314\Windows_NT6_BSOD_jcgriff2\042812-42993-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02a50000 PsLoadedModuleList = 0xfffff800`02c8de70
Debug session time: Sat Apr 28 11:50:37.881 2012 (UTC - 6:00)
System Uptime: 0 days 0:28:53.239
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff30015b7f7f0, 1, fffff80002ac5a07, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheckWithHint+d7 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff30015b7f7f0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ac5a07, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf80e0
 fffff30015b7f7f0 

FAULTING_IP: 
nt!SeAccessCheckWithHint+d7
fffff800`02ac5a07 c684249000000001 mov     byte ptr [rsp+90h],1

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  TeraCopy.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880080975a0 -- (.trap 0xfffff880080975a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a007c2302c rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88008097a0c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ac5a07 rsp=fffff88008097730 rbp=fffffa800dae8030
 r8=fffff88008097a28  r9=fffffa800dae8001 r10=fffff88008098770
r11=fffff88008097808 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!SeAccessCheckWithHint+0xd7:
fffff800`02ac5a07 c684249000000001 mov     byte ptr [rsp+90h],1 ss:0018:fffff880`080977c0=10
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b3f729 to fffff80002ac05c0

STACK_TEXT:  
fffff880`08097438 fffff800`02b3f729 : 00000000`00000050 fffff300`15b7f7f0 00000000`00000001 fffff880`080975a0 : nt!KeBugCheckEx
fffff880`08097440 fffff800`02abe6ae : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ccb
fffff880`080975a0 fffff800`02ac5a07 : 00000000`00000000 00000028`00000030 00000000`00000000 fffffa80`0c070c40 : nt!KiPageFault+0x16e
fffff880`08097730 fffff880`012c2e33 : fffff8a0`07c2302c fffff8a0`07c2302c fffff8a0`07c23010 fffffa80`07822180 : nt!SeAccessCheckWithHint+0xd7
fffff880`08097810 fffff880`012c49e7 : fffffa80`0dae8010 00000000`00000000 fffff8a0`115d1010 00000000`00000080 : Ntfs!TxfAccessCheck+0x123
fffff880`08097980 fffff880`012b3573 : fffffa80`0cdb7010 fffff880`080983b0 fffff8a0`115d1010 fffff8a0`21025510 : Ntfs!NtfsAccessCheck+0x1b7
fffff880`08097b60 fffff880`012b3d73 : fffff880`080983b0 fffff8a0`115d1010 00000000`00000002 fffff880`01057001 : Ntfs!NtfsCheckExistingFile+0xc3
fffff880`08097bf0 fffff880`012b06ef : fffff880`080983b0 00000000`00000000 fffff880`02fd5180 fffffa80`00000094 : Ntfs!NtfsOpenExistingAttr+0x73
fffff880`08097cb0 fffff880`012b0eff : fffffa80`0cdb7010 fffffa80`079e1c10 fffff8a0`115d1450 fffff880`00000094 : Ntfs!NtfsOpenAttributeInExistingFile+0x50f
fffff880`08097e40 fffff880`012c1e76 : fffffa80`0cdb7010 fffffa80`079e1c10 fffff8a0`115d1450 00000000`02734501 : Ntfs!NtfsOpenExistingPrefixFcb+0x1ef
fffff880`08097f30 fffff880`012bc28d : fffffa80`0cdb7010 fffffa80`079e1c10 fffff880`08098110 fffff880`08098158 : Ntfs!NtfsFindStartingNode+0x5e6
fffff880`08098000 fffff880`01225c0d : fffffa80`0cdb7010 fffffa80`079e1c10 fffff880`080983b0 fffff8a0`21bcfc00 : Ntfs!NtfsCommonCreate+0x3dd
fffff880`080981e0 fffff800`02acfcda : fffff880`08098320 fffff8a0`115d1140 fffffa80`07822180 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`08098210 fffff880`01225b2f : fffff880`01225bf0 fffff880`08098320 fffff880`08098300 fffff880`012c732d : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`080982f0 fffff880`012c29c0 : 00000000`00000000 00000000`00000000 fffff880`08098540 fffffa80`079e1c10 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
fffff880`08098350 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsFsdCreate+0x1b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!SeAccessCheckWithHint+d7
fffff800`02ac5a07 c684249000000001 mov     byte ptr [rsp+90h],1

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!SeAccessCheckWithHint+d7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0x50_nt!SeAccessCheckWithHint+d7

BUCKET_ID:  X64_0x50_nt!SeAccessCheckWithHint+d7

Followup: MachineOwner
---------

The above crash was caused by TeraCopy. Recommend uninstalling the software through Start Menu -> Control Panel -> Uninstall a program.

 

[monkey314]

I did everything you said. I removed teracopy, even though I can't believe it's the culprit; been using it for years without blue screens. MSE is installed again (fresh install of win 7). Updated the drivers.

And as an FYI nothing on my system is overheating. Everything stays well under 60C. Even my previously overclocked (blue screens occasionally reset my BIOS settings for my processor) processor stayed under 70C when running prime95.

I can run a full stress test tomorrow after my finals are over.

 

[writhziden]

If TeraCopy is not at fault, then you have hard disk errors, data corruption, or a hard disk controller issue. It could also be a bad connection between the hard disk and motherboard. NTFS on the stack in the crash usually indicates one of these scenarios if it is not being caused by a program like TeraCopy or if it is not caused by backup software/3rd party defrag software. I should also mention, NTFS can be on the stack due to a virus or malware installed on the system.

If you check your hard disk connections... As you add and remove hardware, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[monkey314]

I've gotten roughly 4 different blue screens messages (even a completely one). I should have put the dump files up here on the site before reinstalling windows, but oh well. I'm currently running on 4GB of RAM instead of 8GB. I got a hardware error when running a memtest through windows repair (even though memtest86 didn't detect any problems a week prior). The fact that I've had so many blue screens just out of the blue (ha ha ha) makes me lean toward a hardware issue.

I'll be stressing out my PC tomorrow, today I'm stressing about exams.

Thanks for your time

 

[writhziden]

You're welcome.

I understand the stress with exams as I am a student myself. Best of luck with those. Let us know how things go as you progress. You can run tests at whatever pace you need to for them not to interfere with life. I'll be subscribed to the thread as you go.

 

[monkey314]

So far so good, but like I said in my first post my computer would run for weeks no problems so I won't know for sure for a while. I ran Skyrim and TF2 no problems. I reinstalled teracopy (it's soooooooo much better than default explorer file mover). I remember that when I first installed it I got the message saying windows believes this program incorrectly and I just ignored it.

I'm also running on 2 sticks of RAM rather than my full 4 sticks. So that could have been problem (bad RAM slot or stick). I would also like to find out why it takes sooooo long to boot. Anywhere from 4-7 minutes. It's been this way since the beginning.

 

[writhziden]

The only simple method I know of to decrease boot time is http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html.

If that does not help, check your BIOS settings for AHCI versus IDE mode. SATA drives run faster in AHCI mode.
NOTE: AHCI mode can decrease stability of the system in some cases.


You may also look at http://www.sevenforums.com/tutorial...ws-7-a.html?filter[2]=Performance Maintenance for speeding up boot time.

 

[monkey314]

Well I screwed up. I switched to ahci and back to ide. Now it just sits at "loading operating system"... F*CK.

I feel sick. GUH. Please don't tell my I really screwed myself...

 

[monkey314]

ok... now it won't even get to the motherboard screen. There's no post beep. what the hell. ****. oh man i'm physically ill right now...

 

[writhziden]

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves. Then add one piece of hardware back at a time until the problem re-occurs. Take notes of what hardware you add and how the system responds to the hardware changes.

As you add and remove hardware, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

Once these steps have been followed, it is safe to remove and replace components within your computer.


The above probably will not get Windows to start. Windows has issues when switching from AHCI to IDE, but it does not have issues when switching from IDE to AHCI. You will likely have to re-install at this point. We can help you backup your data first, but it is more important to get your computer to POST before worrying about Windows.

 

[monkey314]

ok so it wouldn't do anything because i thought I changed my CPU frequency back to default, but I didn't. will an image I made two days ago solve this problem with the ahci problem? why did I have to mess with it...

 

[monkey314]

My computer will get past boot, but i'm still stuck with the ahci problem.

thanks for you help

 

[writhziden]

Sorry, I remembered backwards. The IDE to AHCI switch requires a registry change before it can be applied.

The AHCI to IDE switch typically does not affect Windows. If you switch back to IDE, a system image should take care of it. If you want, you can re-install Windows and see if AHCI provides a performance boost.

 

[monkey314]

I did a restore and everything is good! oh shit man... I'm a grown man and on the verge of tears and vomiting when my computer wouldn't even get past post.

thank you so much for being there at least; I'm ever so grateful.

 

[writhziden]

You running with IDE or AHCI?

And no problem for the help/support. That's why we're here.

 

[monkey314]

I was running ide, I switched to achi. Saw a whole bunch of crap I never saw before and then it got to loading operating system and it just sat there for two minutes. So I switched back to ide and it also just sat there. I tried several repairs with my repair disk and they both said they failed. Then i messed with bois. Then it wouldn't even boot. *tears* Then i got a message saying errors cause of overclocking (I thought i changed them back to default, but I guess not). Changed my cpu multiplier again. Then it booted fine and i did a system restore to last night and everything is good so far.

HALLELUIAH. Believe it or not today is my birthday and I was so close to having an epic meltdown. Making an image backup right now.

 

[writhziden]

Huh, my birthday is in eight days. Anyway, good luck with the backup and keep us posted whether you need help afterward.

 

[monkey314]

My RAM timings and frequency changed... why God, why?

 

[writhziden]

Had you changed them before? Load Setup Defaults in the Exit screen of the BIOS. That should set them back to nominal.