Random BSOD's, random freezes..

#1
Hello there,

I know this is an old computer, but if I don't have to buy a new one, that's always nice.
I've got random bsod's, en sometimes just freezes. It's hard for me to get into windows, and I have no idea how long it will run before it freezes again.

I had 3x 1024 DDR2 memory in the system, and tried all 3 seperatly, that wasn't a go. Now I run only with one, because it seems like it runs better now.

Here is a link with what I think all the requested files you needed.

With regards, and thanks in advance.

==EDIT==

The blue screens are only with this processor. When I put down my other slower Processor, I don't get any blue screens. I installed this Windows, all the drivers, flashed the bios to the latest version I could find on the Foxconn site, and like said above, tested all the memory.

Neither the memory or the video card is capable with the motherboard, according to their site, but yet I didn't seem too bother with the old CPU.

The computer is running now 2 hours straight, without any errors. Wich is a new record since this CPU.

==EDIT 2==

I was just sitting, watching a movie, and I thought; what did I do what makes the computer still work?
Well, I have 1 memory bank plugged in, but not into the first slot where to put it in, but in the second.
So, why did it work with the old CPU, and not with this one.

All these questions... When I'm done with downloading the game I play, I will try put back the other 2 memory banks in the last 2 slots, and leave the first slot open.

I'll post results after it, hopes someone will reply before that, maybe it's something entirely different.

http://www.megafileupload.com/en/file/375973/W7F-25-11-2012-rar.html
 


Last edited:

usasma

Fantastic Member
Microsoft Community Contributor
#2
Only 402 mB of RAM is available - if this is because of the testing, don't worry about it. But if this is all the RAM that you have - post back and we'll make some recommendations.

The systeminfo file relates 400+ Windows Updates installed after SP1. Most systems have 130 to 140 and I have never seen a Windows system with this many updates installed.

If this is an illegal copy of Windows, please be advised that it may not be fixable by us. The steps taken to bypass Windows Activation, etc will usually be the cause of the problem. As we don't work on illegal copies of Windows here, we don't have any knowledge of how to fix these errors.

Your BIOS dates from 2008. Please post a link to the exact make and model of your motherboard (with specifications) so we can see what updates are available.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

This one must be updated to a later version:
nvBridge.kmd Tue Apr 28 23:25:58 2009 (49F7C8C6)
nVidia Compatible Vista Kernel Mode Driver (likely belongs to nForce chipset drivers)
http://www.carrona.org/drivers/driver.php?id=nvBridge.kmd

This one must be un-installed:
sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
http://www.carrona.org/drivers/driver.php?id=sptd.sys

If this doesn't fix the issues, please run Driver Verifier according to these directions: Driver Verifier Settings


Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Sun Nov 25 09:51:41.309 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-26286-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].22105.amd64fre.win7sp1_ldr.120903-0332
System Uptime:[B]0 days 0:00:13.291[/B]
BugCheck Code: [B]BugCheck A, {fffffffffffffff7, 2, 0, fffff800028dced9}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiTimerExpiration+d9 )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
Arguments: 
Arg1: fffffffffffffff7, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800028dced9, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiTimerExpiration+d9[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 09:29:58.656 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-24336-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].22105.amd64fre.win7sp1_ldr.120903-0332
System Uptime:[B]0 days 0:00:58.297[/B]
BugCheck Code: [B]BugCheck A, {448f, 2, 1, fffff80001c952c2}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiTimerWaitTest+1e2 )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
Arguments: 
Arg1: 000000000000448f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001c952c2, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiTimerWaitTest+1e2[/B]
  BIOS Version                  080014 
  BIOS Release Date             07/26/2008
  Manufacturer                  FOXCONN
  Product Name                  RS690M2MA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 09:25:43.888 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-25911-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].22105.amd64fre.win7sp1_ldr.120903-0332
System Uptime:[B]0 days 0:00:12.870[/B]
BugCheck Code: [B]BugCheck A, {448f, 2, 1, fffff800028e52c2}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiTimerWaitTest+1e2 )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
Arguments: 
Arg1: 000000000000448f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800028e52c2, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiTimerWaitTest+1e2[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 08:42:49.418 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-26364-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].22105.amd64fre.win7sp1_ldr.120903-0332
System Uptime:[B]0 days 0:02:40.275[/B]
BugCheck Code: [B]BugCheck D1, {ffffffffffffffff, d, 8, ffffffffffffffff}[/B]
Probably caused by :[B]atapi.sys ( atapi!AtapiHwStartIo+f3 )[/B]
BugCheck Info: [B]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/B]
Arguments: 
Arg1: ffffffffffffffff, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: ffffffffffffffff, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_CODE_AV_BAD_IP_atapi!AtapiHwStartIo+f3[/B]
  BIOS Version                  080014 
  BIOS Release Date             07/26/2008
  Manufacturer                  FOXCONN
  Product Name                  RS690M2MA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 08:38:18.095 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-27456-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].22105.amd64fre.win7sp1_ldr.120903-0332
System Uptime:[B]0 days 0:00:20.077[/B]
BugCheck Code: [B]BugCheck A, {28, d, 0, fffff80002817887}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck Info: [B]IRQL_NOT_LESS_OR_EQUAL (a)[/B]
Arguments: 
Arg1: 0000000000000028, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002817887, address which referenced memory
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiPageFault+260[/B]
  BIOS Version                  080014 
  BIOS Release Date             07/26/2008
  Manufacturer                  FOXCONN
  Product Name                  RS690M2MA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[FONT=lucida console]**************************Sun Nov 25 09:51:41.309 2012 (UTC - 5:00)**************************
[COLOR=RED][B]sptd.sys                    Sun Oct 11 16:55:14 2009 (4AD24632)[/B][/COLOR]
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 09:29:58.656 2012 (UTC - 5:00)**************************
Rtnic64.sys                 Thu Jul 23 10:03:10 2009 (4A686D9E)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 08:42:49.418 2012 (UTC - 5:00)**************************
[COLOR=RED][B]nvBridge.kmd                Tue Apr 28 23:25:58 2009 (49F7C8C6)[/B][/COLOR]
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
[/FONT]
http://www.carrona.org/drivers/driver.php?id=sptd.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=Rtnic64.sys
http://www.carrona.org/drivers/driver.php?id=nvBridge.kmd
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 


GeneralHiningII

Honorable Member
#3
It could also be that your motherboard can't work well with the processor
 


usasma

Fantastic Member
Microsoft Community Contributor
#4
Your BIOS is seriously outdated.
Your chipset drivers are seriously outdated
We don't know the make/model of both processors - so we can't tell if they're compatible or not.
And your Windows is not a legal copy.

The first step (for working here) is to get legal. The forum rules won't allow us to continue helping with illegal software. Forum Rules - Windows 7 Forums You also should be legal so that the system is performing as the manufacturer intended it (without the hacks that make it work illegally).
The next step is to research the compatibility of both processors with this motherboard
The next step is to ensure that you have the latest chipset drivers from AMD: AMD Chipset Drivers

Good luck to you - I hope to see you back (if needed) once you've got a legal copy of Windows installed!
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top