Recent build has given me nothing but headaches - trouble shooting advice needed

Hello all, I just built a new machine a few months ago, I'm having 3
problems that I haven't been able to figure out a solution to. These
are the specs:

Biostar TZ68A+ mobo
Core i5 2500
2 x 4gb Mushkin Enhanced Silverline ram
EVGA GeForce GTX560
90gb Mushkin Chronos SSD
Windows 7 Home Premium x64


- I'm getting blue screens and I can't figure out the cause. I ran
Memtest on both sticks of RAM overnight - no errors. I took out the
SSD and replaced it with a brand new hard drive. I replaced the dvd
drive with a brand new one. I took out the video card and ran the
monitor off the cpu. I tried a different PSU. The drivers I have
installed are all up to date. I installed the most recent version of
Ubuntu and ran that for a couple weeks and didn't have any problems,
so it doesn't look like defective hardware is the problem. Every blue
screen I've had (more than 50 times), with no exceptions, happened
within 5-10 minutes after booting the machine. If I don't get a blue
screen within 5 or 10 minutes after booting then it doesn't happen.

- svchost.exe (LocalServiceNetworkRestricted) is showing 40-60% CPU
usage 100% of the time. I know the problem is LAN driver related
because it went down to 0% after uninstalling the LAN drivers. I
reverted back to the driver that shipped with the motherboard. That
didn't help. I tried an old Linksys network card I had laying around
and that does the same thing. I booted into safe mode with networking
and it didn't do this in safe mode. The CPU stays near 0%.

- I'm having problems with permissions. I installed Avira AV, tried
renaming the licence file so I could copy over the most recent one and
I'm being told that I need permission from Administrators to rename
the file. The account I'm using IS an administator account. So I
unlocked the hidden administrator account and logged into that and I
still get the same message. The most privileged user account you can
possibly use is being denied the right to rename files?? Yet I'm
allowed to install programs and make changes to the registry? This
makes no sense.


I've installed Windows 4 times since I built this machine. The blue
screen problem is the only constant. The other problems never happened
until this most recent time re-installing (a few days ago). If anyone
has any suggestions I would be grateful, I've run out of ideas.

Jon

On 18/09/2012 12:56, wrote:
Hello all, I just built a new machine a few months ago, I'm having 3
problems that I haven't been able to figure out a solution to. These
are the specs:

Biostar TZ68A+ mobo
Core i5 2500
2 x 4gb Mushkin Enhanced Silverline ram
EVGA GeForce GTX560
90gb Mushkin Chronos SSD
Windows 7 Home Premium x64


- I'm getting blue screens and I can't figure out the cause. I ran
Memtest on both sticks of RAM overnight - no errors. I took out the
SSD and replaced it with a brand new hard drive. I replaced the dvd
drive with a brand new one. I took out the video card and ran the
monitor off the cpu. I tried a different PSU. The drivers I have
installed are all up to date. I installed the most recent version of
Ubuntu and ran that for a couple weeks and didn't have any problems,
so it doesn't look like defective hardware is the problem. Every blue
screen I've had (more than 50 times), with no exceptions, happened
within 5-10 minutes after booting the machine. If I don't get a blue
screen within 5 or 10 minutes after booting then it doesn't happen.

- svchost.exe (LocalServiceNetworkRestricted) is showing 40-60% CPU
usage 100% of the time. I know the problem is LAN driver related
because it went down to 0% after uninstalling the LAN drivers. I
reverted back to the driver that shipped with the motherboard. That
didn't help. I tried an old Linksys network card I had laying around
and that does the same thing. I booted into safe mode with networking
and it didn't do this in safe mode. The CPU stays near 0%.

- I'm having problems with permissions. I installed Avira AV, tried
renaming the licence file so I could copy over the most recent one and
I'm being told that I need permission from Administrators to rename
the file. The account I'm using IS an administator account. So I
unlocked the hidden administrator account and logged into that and I
still get the same message. The most privileged user account you can
possibly use is being denied the right to rename files?? Yet I'm
allowed to install programs and make changes to the registry? This
makes no sense.


I've installed Windows 4 times since I built this machine. The blue
screen problem is the only constant. The other problems never happened
until this most recent time re-installing (a few days ago). If anyone
has any suggestions I would be grateful, I've run out of ideas.

