Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Harddrive causing ntoskrnl and memory errors?

31 May 2011   #1

Windows 7 ultimate x64
 
 
Harddrive causing ntoskrnl and memory errors?

Ok so, this is the situation.

I've been having alot of bluescreens while playing games.

i used to have bluescreens with my geforce 9800gt card and the graphics went all strange during gaming, so i take it the card was failing.

i have replaced my motherboard,cpu and graphic card since then and am still
experiencing bluescreens, 7 of them blame ntoskrnl.exe and one to do with my graphic card

the errors are
IRQL_NOT_LESS_OR_EQUAL
IRQL_GT_ZERO_AT_SYSTEM_SERVICE
KMODE_EXCEPTION_NOT_HANDLED
SYSTEM_SERVICE_EXCEPTION
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


Windows is installed on my C: drive which is 250gb
however all my games are installed on my E: drive which is 1tb
recently while using my 1tb hard drive it has made a single click sound and
straight after if i open the hard drive my explorer.exe freezes

i thought all the bluescreens might have been caused by RAM at first
but could it be possible that while im gaming the harddrive does this and bluescreens me, blaming it on memory?

Im reformatting E: at this very moment.

My System SpecsSystem Spec
31 May 2011   #2
Microsoft MVP

 
 

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)
If these tests pass, then please post this info: http://www.sevenforums.com/crashes-d...tructions.html
My System SpecsSystem Spec
04 Jun 2011   #3

Windows 7 ultimate x64
 
 

I ran short generic tests with the seagate seatools on both harddrives and they passed
i did the same with speedfan's S.M.A.R.T and passed also.

While testing my 150gb (where windows is installed) i noticed no sound
however when testing my 1tb i noticed a grumble noise its quite loud but its
not high pitched or anything its literally like a grumble.
My System SpecsSystem Spec
.


04 Jun 2011   #4
Microsoft MVP

 
 

Please run the long diagnostic test. I have seen the short test pass drives that failed the long test.
IMO any noise from a hard drive is bad news. Here's a link to a Google search for hard drive noises - try playing a few of them to see if you can ID it.

Also, please run the memory test for at least 3 passes.

It appears that you reinstalled Windows on 22 May 2011 and haven't updated Windows since then. The memory dumps that you uploaded started on 23 May 2011. I presume that you were experiencing BSOD's prior to this point - is that the case? If so, then that makes a hardware problem most likely (although compatibility and low-level driver issues are a possibility also).

Please visit Windows Updates and get all Windows updates available (60 to 80 at this time). DON'T install Service Pack 1 yet - you can do that after updating all of your drivers (that'll be info contained in the dump file analysis later on in this post).

MSINFO32 shows one BSOD on 23 May 2011 that involves your USB audio driver. Do you use a USB audio device?

