08-15-2010, 06:42 PM
Pages: 1 2
08-15-2010, 07:22 PM
I didn't see any error code like that.
08-15-2010, 10:12 PM
From whocrashed:
It looks like something damaged windows.
Quote:Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 8/14/2010 1:48:23 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x82E903A8, 0x9A6EBB90, 0x9A6EB770)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\081410-17628-01.dmp
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
It looks like something damaged windows.
08-15-2010, 10:42 PM
After a quick search of ntkrnlpa.exe, I think I discovered that it's the driver for the card reader causing the problem, as I expected. I'll update it and tell you how it goes.
08-15-2010, 11:09 PM
Yeah it hit me that it could also be a driver however that driver might be a windows driver.
08-16-2010, 08:05 PM
So how is your computer?

08-16-2010, 08:27 PM
Perfectly fine, apparently. I'll check the log after I move in. I changed my mind about reinstalling the drivers, because it seems to be doing fine now.
08-16-2010, 11:11 PM
Have you since tried to use the card or have you given up?
08-17-2010, 12:17 AM
It was my sister's card. She was only here for the weekend.
08-17-2010, 11:28 PM
Must have just been a driver if you haven't had anymore instability doing anything else. If your OS was corrupted you would probably have it crashing more.
08-18-2010, 01:04 PM
Yes, that's about what I'm thinking. I used a different SD card (actually a micro SD card in an adaptor) without any problems. I removed it and reinserted it the same way I did when I got the error, and that worked smoothly. I will finally be able to test it tomorrow when I get to VT. Or maybe the next day; I've got a lot to do on move in day!
08-19-2010, 05:38 PM
I ran the analysis and got the same result you did. The problem has not reoccurred, and I plan on reinstalling Windows anyways, so do you guys think there's anything to worry about here?
08-19-2010, 06:28 PM
I don't think so unless you reinstall and it reoccurs.
Pages: 1 2