Jon

Download this program:

http://www.nirsoft.net/utils/blue_screen_view.html

I did and it sorted out my BSD's, as it tells you what driver is causing
the problem.

wrote:

Biostar TZ68A+ mobo Core i5 2500 2 x 4gb Mushkin Enhanced
Silverline ram EVGA GeForce GTX560 90gb Mushkin Chronos SSD
Windows 7 Home Premium x64


- I'm getting blue screens and I can't figure out the cause. I
ran Memtest on both sticks of RAM overnight - no errors. I took
out the SSD and replaced it with a brand new hard drive. I
replaced the dvd drive with a brand new one. I took out the
video card and ran the monitor off the cpu. I tried a different
PSU. The drivers I have installed are all up to date. I
installed the most recent version of Ubuntu and ran that for a
couple weeks and didn't have any problems, so it doesn't look
like defective hardware is the problem. Every blue screen I've
had (more than 50 times), with no exceptions, happened within
5-10 minutes after booting the machine. If I don't get a blue
screen within 5 or 10 minutes after booting then it doesn't
happen.

- svchost.exe (LocalServiceNetworkRestricted) is showing 40-60%
CPU usage 100% of the time. I know the problem is LAN driver
related because it went down to 0% after uninstalling the LAN
drivers. I reverted back to the driver that shipped with the
motherboard. That didn't help. I tried an old Linksys network
card I had laying around and that does the same thing. I booted
into safe mode with networking and it didn't do this in safe
mode. The CPU stays near 0%.

I've installed Windows 4 times since I built this machine. The
blue screen problem is the only constant. The other problems
never happened until this most recent time re-installing (a few
days ago). If anyone has any suggestions I would be grateful,
I've run out of ideas.

This is another good reason to make incremental backups when
installing Windows, using Macrium Reflect. That way, you can
figure out when the problem started during the installation.
Without having to reinstall Windows.

--













Jon

En el artículo ,
escribió:

- I'm getting blue screens and I can't figure out the cause.

No one can begin to help you until you give us the STOP 0xnn error that
comes with the blue screen.

--
(\_/)
(='.'=)
(")_(")

Biostar TZ68A+ mobo
Core i5 2500
...
- I'm getting blue screens and I can't figure out the cause. I ran
Memtest on both sticks of RAM overnight - no errors. I took out the
SSD and replaced it with a brand new hard drive. I replaced the dvd

No overclocking?
What if you used a regular spinning hard disk? Maybe it's the SSD!
Or maybe it's AHCI problem.
Are you using legitimate Windows?

--
@~@ Remain silent. Nothing from soldiers and magicians is real!
/ v \ Simplicity is Beauty! May the Force and farces be with you!
/( _ )\ (Fedora 17 i686) Linux 3.5.3-1.fc17.i686
^ ^ 00:54:01 up 2:17 0 users load average: 0.00 0.01 0.05
�借貸! ��騙! ��交! �打交! �打劫! �自殺! 請考慮綜� (CSSA):
http://www.swd.gov.hk/tc/index/site_...sub_addressesa

On Sep 18, 7:56 am, wrote:
Hello all, I just built a new machine a few months ago, I'm having 3
problems that I haven't been able to figure out a solution to. These
are the specs:

Biostar TZ68A+ mobo
Core i5 2500
2 x 4gb Mushkin Enhanced Silverline ram
EVGA GeForce GTX560
90gb Mushkin Chronos SSD
Windows 7 Home Premium x64

- I'm getting blue screens and I can't figure out the cause. I ran
Memtest on both sticks of RAM overnight - no errors. I took out the
SSD and replaced it with a brand new hard drive. I replaced the dvd
drive with a brand new one. I took out the video card and ran the
monitor off the cpu. I tried a different PSU. The drivers I have
installed are all up to date. I installed the most recent version of
Ubuntu and ran that for a couple weeks and didn't have any problems,
so it doesn't look like defective hardware is the problem. Every blue
screen I've had (more than 50 times), with no exceptions, happened
within 5-10 minutes after booting the machine. If I don't get a blue
screen within 5 or 10 minutes after booting then it doesn't happen.

