ntoskrnl.exe+7cc40 BSOD's

[Kristofaaa]

Hi,

I have a new rig i built my self and it runs perfectly except the occasional BSOD and i cant for the life of me work out why...

091711-6006-01.dmp 17/09/2011 21:33:23 BAD_POOL_HEADER 0x00000019 00000000`00000003 fffff8a0`1205a820 ff8af8a0`1205a820 fffff8a0`1205a820 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\091711-6006-01.dmp 8 15 7601 293,064

091311-5896-01.dmp 13/09/2011 18:56:14 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`55685460 00000000`00000001 fffff880`06b9d316 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\091311-5896-01.dmp 8 15 7601 291,016

091311-7722-01.dmp 13/09/2011 13:40:14 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc10 C:\Windows\Minidump\091311-7722-01.dmp 8 15 7601 288,232

Basically i bought one of the affected mother boards before the b3 revision for sandy bridge systems. I managed to get an updated mobo via RMA.

So i changed mother boards over. Then a few weeks later i changed my RAM, old was Corsair XMS 1600mhz 4gb, new is Corsair Vengeance 1866mhz 8gb.

I also started off with a F60 Corsair ssd 60gb and change dthat to a new force 3 120gb ssd.

Since i reinstalled my OS (win 7 x64) i keep getting BSOD's. I have formatted and reinstalled and the same happens.

Please any assistance would be greatly appreciated...

Attached my minidump folder...

Thanks in advance.

 

[zigzag3143]

Hi,

I have a new rig i built my self and it runs perfectly except the occasional BSOD and i cant for the life of me work out why...

091711-6006-01.dmp 17/09/2011 21:33:23 BAD_POOL_HEADER 0x00000019 00000000`00000003 fffff8a0`1205a820 ff8af8a0`1205a820 fffff8a0`1205a820 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\091711-6006-01.dmp 8 15 7601 293,064

091311-5896-01.dmp 13/09/2011 18:56:14 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`55685460 00000000`00000001 fffff880`06b9d316 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+7cc40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\091311-5896-01.dmp 8 15 7601 291,016

091311-7722-01.dmp 13/09/2011 13:40:14 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7cc10 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17640 (win7sp1_gdr.110622-1506) x64 ntoskrnl.exe+7cc10 C:\Windows\Minidump\091311-7722-01.dmp 8 15 7601 288,232

Basically i bought one of the affected mother boards before the b3 revision for sandy bridge systems. I managed to get an updated mobo via RMA.

So i changed mother boards over. Then a few weeks later i changed my RAM, old was Corsair XMS 1600mhz 4gb, new is Corsair Vengeance 1866mhz 8gb.

I also started off with a F60 Corsair ssd 60gb and change dthat to a new force 3 120gb ssd.

Since i reinstalled my OS (win 7 x64) i keep getting BSOD's. I have formatted and reinstalled and the same happens.

Please any assistance would be greatly appreciated...

Attached my minidump folder...

Thanks in advance.

Easy, these were related to your C-media Audio driver. I would update to the newest version below.

C-Media Electronics, Inc.




Since pool corruption was involved I would run these two tests.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 6 or 8 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Kristofaaa]

Hi,

Wow that was quick...

Ok i did the mem86 test and all was fine.

I forgot the c media stuff, that i THINK was from earlier BSOD's that i resolved to do with my new headset. The last 3 i have had are the ones i put in my OP some thing to do with NT Kernal ?

So should i still try the 2nd idea you gave ?

Thanks.

 

[tonyozr]

A few hours ago I started getting the same error on the same memory addresses. I have a suspicion that this is related to Sandboxie. You use this program?

Sorry for my English =)

 

[Kristofaaa]

Hi,

No never heard of that program... Sorry..

 

[Kristofaaa]

Hi again,

Ok so i did the verifier how you explained and got a BSOD on start up.

So i booted into safe mode and turned verifier off and here's the mini dump....

There should be 2 but the later one is the correct one, the first was me testing the verifier so i knew how to disable it

Ah i so hope someone can get to the bottom of this for me i will let you borrow my GF if you can lol

091811-6505-01.dmp 18/09/2011 09:03:38 DRIVER_VERIFIER_IOMANAGER_VIOLATION 0x000000c9 00000000`0000023b fffff880`05f07710 fffff980`25112cf0 00000000`00000000 HIDCLASS.SYS HIDCLASS.SYS+2710 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\091811-6505-01.dmp 8 15 7601 266,320

 

[Kristofaaa]

Hi....

Im assuming that last mindump i attached did not help ??

Anything else i can try please ?

 

[zigzag3143]

Hi again,

Ok so i did the verifier how you explained and got a BSOD on start up.

So i booted into safe mode and turned verifier off and here's the mini dump....

There should be 2 but the later one is the correct one, the first was me testing the verifier so i knew how to disable it

Ah i so hope someone can get to the bottom of this for me i will let you borrow my GF if you can lol

091811-6505-01.dmp 18/09/2011 09:03:38 DRIVER_VERIFIER_IOMANAGER_VIOLATION 0x000000c9 00000000`0000023b fffff880`05f07710 fffff980`25112cf0 00000000`00000000 HIDCLASS.SYS HIDCLASS.SYS+2710 x64 ntoskrnl.exe+7cc40 C:\Windows\Minidump\091811-6505-01.dmp 8 15 7601 266,320

