Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Ridiculous , absolutely ridiculous


  • Please log in to reply

#61
urgenthelp

urgenthelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
Any RAM suggestions.
  • 0

Advertisements


#62
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
The Intel i5 processor - memory specifications is

Max Memory Size (dependent on memory type)16 GBMemory TypesDDR3-1066/1333

http://ark.intel.com...-Cache-2_80-GHz)

The motherboard memory spec is

  • Support for DDR3 2200/1333/1066/800 MHz memory modules
  • Support for non-ECC memory modules
What that means is that the processor, whi9ch is what now dictates the ram to a large extent will accept ddr3 1066 or 1333 and that ram will work on default settings without

altering any ram settings in the BIOS. It does not mean that the processor wil not work with other ram spec, but simply that it will have to be set up.

therefore the ram is the 1333 or 1066 listed here as tested ram with the board

http://download.giga...5-us3l_v2.0.pdf

so you could if you wished put 8Gb Crucial in (4 x 2GB)

http://www.crucial.c...e=CT25664BA1339




  • 0

#63
urgenthelp

urgenthelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
Thank you for responding, i have now ordered 4 sticks and will report back when i receive them, thank you for the suggestion.
  • 0

#64
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Well I will be holding my breath so to speak

In that I just hope it works.

I cannot see another explanation as you have it OK with two sticks in and with ONE but not OK with two in dual channel.

If it does not, it is then apparent as far as I can see that you have a fault on the motherboard
  • 0

#65
urgenthelp

urgenthelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
However when i have it not dual channeled it says 4gb (2gb usable) when they are in 1 and 4 slots. But when i put it 1 and 2 it still crashes. And 2 and 3 doesn't work.
  • 0

#66
urgenthelp

urgenthelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
same old. the ram works perfectly, i have 8gb spread out into all the sockets. Everything was working perfectly, very fast. Then after a few hours bang i get 3 BSODs while playing a game all within 15 minutes of each other. 2 0x09c and 1 0x124. Established there is something seriously wrong here.
  • 0

#67
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Send me the either the who crashed or the latest minidump
  • 0

#68
urgenthelp

urgenthelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
There has been 5 since new ram, but this is the only one which got 100% in minidump.