- svchost.exe (LocalServiceNetworkRestricted) is showing 40-60% CPU
usage 100% of the time. I know the problem is LAN driver related
because it went down to 0% after uninstalling the LAN drivers. I
reverted back to the driver that shipped with the motherboard. That
didn't help. I tried an old Linksys network card I had laying around
and that does the same thing. I booted into safe mode with networking
and it didn't do this in safe mode. The CPU stays near 0%.

- I'm having problems with permissions. I installed Avira AV, tried
renaming the licence file so I could copy over the most recent one and
I'm being told that I need permission from Administrators to rename
the file. The account I'm using IS an administator account. So I
unlocked the hidden administrator account and logged into that and I
still get the same message. The most privileged user account you can
possibly use is being denied the right to rename files?? Yet I'm
allowed to install programs and make changes to the registry? This
makes no sense.

I've installed Windows 4 times since I built this machine. The blue
screen problem is the only constant. The other problems never happened
until this most recent time re-installing (a few days ago). If anyone
has any suggestions I would be grateful, I've run out of ideas.

Jon

I don't know about W7, except its sort of XP and sort of works sort of
more often than not with sorts of new programs [that don't, sort of,
when they see XP]. Other than that, they're identical, but of course.

What I do, as well, know about is the two BIOSTAR MBs I've owned. Not
in your league, though, one goes way back and the newer experience, of
late, was questionable to begin with -- luckily, easily diagnosed for
latter obvious hardware faults (funny that, how retailers
thereuponwith haven't a clue, lose everything, after telling them
exactly WTF's wrong at exactly the time it comes to giving someone
their money back). Suffice to say biostar isn't my first choice these
days. Or, I'd rather be dipped in tar, baby, for feathering.

Somebody already mentioned backups. Realize that as you continue with
and along the lines of things bad, making them badder gets totally
assed until the whole OS system conceivably is buggered into junk.
Time for another OS install. Hence&with.