17 memory dumps from 23 May to 04 Jun 2011
7 different BSOD error codes
7 different causes blamed
As mentioned above, that makes a hardware problem most likely (although compatibility and low-level driver issues are a possibility also.

After running the long hard drive test (on both drives), then memory test (at least 3 passes), and a malware scan (at least one of the online scans) - then try these stress tests (the first 2 are the most important to us right now):
Quote:
Quote:
FurMark download site: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90║C. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exit
Quote:
Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: http://www.playtool.com/pages/prime95/prime95.html
Quote:
More Video Stress Tests:
1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
2. Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - http://nvworld.ru/utilities/vmt/
Artifact Locator - http://nvworld.ru/utilities/alocator/
Sorry, but I don't read the language that this website is made in.
3. Another interesting test that came to my attention: http://www.ocbase.com/perestroika_en/index.php?Download
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!
But, as mentioned earlier, lower level drivers can also cause this - and the ASACPI.sys driver (listed below) is a prime example of this. The 2005 version is a known BSOD cause in many Windows 7 systems. Please visit the Asus website to download/install the latest version of this driver (it's the ATK0110 ACPI Utility). It's either listed under the ATK section or the Utilities section of the download page (I don't have the exact model of your mobo to look it up). Also, the driver is usually contained in the Asus AISuite software or the Asus PCProbe software - if installing it that way, double check the date on the ASCAPI.sys file in the C:\Windows\System32\drivers folder.

If you can't find it, please post back with the exact model number so we can research it. Here's the models from the Asus website: I would also download and install the chipset driver software from the nVidia website here: NVIDIA DRIVERS 275.33 WHQL

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:
Quote:
Code:

nvstor.sys        Wed May 20 02:45:37 2009 (4A13A711)
amdxata.sys       Tue May 19 13:56:59 2009 (4A12F2EB) - Windows Update will update this, please make sure to get it (it'll have a 2010 date stamp).
speedfan.sys      Sat Dec 18 06:03:51 2010 (4D0C9517)
netr6164.sys      Wed Apr 07 08:07:21 2010 (4BBC7579)
nvmf6264.sys      Thu Aug 12 07:46:06 2010 (4C63DEFE)
SCDEmu.SYS        Mon Apr 12 04:52:25 2010 (4BC2DF49)
AsUpIO.sys        Sun Jul 05 22:21:38 2009 (4A515FB2)
AsIO.sys          Thu Apr 22 07:18:03 2010 (4BD0306B)
ASACPI.sys        Wed Jul 15 23:31:29 2009 (4A5E9F11)
amdiox64.sys      Thu Feb 18 10:17:53 2010 (4B7D5A21)
dump_nvstor.sys   Wed May 20 02:45:37 2009 (4A13A711)
viahduaa.sys      Mon Jan 11 05:05:18 2010 (4B4AF7DE)
aswMonFlt.sys     Tue May 10 07:59:47 2011 (4DC928B3)
AtihdW76.sys      Thu Mar 31 03:15:43 2011 (4D942A1F)
ASACPI.sys        Sun Mar 27 22:30:36 2005 (42476C4C)
netr6164.sys      Thu Oct 15 23:15:23 2009 (4AD7E54B)
nvm62x64.sys      Fri Oct 17 17:01:06 2008 (48F8FD12)
mbam.sys          Mon Jan 03 15:50:39 2011 (4D22369F)
aswSP.SYS         Tue May 10 08:04:06 2011 (4DC929B6)
aswSnx.SYS        Tue May 10 08:04:06 2011 (4DC929B6)
atikmpag.sys      Tue Apr 19 21:22:32 2011 (4DAE3558)
atikmdag.sys      Tue Apr 19 21:53:29 2011 (4DAE3C99)
aswFsBlk.SYS      Tue May 10 07:59:36 2011 (4DC928A8)
aswTdi.SYS        Tue May 10 08:02:40 2011 (4DC92960)
dump_storport.sys Mon Jul 13 20:01:00 2009 (4A5BCABC)
http://www.carrona.org/dvrref.html#nvstor.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#speedfan.sys
http://www.carrona.org/dvrref.html#netr6164.sys
http://www.carrona.org/dvrref.html#nvmf6264.sys
http://www.carrona.org/dvrref.html#SCDEmu.SYS
http://www.carrona.org/dvrref.html#AsUpIO.sys
http://www.carrona.org/dvrref.html#AsIO.sys
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#amdiox64.sys
http://www.carrona.org/dvrref.html#dump_nvstor.sys
http://www.carrona.org/dvrref.html#viahduaa.sys
http://www.carrona.org/dvrref.html#aswMonFlt.sys
http://www.carrona.org/dvrref.html#AtihdW76.sys
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#netr6164.sys
http://www.carrona.org/dvrref.html#nvm62x64.sys
http://www.carrona.org/dvrref.html#mbam.sys
http://www.carrona.org/dvrref.html#aswSP.SYS
http://www.carrona.org/dvrref.html#aswSnx.SYS
http://www.carrona.org/dvrref.html#atikmpag.sys
http://www.carrona.org/dvrref.html#atikmdag.sys
http://www.carrona.org/dvrref.html#aswFsBlk.SYS
http://www.carrona.org/dvrref.html#aswTdi.SYS
http://www.carrona.org/dvrref.html#dump_storport.sys
BSOD BUGCHECK SUMMARY
Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060411-22963-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun  4 13:32:01.435 2011 (UTC - 4:00)
System Uptime: 0 days 2:29:30.294
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!RtlImageNtHeaderEx+3f
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`01ab3047 fffff880`08b9b9a0 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060411-20607-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jun  3 18:20:18.279 2011 (UTC - 4:00)
System Uptime: 0 days 3:40:31.153
Probably caused by : netbt.sys ( netbt!NbtDereferenceAddress+69 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x27
FAILURE_BUCKET_ID:  X64_0x27_netbt!NbtDereferenceAddress+69
Bugcheck code 00000027
Arguments 00000000`baad0073 fffff880`099732a8 fffff880`09972b00 fffff880`0359264b
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060311-18860-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jun  3 14:38:08.503 2011 (UTC - 4:00)
System Uptime: 0 days 1:36:18.721
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`04365ff3 fffff880`04fb6698 fffff880`04fb5ef0
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060211-18704-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jun  2 10:56:33.125 2011 (UTC - 4:00)
System Uptime: 0 days 4:08:56.359
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060111-20046-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun  1 18:07:19.440 2011 (UTC - 4:00)
System Uptime: 0 days 4:44:08.315
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000109
Arguments a3a039d8`991345cd 00000000`00000000 f6694b4c`3404564b 00000000`00000101
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060111-24164-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun  1 12:35:14.770 2011 (UTC - 4:00)
System Uptime: 0 days 10:46:14.003
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`04398ff3 fffff880`044f6698 fffff880`044f5ef0
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053111-30420-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue May 31 10:23:27.713 2011 (UTC - 4:00)
System Uptime: 0 days 0:20:05.572
Probably caused by : ntkrnlmp.exe ( nt!AlpcpQueueIoCompletionPort+11a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wlcomm.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!AlpcpQueueIoCompletionPort+11a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0189abaa fffff880`089cd3f0 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053011-16582-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon May 30 17:49:27.494 2011 (UTC - 4:00)
System Uptime: 0 days 0:31:29.368
Probably caused by : kbdclass.sys ( kbdclass!KeyboardClassServiceCallback+47e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_kbdclass!KeyboardClassServiceCallback+47e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053011-19297-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon May 30 17:17:12.616 2011 (UTC - 4:00)
System Uptime: 0 days 2:04:10.864
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+73 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+73
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`03228997 fffff880`09f5d940 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053011-18766-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon May 30 15:12:14.828 2011 (UTC - 4:00)
System Uptime: 0 days 6:19:34.077
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`041ac50a fffff880`09bb8c30 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052911-18579-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun May 29 16:21:05.048 2011 (UTC - 4:00)
System Uptime: 0 days 2:15:44.923
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExFreePoolWithTag+43
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`019bc0f3 fffff880`05578b80 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052911-21871-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun May 29 14:03:40.281 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:07.530
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052911-34351-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun May 29 13:40:48.895 2011 (UTC - 4:00)
System Uptime: 0 days 8:24:33.144
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+3d3f5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+3d3f5
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`038cc3f5 fffff880`05191408 fffff880`05190c60
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052811-20982-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat May 28 18:21:44.264 2011 (UTC - 4:00)
System Uptime: 0 days 6:40:27.497
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  hl2.exe
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052811-26286-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat May 28 11:29:35.951 2011 (UTC - 4:00)
System Uptime: 0 days 5:41:26.200
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExFreePoolWithTag+43
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`01a000f3 fffff880`07bcda00 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052611-25240-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu May 26 12:04:59.520 2011 (UTC - 4:00)
System Uptime: 0 days 3:50:45.363
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
PROCESS_NAME:  AvastSvc.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_AvastSvc.exe_nt!KiSystemServiceExit+245
Bugcheck code 0000004A
Arguments 00000000`741b2dd9 00000000`00000002 00000000`00000000 fffff880`021c9ca0
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052311-22120-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon May 23 17:05:48.767 2011 (UTC - 4:00)
System Uptime: 0 days 3:23:34.001
Probably caused by : usbaudio.sys ( usbaudio!USBCaptureProcessPin+306 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xA_CODE_AV_BAD_IP_usbaudio!USBCaptureProcessPin+306
Bugcheck code 0000000A
Arguments fffff800`01bff800 00000000`00000002 00000000`00000008 fffff800`01bff800
BiosVersion = 0706   
BiosReleaseDate = 04/09/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
13 Jun 2011   #5

Windows 7 ultimate x64
 
 
Fixed

I replaced my

Geil 2GB Value Series PC10660 1333MHz CL9.0 DDR3


With

2GB DDR3 PC10660 1333MHZ VDATA MEMORY


And the problem has been fixed
strange how i tried each 2gb geil stick seperate with the same bluescreens, maybe the geil memory just doesn't like my asus m4n68t? or i was extremely unlucky and got two faulty sticks
My System SpecsSystem Spec
Reply

 Harddrive causing ntoskrnl and memory errors?





Thread Tools



Similar help and support threads for2: Harddrive causing ntoskrnl and memory errors?
Thread Forum
Multiple Errors BSOD, NTOSKRNL.exe, possible memory involvment BSOD Help and Support
ntoskrnl.exe causing BSOD BSOD Help and Support
BSOD opening files located on external harddrive - ntoskrnl.exe BSOD Help and Support
ntoskrnl.exe causing a lot of BSOD BSOD Help and Support
bluescreens/stack dumps/memory errors/bad image errors BSOD Help and Support
ntoskrnl.exe causing the problem ?? BSOD Help and Support
ntoskrnl causing kernel power errors on brand new pc BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 10:27 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33