Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Getting The Darkness 2 to run with AMD FX 4100 Black Edition CPU?


  • Please log in to reply

#1
Northy

Northy

    Member

  • Member
  • PipPip
  • 46 posts
This is the second game I bought now that won't run with my processor, the system freezes, presents a blue screen then reboots. All I've been told is to flash my BIOS but I don't have the know how to do it manually on Windows 7 64 Bit. Is there anything else I can try to get this game working? I rang up my local computer shop but they refused to flash the BIOS incase they screwed up.

Thanks in advance.
  • 0

Advertisements


#2
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Have a look at this please and work your way through.

Post please either way, if it provides a solution or not and if NOT we will explore further.


http://apps-explorer...ms-crashes.html
  • 0

#3
Northy

Northy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 46 posts
Just to add before I start I cannot get into the game at all, it will get to the title screen on odd occasions. The only way I can access compatibility mode for the game is to launch it and do it from the task manager, however the game crashes to quickly for me too.
  • 0

#4
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
There are a number of suggestions for that situation. To save me a lot of typing, please work your way through them.

I presume, you know that your system meets the requirements of the game.

Does the system crash at anytime, when not gaming.




  • 0

#5
Northy

Northy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 46 posts
I will do when I get on the pc, il most likely have the results up tomorrow.
I have a system spec capable of running it on high as it worked on the demo.
Having owned the rig for 6 months it has not crashed other than this game problem ( same with space marine)
  • 0

#6
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
When it blue screens is it the BSOD with the stop and error codes
  • 0

#7
Northy

Northy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 46 posts
I don't think so. All I can remember from it is, is that it said windows has encountered an error. It's stopped now for some reason the game just freezes and reboots.
  • 0

#8
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
download this please click the analyse tab scroll down for the results please and copy and paste them to your reply

http://www.resplende...rashedSetup.exe
  • 0

#9
Northy

Northy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 46 posts
System Information (local)
--------------------------------------------------------------------------------

computer name: RYAN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX™-4100 Quad-Core Processor AMD586, level: 21
4 logical processors, active mask: 15
RAM: 4292403200 total
VM: 2147352576, free: 1974075392



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 19/07/2012 19:12:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-27846-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80049908F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 19/07/2012 18:51:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-17269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004F8D8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 19/07/2012 18:41:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-18033-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80049638F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 19/07/2012 18:33:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-22417-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004FA9038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 19/07/2012 17:33:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071912-22183-01.dmp
This was probably caused by the following module: unknown_module_00000000`000000a6.sys (Unloaded_Unknown_Module_00000000`000000a6+0x5B)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`000000a6.sys .
Google query: unknown_module_00000000`000000a6.sys CLOCK_WATCHDOG_TIMEOUT




On Thu 19/07/2012 17:33:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 17/07/2012 11:31:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071712-23899-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 17/07/2012 11:27:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071712-23478-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80049568F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 07/06/2012 14:09:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-18454-01.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0x4A94)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880043EAA94, 0xFFFFF88004BB1398, 0xFFFFF88004BB0BF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc).
Google query: etronxhci.sys Etron Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Thu 26/04/2012 17:03:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042612-19094-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F64180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 25/04/2012 15:01:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042512-16863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800466D8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 24/04/2012 22:19:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042512-19921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 24/04/2012 22:08:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042412-18189-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 24/04/2012 21:45:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042412-23587-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80049318F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 24/04/2012 21:38:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042412-22167-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

17 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc)

unknown_module_00000000`000000a6.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#10
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Whilst I look at that go Control Panel Programs and features. click on left pane view installed updates and check if you have these

KB2645594

KB 2646060


  • 0

Advertisements


#11
Northy

Northy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 46 posts
I do not have these installed.
  • 0

#12
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Before we start on that

However small the risk, there is always of course a risk, once we start installing drivers and addressing other issues.

1. Is system restore turned on.

2. Check that you can create a restore point

3. Do you have the system backed up and does that include a complete image

4. Is the computer OEM with a pre installed O/S and a recovery partition OR is it generic and you have the Windows 7 Microsoft DVD, so that if necessary we can boot and use startup repair.

5. I am NOT expecting anything to happen but it is no use trying to shut the stable door after the horse has bolted.




  • 0

#13
Northy

Northy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 46 posts
its on and I can restore.
  • 0

#14
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Please tell me when you are calling it a night and I will do the same for you.

That will save either of us waiting fro a reply that is not arriving

I am in the UK and will be signing off in about one hour, but I will post when I am going.

Pls answer 3 & 4








  • 0

#15
Northy

Northy

    Member

  • Topic Starter
  • Member
  • PipPip
  • 46 posts
UK also, North Wales actually :P

3: Not backed up, no resource to do so
4: One partition with Windows 7 DVD
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP