Solved Computer Crashing Randomly After Update

[Fari]

Memory corruption (probably caused by one of these drivers from 2007)

ADIHdAud.sys    8/3/2007 2:28:43 PM        
DLADResM.SYS    7/23/2007 6:04:10 PM       
DLAOPIOM.SYS    7/23/2007 6:03:19 PM       
DLABMFSM.SYS    7/23/2007 6:02:42 PM       
DLABOIOM.SYS    7/23/2007 6:02:37 PM       
DLAUDFAM.SYS    7/23/2007 6:02:20 PM        
DLAUDF_M.SYS    7/23/2007 6:01:56 PM       
DLAPoolM.SYS    7/23/2007 6:01:41 PM       
DLAIFS_M.SYS    7/23/2007 6:01:39 PM       
DRVMCDB.SYS    7/23/2007 5:53:48 PM       
DLACDBHM.SYS    7/23/2007 5:49:30 PM      
DLARTL_M.SYS    7/23/2007 5:48:47 PM       
DRVNDDM.SYS    7/23/2007 5:42:35 PM

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

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



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Every time I try to System Restore from my installation DVD I get back to the problem??

 

[DJJay]

Good morning. Crashed multiple times overnight. Not one problem all day while I was working yesterday.
I have attached last nights dumps.

Also the same updates are still showing up in my windows update notifications.

 

[DJJay]

....and now for today's top 10 minidumps.
Actually 16 of them overnight.

 

[Fari]

Good morning. Crashed multiple times overnight. Not one problem all day while I was working yesterday.
I have attached last nights dumps.

Also the same updates are still showing up in my windows update notifications.

Name of problem: StartupRepairOffline
Problemdetalje:
Problemsignatur 01: 6.1.7600.16385
Problemsignatur 02: 6.1.7600.16385
problemsignatur 03: Unknown
problemsignatur 04: 21200618
problemsignatur 05: AutoFailover
problemsignatur 06: 2
problemsignatur 07: NoRootCause
OS-version: 6.1.7600.2.0.0.256.1
Landestandard-id: 1030

 

[writhziden]

I am confused. Does this mean you cannot boot into Windows at the moment? Did you try OPTION TWO of http://www.sevenforums.com/tutorials/700-system-restore.html:

• http://www.sevenforums.com/tutorials/666-advanced-boot-options.html
• Repair Your Computer
• http://www.sevenforums.com/tutorials/668-system-recovery-options.html
• OPTION TWO of http://www.sevenforums.com/tutorials/700-system-restore.html

 

[DJJay]

I'm confused here. Who is answering who. I am not Fari. I was being helped by zigzag and then a random post from Fari showed up on this thread.

I can boot my system and work all day without any problems. The crashes are happening at night.
Seems like another thread was started in my thread and I'm not sure where the responses are directed.

 

[writhziden]

Sorry, did not notice it was someone else. I am a bit overworked today... Fari, this is why we ask that people start their own threads.

Fari: Please start your own thread and follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

DJJay: I apologize for the confusion. We are a bit shorthanded at this time in crashes and debugging and I have taken over many of zigzag3143's threads (there are a lot of them) for the time being. Analyzing your crashes...


Possible out of date drivers:

ADIHdAud	92055000	920af000	Fri Aug 03 12:28:43 2007 (46b373db)	000582a5		ADIHdAud.sys
purendis	921e3000	921ed000	Fri Jun 05 22:32:39 2009 (4a29f167)	00013375		purendis.sys
pnarp	921d9000	921e3000	Sat Jun 06 00:07:38 2009 (4a2a07aa)	0000ce6e		pnarp.sys

ADIHdAud.sys
purendis.sys
pnarp.sys

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\DJJay\Minidumps\032212-21091-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x82c04000 PsLoadedModuleList = 0x82d4d4d0
Debug session time: Thu Mar 22 05:49:49.242 2012 (UTC - 6:00)
System Uptime: 0 days 0:42:59.897
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0447d50, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 10cad860, current process (virtual address for lock type 3, or PTE)
Arg4: 88faad99, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

GetPointerFromAddress: unable to read from 82d6d830

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  ae708a40 -- (.trap 0xffffffffae708a40)
ErrCode = 00000010
eax=00000000 ebx=853dcdf0 ecx=88ee73c5 edx=85f0c148 esi=853dcd98 edi=860120d8
eip=88faad99 esp=ae708ab4 ebp=ae708b14 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
Ntfs!NtfsAbortTransaction:
88faad99 92              xchg    eax,edx
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82ca7e18 to 82ce2f04