Onwards to Pain In The Ass. Royal. You'll have to take the
installation down to its simplest terms for W7. Preferably w/o the
fancy graphics, SS hard drive. Reason: to verify either of the two
former are not culprits to Microsoft instability;- the ram modules may
also need optionally checking (try just one), double check your CPU
seating (I'm sure is good) - ALL your hardware BIOS settings/
voltages/speeds and therewithinall potential options as related to
FAILSAFE setting, Defaults for a touch, or AssForward WarpSpeed
Overclocking for BigTime Gamers.

Once stable, start adding back stuff until the problems occur.
Continuing, hobbled, if you can fix it at some compromised below-BSOD
level.

Or, if you can swing it from, apparently, people like Newegg -- pay
shipping back, perhaps restocking for, I dunno, Quanto -- and join
their Happy Club of Reviewers for placing Your Opinion among the 1200
others, or thereabouts, about BioStar, that it's a total piece of crap
and you wished you'd bought a real motherboard from rapidly
diminishing Quality Control, perhaps, while extant.

You can now go back disregard everything above in the case I'm utterly
wrong about virtually everything. Have a happy day anyway, y'hear.

wrote:
Hello all, I just built a new machine a few months ago, I'm having 3
problems that I haven't been able to figure out a solution to. These
are the specs:

Biostar TZ68A+ mobo
Core i5 2500
2 x 4gb Mushkin Enhanced Silverline ram
EVGA GeForce GTX560
90gb Mushkin Chronos SSD
Windows 7 Home Premium x64


- I'm getting blue screens and I can't figure out the cause. I ran
Memtest on both sticks of RAM overnight - no errors. I took out the
SSD and replaced it with a brand new hard drive. I replaced the dvd
drive with a brand new one. I took out the video card and ran the
monitor off the cpu. I tried a different PSU. The drivers I have
installed are all up to date. I installed the most recent version of
Ubuntu and ran that for a couple weeks and didn't have any problems,
so it doesn't look like defective hardware is the problem. Every blue
screen I've had (more than 50 times), with no exceptions, happened
within 5-10 minutes after booting the machine. If I don't get a blue
screen within 5 or 10 minutes after booting then it doesn't happen.

- svchost.exe (LocalServiceNetworkRestricted) is showing 40-60% CPU
usage 100% of the time. I know the problem is LAN driver related
because it went down to 0% after uninstalling the LAN drivers. I
reverted back to the driver that shipped with the motherboard. That
didn't help. I tried an old Linksys network card I had laying around
and that does the same thing. I booted into safe mode with networking
and it didn't do this in safe mode. The CPU stays near 0%.

- I'm having problems with permissions. I installed Avira AV, tried
renaming the licence file so I could copy over the most recent one and
I'm being told that I need permission from Administrators to rename
the file. The account I'm using IS an administator account. So I
unlocked the hidden administrator account and logged into that and I
still get the same message. The most privileged user account you can
possibly use is being denied the right to rename files?? Yet I'm
allowed to install programs and make changes to the registry? This
makes no sense.


I've installed Windows 4 times since I built this machine. The blue
screen problem is the only constant. The other problems never happened
until this most recent time re-installing (a few days ago). If anyone
has any suggestions I would be grateful, I've run out of ideas.

Jon

Blue screen errors, include an error number, and sometimes, the name
of a driver file (if it's a driver file causing the problem). The Stop
codes, are documented here. If the blue screen isn't standing still,
you may be able to disable "automatic restart", so that you can read
the screen. Event Viewer, won't necessary have a copy of the event,
if the crash happens when it can't log stuff.

http://aumha.org/a/stop.htm

SVCHosts running in the OS, can host more than one thing at a time.
So when a SVCHost goes to 100% on one core, you don't know what's doing it.
You have options, like perhaps Process Explorer from Sysinternals -

http://technet.microsoft.com/en-us/s...rnals/bb896653

It's also possible, at least on the older OSes, to move things
in SVCHosts, such that there is one thing per SVCHost. Then,
when a SVCHost goes nuts, you know what caused it. On WinXP,
I can have 15 things hiding in one SVCHost. And with 15 commands
of the type below, I could give each a private SVCHost to use.

http://blogs.msdn.com/b/spatdsg/arch...-services.aspx

You can split it out into its own service by running:

“sc config service type= own”

And revert it via

“sc config service type= share”

But to begin with, I'd work on the Blue Screen information. Look
for a .dmp file or the like. Those sorts of things. It's possible
the answer is in the blue screen, saving some work.

Paul

On Tuesday, September 18, 2012 4:56:17 AM UTC-7, (unknown) wrote:

I'm having 3 problems that I haven't been able to figure
out a solution to. These are the specs:

Biostar TZ68A+ mobo
Core i5 2500
2 x 4gb Mushkin Enhanced Silverline ram
EVGA GeForce GTX560
90gb Mushkin Chronos SSD
Windows 7 Home Premium x64

I'm getting blue screens and I can't figure out the
cause. I ran Memtest on both sticks of RAM overnight -
no errors. I took out the SSD and replaced it with a
brand new hard drive. I replaced the dvd drive with a
brand new one. I took out the video card and ran the
monitor off the cpu. I tried a different PSU. The
drivers I have installed are all up to date. I installed
the most recent version of Ubuntu and ran that for a
couple weeks and didn't have any problems, so it doesn't
look like defective hardware is the problem.

While it could be a Windows driver program problem, it could still be bad hardware because Linux and Windows don't put exactly the same information in the RAM. Also Memtest is lousy because it's a Windows program (unless you pay $15 for the self-booting version) that can't test all the memory, so instead try MemTest86, MemTest86+ (they often give different results, despite being based on the same test methods), and Gold Memory. No one memory diagnostic will find all errors, and I've seen one of those programs report errors when the others did not. In one person's case, it took almost 10 hours for a different diagnostic to find 1 bad bit that other diagnostics missed in days of testing. Also consider testing with known good memory, that is, modules made from chips marked with the logo or part number of a real chip maker, like Samsung, Hynix, Micron, Nanya, Elpida, PowerChip, or ProMOS, and where those markings are easy to read (i.e., no heatsinks covering them).

On Tue, 18 Sep 2012 14:37:10 -0400, Paul wrote:

wrote:

removed


Jon



Blue screen errors, include an error number, and sometimes, the name
of a driver file (if it's a driver file causing the problem). The Stop
codes, are documented here. If the blue screen isn't standing still,
you may be able to disable "automatic restart", so that you can read
the screen. Event Viewer, won't necessary have a copy of the event,
if the crash happens when it can't log stuff.

http://aumha.org/a/stop.htm

SVCHosts running in the OS, can host more than one thing at a time.
So when a SVCHost goes to 100% on one core, you don't know what's doing it.
You have options, like perhaps Process Explorer from Sysinternals -

http://technet.microsoft.com/en-us/s...rnals/bb896653

It's also possible, at least on the older OSes, to move things
in SVCHosts, such that there is one thing per SVCHost. Then,
when a SVCHost goes nuts, you know what caused it. On WinXP,
I can have 15 things hiding in one SVCHost. And with 15 commands
of the type below, I could give each a private SVCHost to use.

http://blogs.msdn.com/b/spatdsg/arch...-services.aspx

You can split it out into its own service by running:

“sc config service type= own”

And revert it via

“sc config service type= share”

But to begin with, I'd work on the Blue Screen information. Look
for a .dmp file or the like. Those sorts of things. It's possible
the answer is in the blue screen, saving some work.

Paul

There are four services hosted by svchost:

DHCP Client
TCP/IP NetBios Helper
Windows Event Log
Windows Audio

svchost right now says 50% CPU usage, DHCP client is hovering around
15% constantly, the other 3 all say 0%. I would have thought that the
combined usage of these four services would be equal to that of
svchost.

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

According to WhoCrashed:


On Wed 9/19/2012 4:59:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-5304-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E8B0C5,
0xFFFFF88005BD3AC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to
privileged code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 11:12:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-7098-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA000BEF9580, 0x0, 0xFFFFF80002F00E1A, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has
been referenced.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 11:11:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-5428-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E99168,
0xFFFFF88009E61900, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to
privileged code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 11:06:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-6973-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0xDE (0x2, 0xFFFFF8A0003A5B30, 0xFFFBF8A0003A5B31,
0x1F9DAB8C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has corrupted pool
memory that is used for holding pages destined for disk.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 11:02:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-13774-01.dmp
This was probably caused by the following module: ntfs.sys
(Ntfs+0x21D5)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS
file system.
The crash took place in a standard Microsoft module. Your system
configuration may be incorrect. Possibly this problem is caused by
another driver on your system which cannot be identified at this time.

On Tue 9/18/2012 4:39:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-4711-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0xA48C0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EFF8C0,
0xFFFFF8800417C488, 0xFFFFF8800417BCE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated
an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 4:38:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-7144-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0xA4830)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F08830,
0xFFFFF88003F7C488, 0xFFFFF88003F7BCE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated
an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 4:29:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-5023-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EE5959,
0xFFFFF88003A8BC60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to
privileged code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 4:18:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-5350-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x8FB5E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002E9BB5E,
0xFFFFF8800350F758, 0xFFFFF8800350EFB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated
an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Tue 9/18/2012 3:13:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-5475-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FAC9BC,
0xFFFFF88007697E30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to
privileged code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Mon 9/17/2012 9:36:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-5413-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AF1E060, 0xFFFFFA800AF1E340,
0xFFFFF800031E6510)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial
to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Mon 9/17/2012 9:26:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-3900-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002EB6EDE, 0x0,
0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program
generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Mon 9/17/2012 1:17:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-4648-01.dmp
This was probably caused by the following module: ntoskrnl.exe
(nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EAC830,
0xFFFFF88003EA4100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to
privileged code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.


On Mon 9/17/2012 1:17:29 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe
(nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EAC830,
0xFFFFF88003EA4100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while
executing a routine that transitions from non-privileged code to
privileged code.
This appears to be a typical software driver bug and is not likely to
be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is
caused by another driver which cannot be identified at this time.




Got lots more but this is getting kinda long.


Jon

On Wed, 19 Sep 2012 00:58:27 +0800, Man-wai Chang
wrote:

No overclocking?

No

What if you used a regular spinning hard disk? Maybe it's the SSD!

I said in my original post I took out the SSD and put in a new hard
drive. I don't know if I mentioed but yes it was a disk drive.

Or maybe it's AHCI problem.

If you mean switching to AHCI mode in the BIOS I did that, if not then
I'm not sure what you mean by "AHCI problem".

Are you using legitimate Windows?

Bought and paid for.


thanks for answering