On Sun 29/07/2012 01:07:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x9C (0x0, 0xFFFFF880031DDB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 .
Google query: Unknown MACHINE_CHECK_EXCEPTION
  • 0

#69
Shintaro

Shintaro

    Member

  • Member
  • PipPip
  • 55 posts
Urgenthelp,

Mate there are files in the C:\Windows\minidump directory. I am not trying to be rude, but do you know how to zip the files and upload them to the forum?
  • 0

#70
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Stepping in here for a minute. Instead of trying to sort through the mini dumps try the following which will give everyone a wider picture of everything.

Download BlueScreenView
No installation required.
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.

Thanks to Broni for the instructions and program
  • 0

Advertisements


#71
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Please DO as my colleague rshaffer61 has asked

Here is an excellent article on 0x000124 crash

Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled. If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. The most obvious examples are the RAM and HDD(s). For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing. For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc. Should that fail to mitigate the 0x124 problem, jump to the next steps. Otherwise, if you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.

If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine. Reseat all connectors and memory modules. Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

END OF EXTRACT


MOST relevent to the situation I opine is that we have I think updated the viedo drivers and I seem to remember suggesting that you updatde all for which there were updates.

We can now discount the ram I think

As you have run it perfectly with the new ram and then you get the crash while playing the game, if we are to pursue the hardware, we may be back to the graphics

We have run chkdsk and system file check

You say there is no overclock settings

After you have the Blue Screen View we will I think explore the temps when we load the graphics on a stress test

AND also check this please for your Intel i5 processor in the BIOS settings

Intel Turbo Boost Technology is usually enabled by default by a switch in the bios where you can either enable or disable operation. Other than this, there are no user controllable settings to change Intel Turbo Boost Technology operation either in the hardware settings or operating system. Once enabled, Intel Turbo Boost Technology works automatically under operating system control.


If you have it enabled try disabling it and check again for a crash
  • 0

#72
urgenthelp

urgenthelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
==================================================
Dump File : 071212-16411-01.dmp
Crash Time : 12/07/2012 02:04:13
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000050
Parameter 2 : 00000000`0000000a
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`04a0c071
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+c071
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071212-16411-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 071212-19468-01.dmp
Crash Time : 12/07/2012 01:31:44
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff880`009f1b70
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071212-19468-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 071012-21200-01.dmp
Crash Time : 10/07/2012 03:41:55
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`033b328f
Parameter 3 : fffff880`024d30b0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071012-21200-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 070912-16380-01.dmp
Crash Time : 09/07/2012 18:08:36
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`033ba28f
Parameter 3 : fffff880`0902e0b0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070912-16380-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 070812-19500-01.dmp
Crash Time : 08/07/2012 02:49:32
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0336d28f
Parameter 3 : fffff880`07a3c0b0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070812-19500-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 070712-17628-01.dmp
Crash Time : 07/07/2012 23:28:20
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff880`02f6bb70
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070712-17628-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 070512-15896-01.dmp
Crash Time : 05/07/2012 22:44:39
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`c2246c28
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030dead9
Caused By Driver : Unknown_Module_fffff880`016a5000
Caused By Address : Unknown_Module_fffff880`016a5000+17e140
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f549
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070512-15896-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 070512-16676-01.dmp
Crash Time : 05/07/2012 21:57:03
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : volsnap.sys
Caused By Address : volsnap.sys+54d6
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+fdf14
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070512-16676-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 070412-19203-01.dmp
Crash Time : 04/07/2012 23:12:57
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000001`002117f0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030a3f93
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070412-19203-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 070312-15974-01.dmp
Crash Time : 03/07/2012 13:36:09
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff880`c2f66ec0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`0309e2db
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070312-15974-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 062912-19624-01.dmp
Crash Time : 29/06/2012 19:23:16
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`033d3258
Parameter 3 : fffff880`07c9a020
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062912-19624-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 062612-18922-01.dmp
Crash Time : 26/06/2012 22:52:31
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f190
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f190
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062612-18922-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 062312-17487-01.dmp
Crash Time : 23/06/2012 01:13:03
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff880`009f1b70
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12818
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062312-17487-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 062212-16302-01.dmp
Crash Time : 22/06/2012 13:37:15
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000001`00fd5dd0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030def93
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062212-16302-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 062112-19905-01.dmp
Crash Time : 21/06/2012 17:57:24
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff880`c2f65ac0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030d82db
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062112-19905-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061812-18486-01.dmp
Crash Time : 18/06/2012 16:52:55
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`c3b769a0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030eb2db
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061812-18486-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061812-16832-01.dmp
Crash Time : 18/06/2012 16:14:29
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff880`ff9ec9c0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030e92db
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061812-16832-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061512-17472-01.dmp
Crash Time : 15/06/2012 17:26:04
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`c2b75ee0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`030de2db
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061512-17472-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061512-19936-01.dmp
Crash Time : 15/06/2012 12:39:26
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000001`00f66eb0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030a5f93
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061512-19936-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061412-21247-01.dmp
Crash Time : 14/06/2012 13:45:30
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff880`0316bb70
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12818
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061412-21247-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061412-19250-01.dmp
Crash Time : 14/06/2012 01:58:14
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffffff`bd8c6255
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030a2688
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5328a
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061412-19250-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 314,320
==================================================

==================================================
Dump File : 061412-38267-01.dmp
Crash Time : 14/06/2012 01:19:35
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffffff`85455e32
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030e2688
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5328a
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061412-38267-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061312-22417-01.dmp
Crash Time : 13/06/2012 23:41:41
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+2593
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f190
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061312-22417-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061212-14523-01.dmp
Crash Time : 12/06/2012 20:59:09
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff880`009f1b70
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12818
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061212-14523-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 061112-14929-01.dmp
Crash Time : 11/06/2012 22:41:24
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000001`009ed2d0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030e9fa3
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061112-14929-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 061112-14695-01.dmp
Crash Time : 11/06/2012 02:17:44
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f190
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f190
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\061112-14695-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 060812-16645-01.dmp
Crash Time : 08/06/2012 03:44:49
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`030b19a3
Parameter 3 : fffff880`09b88020
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060812-16645-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 060712-16458-01.dmp
Crash Time : 07/06/2012 00:55:59
Bug Check String : TIMER_OR_DPC_INVALID
Bug Check Code : 0x000000c7
Parameter 1 : 00000000`00000005
Parameter 2 : fffff880`0408e8c0
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`0000ffff
Caused By Driver : afd.sys
Caused By Address : afd.sys+538c0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060712-16458-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 060612-17643-01.dmp
Crash Time : 06/06/2012 15:32:09
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff880`02fdbb70
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12818
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060612-17643-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 060512-18283-01.dmp
Crash Time : 05/06/2012 22:33:16
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffffff`dbee88fb
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030e5688
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060512-18283-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 060412-24523-01.dmp
Crash Time : 04/06/2012 00:52:19
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`80000003
Parameter 2 : fffff960`00685aee
Parameter 3 : fffff880`09383778
Parameter 4 : fffff880`09382fd0
Caused By Driver : cdd.dll
Caused By Address : cdd.dll+204b0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : cdd.dll+5aee
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\060412-24523-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================

==================================================
Dump File : 053012-22994-01.dmp
Crash Time : 30/05/2012 17:05:27
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffffff`68554250
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030e9688
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\053012-22994-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,448
==================================================
=========

There is a problem here the last registered one is 12/07/12, i have had many bsods since then so they seem to not being put into the minidump file, however i think that covers all the reasons i am getting, Thanks again i will not go to bios.
  • 0

#73
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads
  • 0

#74
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
As you will have seen the latest crash report on blue screen view is 12 July and unless I am mistaken that date and indeed all earlier dates are largely irrelevant to the situation at present as they appertain to times when the old ram configuraration was in use.

Please check that processor details in the BIOS setup




  • 0

#75
urgenthelp

urgenthelp

    Member

  • Topic Starter
  • Member
  • PipPip
  • 64 posts
On Mon 30/07/2012 04:06:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073012-18220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41287, 0x20C4C0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 12/07/2012 01:02:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-16411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x50, 0xA, 0x0, 0xFFFFF88004A0C071)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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 Thu 12/07/2012 00:28:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-19468-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F1B70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 10/07/2012 02:40:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071012-21200-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033B328F, 0xFFFFF880024D30B0, 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 09/07/2012 17:06:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070912-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033BA28F, 0xFFFFF8800902E0B0, 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 Sun 08/07/2012 01:47:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070812-19500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000336D28F, 0xFFFFF88007A3C0B0, 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 Sat 07/07/2012 22:26:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070712-17628-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x9C (0x0, 0xFFFFF88002F6BB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 Thu 05/07/2012 21:43:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070512-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F549)
Bugcheck code: 0xA (0xFFFFFA80C2246C28, 0x2, 0x0, 0xFFFFF800030DEAD9)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Thu 05/07/2012 20:55:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070512-16676-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xFDF14)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Wed 04/07/2012 22:11:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070412-19203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x1002117F0, 0x2, 0x1, 0xFFFFF800030A3F93)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 03/07/2012 12:35:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070312-15974-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF880C2F66EC0, 0x2, 0x0, 0xFFFFF8000309E2DB)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Fri 29/06/2012 18:22:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062912-19624-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033D3258, 0xFFFFF88007C9A020, 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 26/06/2012 21:50:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062612-18922-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Sat 23/06/2012 00:10:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062312-17487-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F1B70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 Fri 22/06/2012 01:18:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062212-16302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x100FD5DD0, 0x2, 0x1, 0xFFFFF800030DEF93)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.



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

33 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:

unknown_module_00000000`00000022.sys

unknown_module_00000000`00000000.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.




That 30/07/12 one is new and i never received with my previous memory, but it does look like drivers.
  • 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