The most recent two driver verified crashes were releate to HIDCLASS.sys (an OS file related to "human Interface devices". Things like fingerprint readers, accellerometers, etc)

Since this is an OS driver and you have updated to SP-1 I would run a systm file check to verify and repair your system drivers

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

 

[Kristofaaa]

Hmmm...

All i have plugged in that i use is a mouse and keyboard and a headset...

I did the check and it says all is ok..

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>SFC /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

Incidentally i have not experienced a BSOD for 2 days now and i have been using my system just as i always do...

 

[zigzag3143]

Hmmm...

All i have plugged in that i use is a mouse and keyboard and a headset...

I did the check and it says all is ok..

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>SFC /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

Incidentally i have not experienced a BSOD for 2 days now and i have been using my system just as i always do...

Well at least SFC didnt report any errors. Upload any DMP's if they occur.

 

[Homeuser66]

Has anyone found a fix for this? I still don't know what is causing it. I ran "Who Crashed" after I got a BSOS and this was my result:

On Fri 9/23/2011 5:01:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092311-18938-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B4D9028, 0xFE000000, 0x40014A)
Error: WHEA_UNCORRECTABLE_ERROR
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 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 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.

Running Blue Screen Viewer I get:

==================================================
Dump File : 092311-18938-01.dmp
Crash Time : 9/23/2011 1:04:17 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0b4d9028
Parameter 3 : 00000000`fe000000
Parameter 4 : 00000000`0040014a
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092311-18938-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 297,176




All my Temp's seemed to be in range during the crash. But you never know...any ideas here?

 

[zigzag3143]

Has anyone found a fix for this? I still don't know what is causing it. I ran "Who Crashed" after I got a BSOS and this was my result:

On Fri 9/23/2011 5:01:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092311-18938-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B4D9028, 0xFE000000, 0x40014A)
Error: WHEA_UNCORRECTABLE_ERROR
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 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 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.

Running Blue Screen Viewer I get:

==================================================
Dump File : 092311-18938-01.dmp
Crash Time : 9/23/2011 1:04:17 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0b4d9028
Parameter 3 : 00000000`fe000000
Parameter 4 : 00000000`0040014a
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092311-18938-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 297,176




All my Temp's seemed to be in range during the crash. But you never know...any ideas here?

As previously indicated we need the actual dmp file to examine.


Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Homeuser66]

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

I looked into this and I have already done all these steps. Except for updating my BIOS. I will try that next, but they suggest (ASUS) if the update description doesn't fit my issue, not to update. But I can always revert back.

As previously indicated we need the actual dmp file to examine.

I am attaching my .dmp file.

 

[zigzag3143]

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

I looked into this and I have already done all these steps. Except for updating my BIOS. I will try that next, but they suggest (ASUS) if the update description doesn't fit my issue, not to update. But I can always revert back.

As previously indicated we need the actual dmp file to examine.

I am attaching my .dmp file.

Still pointing to hardware. I would remove anything you can (ie external hd, etc) leaving only mouse, keyboard, monitor, and mobo.

If it is a desktop I would also remove all but one stick of ram.

See if it crashes then and add back the hardware you removed.

 

[Homeuser66]

Still pointing to hardware. I would remove anything you can (ie external hd, etc) leaving only mouse, keyboard, monitor, and mobo

Thanks Zigzag....I will do this....however, I can't duplicate my problem.. I only happened a few days ago, then before that, it was months ago....so I would be removing items that I use on a day-to-day basis..So far, i have updated all my device drivers using Driver Genius Pro.. BIOS is my next step. I have ran Mem-test and all has passed. I even replaced a HDD and it still does it, but again, randomly.. I will keep a close eye on it and when I can, remove and use the comp parts sparingly....

 

[djceejay]

I think I got it!

Hi!

Same issue here, same driver and same Problem

Before 2 min. I was like , then I was like and now I´m like

I have 2 Harddrives, both with a primary Partition (160 GB is the active HDD). Earlier I installed Windows on my 1 TB HDD, which is now not actual anymore.

If you have 2 primary partitions on your system, change the letter of the inactive one from D to anything else (I used J) - maybe that´s the solving action. I did it and I didn´t have any BSOD´s with that dll anymore.

Peaces

 

[djceejay]

Ok forgot what I typed... it was a bad driver -.-

To localize the Bad driver, just open the device manager and let you show ALL Drivers (View -> Show all Drivers), if you now have a bad driver, you can see it ( I had a bad driver for my Mouse and my Keyboard)

Hope it helps you!

 

[Homeuser66]

I actually haven't had this BSOD in months..I don't know what I did to fix it, but I just reformatted back Dec, 2011...When I have time, I will look into this a little more and try to remember what the issue was.

I do recall, there is/was another post about this similar issue. Found (on SevenFourms) Here: http://www.sevenforums.com/crashes-...vlddmkm-sys-dxgkrnl-sys-help.html#post1682058

Since I have followed these steps, I have never had a BSOD again...could be coincidence, or it could be the fix....

 

[djceejay]

Thanks, I will try

Thank you for your respond and the tip with link

I will try it

 

[Homeuser66]

Any time....Let me know if it works for you as well......