STACK_TEXT:  
ae7088d4 82ca7e18 0000007a c0447d50 c000000e nt!KeBugCheckEx+0x1e
ae708944 82cab6f9 ae708968 82d6e300 ae708988 nt!MiWaitForInPageComplete+0x302
ae7089a4 82c9495b 82d6e300 88faad99 8581d008 nt!MiIssueHardFault+0x3b3
ae708a28 82c45478 00000008 88faad99 00000000 nt!MmAccessFault+0x2656
ae708a28 88faad99 00000008 88faad99 00000000 nt!KiTrap0E+0xdc
ae708ab0 88ee6100 853dcd98 860120d8 00000000 Ntfs!NtfsAbortTransaction
ae708b14 88f623da 853dcd98 85923298 c000000e Ntfs!NtfsProcessException+0x278
ae708b88 82c3b5be 86012020 85923298 85923298 Ntfs!NtfsFsdFileSystemControl+0x196
ae708ba0 892cd20c 85e71020 85923298 00000000 nt!IofCallDriver+0x63
ae708bc4 892e0ce8 ae708be4 85e71020 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
ae708bfc 82c3b5be 85e71020 85923298 85923298 fltmgr!FltpFsControl+0xe8
ae708c14 82e2eac9 851d66a8 85923298 8592344c nt!IofCallDriver+0x63
ae708c34 82e31c9b 85e71020 851d66a8 00000001 nt!IopSynchronousServiceTail+0x1f8
ae708cd0 82e5a89a 85e71020 85923298 00000000 nt!IopXxxControlFile+0x6aa
ae708d04 82c4228a 00000164 00000000 00000000 nt!NtFsControlFile+0x2a
ae708d04 77b07094 00000164 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00e4f3a4 00000000 00000000 00000000 00000000 0x77b07094


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    88faa000-88faa066  103 bytes - Ntfs!DoAction+104b
	[ 08 74 0f 0f b7 51 08 03:50 8b 00 00 1c 00 ff ff ]
    88faa068-88faa072  11 bytes - Ntfs!DoAction+10b3 (+0x68)
	[ 15 5c e6 ef 88 89 1e 68:a0 07 00 00 1e 00 ff ff ]
    88faa074-88faa076  3 bytes - Ntfs!DoAction+10bf (+0x0c)
	[ e9 a2 ef:1f 00 ff ]
    88faa078-88faa0bd  70 bytes - Ntfs!DoAction+10c3 (+0x04)
	[ ff 8b 55 24 3b d3 74 25:40 04 00 00 1e 00 ff ff ]
    88faa0bf-88faa0cd  15 bytes - Ntfs!DoAction+110a (+0x47)
	[ 15 5c e6 ef 88 89 1e 68:ff a0 bb 03 00 1c 00 ff ]
    88faa0d0-88faa10c  61 bytes - Ntfs!DoAction+111b (+0x11)
	[ 8b 4d 2c 0f b7 51 14 8d:80 bb 03 00 1c 00 ff ff ]
    88faa10e-88faa164  87 bytes - Ntfs!DoAction+1159 (+0x3e)
	[ 00 75 6a 03 c1 0f b7 48:ff ff 60 92 0b 00 1c 00 ]
    88faa166-88faa179  20 bytes - Ntfs!DoAction+11b1 (+0x58)
	[ e9 b0 ee ff ff ff 75 18:ff ff 20 25 00 00 1c 00 ]
    88faa17b-88faa19f  37 bytes - Ntfs!DoAction+11c6 (+0x15)
	[ 8b 06 3b c3 74 09 50 ff:00 1d 00 ff ff e0 92 0b ]
    88faa1a1-88faa1cc  44 bytes - Ntfs!DoAction+11ec (+0x26)
	[ 57 ff 75 0c ff 75 08 e8:93 0b 00 1c 00 ff ff 20 ]
    88faa1ce-88faa1fd  48 bytes - Ntfs!DoAction+1219 (+0x2d)
	[ e9 48 ee ff ff 8b 55 24:ff ff 50 93 0b 00 1c 00 ]
    88faa1ff-88faa209  11 bytes - Ntfs!DoAction+124a (+0x31)
	[ 8b 45 28 3b c3 74 05 0f:ff 20 42 00 00 1d 00 ff ]
    88faa20b-88faa211  7 bytes - Ntfs!DoAction+1256 (+0x0c)
	[ 33 d2 81 fa 03 07 00:00 1c 00 ff ff b0 41 ]
    88faa213-88faa224  18 bytes - Ntfs!DoAction+125e (+0x08)
	[ 74 13 3b c3 74 05 0f b7:00 1d 00 ff ff f0 91 0b ]
    88faa226-88faa22d  8 bytes - Ntfs!DoAction+1271 (+0x13)
	[ 75 0b 51 50 e8 75 07 fd:ff ff d0 91 0b 00 1c 00 ]
    88faa22f - Ntfs!DoAction+127a (+0x09)
	[ 84:ff ]
    88faa231-88faa296  102 bytes - Ntfs!DoAction+127c (+0x02)
	[ 75 19 8b 06 3b c3 74 09:91 0b 00 1c 00 ff ff 80 ]
    88faa298-88faa2a2  11 bytes - Ntfs!DoAction+12e3 (+0x67)
	[ 15 5c e6 ef 88 89 1e 68:20 07 00 00 1d 00 ff ff ]
    88faa2a4-88faa2a6  3 bytes - Ntfs!DoAction+12ef (+0x0c)
	[ e9 72 ed:1c 00 ff ]
    88faa2a8-88faa2b6  15 bytes - Ntfs!DoAction+12f3 (+0x04)
	[ ff 8d 41 08 8b 55 30 89:50 0d 00 00 1d 00 ff ff ]
    88faa2b8-88faa2ee  55 bytes - Ntfs!DoAction+1303 (+0x10)
	[ 30 8b 45 10 0f b7 40 12:40 33 0b 00 1c 00 ff ff ]
    88faa2f0-88faa2fa  11 bytes - Ntfs!DoAction+133b (+0x38)
	[ 15 5c e6 ef 88 89 1e 68:40 32 0b 00 1c 00 ff ff ]
    88faa2fc-88faa2fe  3 bytes - Ntfs!DoAction+1347 (+0x0c)
	[ e9 1a ed:1c 00 ff ]
    88faa300-88faa345  70 bytes - Ntfs!DoAction+134b (+0x04)
	[ ff 8b 55 24 3b d3 74 25:30 02 00 00 1c 00 ff ff ]
    88faa347-88faa355  15 bytes - Ntfs!DoAction+1392 (+0x47)
	[ 15 5c e6 ef 88 89 1e 68:ff 50 41 0b 00 1c 00 ff ]
    88faa358-88faa454  253 bytes - Ntfs!DoAction+13a3 (+0x11)
	[ 8b 5d 2c 0f b7 4b 14 8d:10 4f 0b 00 1c 00 ff ff ]
    88faa456-88faa485  48 bytes - Ntfs!DoAction+14a1 (+0xfe)
	[ e9 c0 eb ff ff 8b 55 24:ff ff e0 6e 0b 00 1c 00 ]
    88faa487-88faa4ac  38 bytes - Ntfs!DoAction+14d2 (+0x31)
	[ 8b 45 28 3b c3 74 05 0f:ff 20 1f 0b 00 1c 00 ff ]
    88faa4ae-88faa4b5  8 bytes - Ntfs!DoAction+14f9 (+0x27)
	[ 75 0b 51 50 e8 ed 04 fd:ff ff c0 23 0b 00 1c 00 ]
    88faa4b7-88faa4ec  54 bytes - Ntfs!DoAction+1502 (+0x09)
	[ 84 c0 75 19 8b 06 3b c3:ff 50 06 00 00 1d 00 ff ]
    88faa4ee-88faa535  72 bytes - Ntfs!DoAction+1539 (+0x37)
	[ 74 15 0f b7 7a 08 03 df:ff ff 50 8e 02 00 1c 00 ]
    88faa537-88faa547  17 bytes - Ntfs!DoAction+1582 (+0x49)
	[ 3b c7 74 09 50 ff 15 5c:ff f0 49 0b 00 1c 00 ff ]
    88faa549-88faa575  45 bytes - Ntfs!DoAction+1594 (+0x12)
	[ e9 67 f0 ff ff 8b 55 14:26 0b 00 1c 00 ff ff 30 ]
    88faa577-88faa5a9  51 bytes - Ntfs!DoAction+15c2 (+0x2e)
	[ 75 10 8b 5d 0c 53 ff 75:ff 60 22 0b 00 1c 00 ff ]
    88faa5ac-88faa5f5  74 bytes - Ntfs!DoAction+15f7 (+0x35)
	[ d3 e0 8b 0f 8b 57 04 8d:1d 00 ff ff a0 22 0b 00 ]
    88faa5f7-88faa606  16 bytes - Ntfs!DoAction+1642 (+0x4b)
	[ 77 04 ff 37 8d 45 cc 50:ff e0 06 00 00 1d 00 ff ]
    88faa608-88faa612  11 bytes - Ntfs!DoAction+1653 (+0x11)
	[ 8b 46 24 f6 40 04 10 0f:10 07 00 00 1d 00 ff ff ]
    88faa614-88faa624  17 bytes - Ntfs!DoAction+165f (+0x0c)
	[ 00 8b 45 28 3b 43 24 0f:1c 00 ff ff 40 23 0b 00 ]
    88faa626-88faa63a  21 bytes - Ntfs!DoAction+1671 (+0x12)
	[ 00 8b 4f 04 29 08 83 58:ff ff 50 23 0b 00 1c 00 ]
    88faa63c-88faa662  39 bytes - Ntfs!DoAction+1687 (+0x16)
	[ d3 e2 0f b7 40 14 c1 e0:1c 00 ff ff 30 07 00 00 ]
    88faa664-88faa686  35 bytes - Ntfs!DoAction+16af (+0x28)
	[ 0f 84 ed 06 00 00 8b b3:1c 00 ff ff d0 03 00 00 ]
    88faa688-88faa6a2  27 bytes - Ntfs!DoAction+16d3 (+0x24)
	[ 15 9c e5 ef 88 84 c0 74:40 c7 01 00 1c 00 ff ff ]
    88faa6a4-88faa6aa  7 bytes - Ntfs!DoAction+16ef (+0x1c)
	[ 3b f0 0f 84 ab 06 00:1c 00 ff ff f0 41 0b ]
    88faa6ac-88faa6b5  10 bytes - Ntfs!DoAction+16f7 (+0x08)
	[ eb c2 6a 00 ff 77 04 ff:1c 00 ff ff c0 c3 03 00 ]
    88faa6b7 - Ntfs!DoAction+1701 (+0x0b)
	[ 75:ff ]
    88faa6b9-88faa6da  34 bytes - Ntfs!DoAction+1703 (+0x02)
	[ 8d 46 08 50 ff 15 0c e0:b8 00 00 1c 00 ff ff 10 ]
    88faa6dc-88faa6ff  36 bytes - Ntfs!DoAction+1726 (+0x23)
	[ e9 76 06 00 00 83 e8 16:1c 00 ff ff a0 c3 03 00 ]
    88faa701-88faa71d  29 bytes - Ntfs!DoAction+174b (+0x25)
	[ 48 0f 85 4f 06 00 00 8d:55 0b 00 1c 00 ff ff 30 ]
    88faa720-88faa756  55 bytes - Ntfs!DoAction+176a (+0x1f)
	[ 8b 4d 14 8b 01 3b 05 68:a0 55 0b 00 1c 00 ff ff ]
    88faa758-88faa765  14 bytes - Ntfs!DoAction+17a2 (+0x38)
	[ ff 8b 42 04 3b 41 0c 7f:f0 55 0b 00 1c 00 ff ff ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3972 errors : !Ntfs (88faa000-88faafff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

This seems like a hard disk controller problem or hard disk problem. Can you upload the full reports through the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html? I notice that zigzag3143 had you rename some driver files. I want to make sure there are not any problem devices that might be interfering with your system running properly.


In the meantime, run a http://www.sevenforums.com/tutorials/433-disk-check.html with both boxes checked at your earliest convenience. It will take some time depending on the size of the disk. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.

 

[DJJay]

Thanks writhziden. I appreciate the help.
I am posting the report you rquested and I will run a chkdsk later.

 

[writhziden]

Are you aware of this Problem device:

TSSTcorp DVD+-RW TS-H653F ATA Device	IDE\CDROMTSSTCORP_DVD+-RW_TS-H653F_______________DW10____\5&22F68978&0&1.0.0	39

???

 

[DJJay]

I was going to ask about it this morning. I noticed it was a problem after I uninstalled all the Roxio and Sonic programs and renamed the drivers as per instructions.

I kinda need my DVD drive.....any suggestions?

Can I fix this crash problem wiithout a full reinstall?

 

[DJJay]

I renamed the drivers back to .sys and my DVD drive is back. The computer crashed after the file renames and as I said, it only crashes when the computer is sitting overnight and not in use. Could it be a screensaver or hibernation issue?

 

[writhziden]

The crash you are getting is not indicative of a driver power state failure, so I do not think that is the cause. Can you upload the latest crash reports?

 

[DJJay]

The dump files are all gone. I shut down the computer last night so there were no new dumps since I last posted.

Is there any other crash report I can get for you?

 

[writhziden]

Yes. Please provide us with your Event Viewer administrative logs by following these steps:

1. Click Start Menu
2. Type eventvwr into Search programs and files (do not hit enter)
3. Right click eventvwr.exe and click Run as administrator
4. Expand Custom Views
5. Click Administrative Events
6. Right click Administrative Events
7. Save all Events in Custom View As...
8. Save them in a folder where you will remember which folder and save as Errors.evtx
9. When asked, save the display information in English.
10. Go to where you saved Errors.evtx
11. Create a new folder by right clicking in a blank area within the folder Errors.evtx is saved in. You could also click New Folder at the top of the directory under the directory path box.
12. Name the new folder Errors.
13. Place Errors.evtx and the LocaleMetaData folder into the new Errors folder.
14. Right click the Errors folder -> send to -> compressed (zipped) folder
15. Upload the .zip file here.

There might be some logs pertaining to the crashes.

 

[DJJay]

As per your request I have uloaded the folder. I will be gone for the weekend starting at 5:00 PM Eastern Time. If I don't hear from you before then ... have a great weekend.
I will be shutting down the computer over the weekend as well. So no new error reports til Tuesday unless, of course, we resolve the problem before then.

 

[writhziden]

Log Name:      System
Source:        sptd
Date:          3/23/2012 2:22:28 PM
Event ID:      4
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Jay-PC
Description:
Driver detected an internal error in its data structures for .

Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

Log Name:      Application
Source:        Microsoft-Windows-WMI
Date:          3/23/2012 12:56:35 AM
Event ID:      10
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Jay-PC
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2

 

[DJJay]

Did as requested and actually found a new Soundmax driver today.

Only 1 crash last night. I am posting the minidump.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\DJJay\032612-32775-01\032612-32775-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x82a01000 PsLoadedModuleList = 0x82b4a4d0
Debug session time: Mon Mar 26 14:26:24.066 2012 (UTC - 6:00)
System Uptime: 0 days 0:47:32.861
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0458898, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 02fc7be0, current process (virtual address for lock type 3, or PTE)
Arg4: 8b113000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SYSTEM

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82aa4e18 to 82adff04

STACK_TEXT:  
8b14fafc 82aa4e18 0000007a c0458898 c000000e nt!KeBugCheckEx+0x1e
8b14fb6c 82aa86f9 8b14fbc0 82b6b300 8b14fbe0 nt!MiWaitForInPageComplete+0x302
8b14fbfc 82a9195b 82b6b300 8b113000 8618d1a8 nt!MiIssueHardFault+0x3b3
8b14fc80 82ab2b00 00000001 8b113000 00000000 nt!MmAccessFault+0x2656
8b14fd10 82ac62be 84caf020 8b14fd30 00000000 nt!MiInPageSingleKernelStack+0x1cf
8b14fd44 82a8a884 84caf094 8b14fd90 82c0a022 nt!KiInSwapKernelStacks+0x41
8b14fd50 82c0a022 00000000 ae5ab346 00000000 nt!KeSwapProcessOrStack+0x78
8b14fd90 82ab2219 82a8a80c 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiWaitForInPageComplete+302
82aa4e18 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiWaitForInPageComplete+302

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79850

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x7a_c000000e_nt!MiWaitForInPageComplete+302

BUCKET_ID:  0x7a_c000000e_nt!MiWaitForInPageComplete+302

Followup: MachineOwner
---------

Definitely starting to look like you have bad RAM even though you passed Memtest86+. Sometimes Memtest86+ does not catch errors on the first run.

• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[DJJay]

Again.... only 1 crash last night. Dump attached again. I will run memetest this evening if I can, otherwise it will be tomorrow.

Thanks for the info. Maybe you can actually solve this, cause I am completely lost at this point.

 

[DJJay]

The computer went down when I was away from it for approx. 25 minutes. This is the first time that it has happened while I was here at work.
I have attached the most recent dump.