Humor Random Comments Thread

Mem Dump: Which Win version are you using?
Windows 7.

I'm looking through the advanced system settings, but I can't seem to find any settings relating to blue screens. :shrug:

Edit: I think I found it. System Failure > Automatically restart. I unchecked it, now I'll wait until the next time it crashes.

Edit2: I also have "Write an event to the system log" checked, so where can I find the system log? (Probably a stupid question, I know :P)

Edit3: Nevermind, I've finally got this all figured out. Automatically restart unchecked and Write debugging information set to complete memory dump.

Edit4: I've got this, I've got this by the :censored:
 
Last edited:
Control panel > administrative tools > Event Viewer
the log you want will be under:
Windows Logs > System, will be of level 'Error' and the source will be bugcheck. the log will tell you what the BSoD told you, plus where the Dump was saved.
 
Wow... there's a Wikipedia page for [ame="http://en.wikipedia.org/wiki/Real_life"]real life[/ame] . :lol:
 
Currently listening to Entropy by MC Hawking.
 
Currently listening to:

[ame="http://www.youtube.com/watch?v=GGae-ZYrdx8"]boud boud boud boud[/ame]

:WTF:
 
Last edited:
Okay, I opened the dump file in winDbg and it said that the likely cause is "ntkrnlmp.exe" yet a search in explorer turns up no results. :shrug:
 
FA-18F_vapor_over_wings_1.jpg
 
:jawdrops:
You should have seen one of those doing a .9 Mach pass 30 feet of the wavetops of SF Bay at Fleet Week... Nice shock cloud hanging off the plane. Remarkably quiet for such a fast flight.
 
:jawdrops:
You should have seen one of those doing a .9 Mach pass 30 feet of the wavetops of SF Bay at Fleet Week... Nice shock cloud hanging off the plane. Remarkably quiet for such a fast flight.

If you're amazed at that, wait until you see this -
OqqFV.jpg
 
My Ubuntu installation just failed for the fifth time today. :dry:

Anyway, does anyone have any idea what's causing my blue screens? I definitely don't have the file ntkrnlmp.exe on my computer.

---------- Post added at 06:37 PM ---------- Previous post was at 05:48 PM ----------

Windows finally blue screened again, here's the important stuff.

KERNEL_DATA_INPAGE_ERROR
*** STOP: 0X0000007A  (0XFFFFF6FC0001A498, 0XFFFFFFFFC0000185,0X0000000075E088860,0XFFFFF80003493B80)
 
My Ubuntu installation just failed for the fifth time today. :dry:

Anyway, does anyone have any idea what's causing my blue screens? I definitely don't have the file ntkrnlmp.exe on my computer.

---------- Post added at 06:37 PM ---------- Previous post was at 05:48 PM ----------

Windows finally blue screened again, here's the important stuff.

KERNEL_DATA_INPAGE_ERROR
*** STOP: 0X0000007A (0XFFFFF6FC0001A498, 0XFFFFFFFFC0000185,0X0000000075E088860,0XFFFFF80003493B80)

Wait... Ubuntu and windows are both crashing on you? The you have a serious hardware problem somewhere, I'd guess.
 
Wait... Ubuntu and windows are both crashing on you? The you have a serious hardware problem somewhere, I'd guess.
No, Ubuntu is fine I just got an error at the end of the installation, it still works as I found out later. :P

On another note.
:blink: That post I made a while back in the "World Ending October 21st?" thread, this was the kind of person I meant by that post.
 
Well, that's just :censored: great, it bluescreened before Ubuntu finished installing. :@

If it's bluescreening while Ubuntu's installing, that would mean you're using Wubi (Windows UBuntu Installer). This installs Windows on a file on your existing Windows partition, which is nice for trying Ubuntu out without committing to repartitioning your hard drive.

The problem with it (especially in your situation) is that because of the "installed in a file" thing, it's extra susceptible to data loss from hard reboots.

Is there any way to make it so the bluescreen shows for more than 2 seconds? I'd like to be able to copy down any information that could help find the problem.

Edit: Even with the AC and my fan at 100% (Or not, Speedfan doesn't seem to actually change the speed :dry:) all my thermometres are reading 30-40C.

30-40 C shouldn't be any problem at all. For a desktop, I'd say it's likely to be a fairly typical idling temperature. My laptop is currently running a bit above idle at 50 C.

If you want to make sure it's not a heating issue, shut down and boot from your Ubuntu CD directly (instead of through your Wubi install, as you don't want to mess that up if the following stress test does cause the machine to crash). Then open up a terminal window for each CPU core you have, plus one more. For each CPU core, type "top -d0" into one of your terminal windows and hit enter (top is a process monitoring program, but we're using it here because the -d0 option makes it update its display as fast as it possibly can, making it take up as much CPU time as it can get ahold of. It's only single threaded, though, so each instance will only max out one core). In the remaining terminal window, type "sensors" and hit enter. This will give you a temperature reading (and should also give you the critical temperature for the components your sensors are monitoring).

The output of "sensors" should look something like this:

Code:
acpitz-virtual-0
Adapter: Virtual device
temp1:       +52.8°C  (crit = +95.0°C)

Every 10 seconds or so, type "sensors" again (or hit the up arrow key, then enter). If after 10 minutes the machine hasn't exceeded any of the critical temperatures listed (my machine only displays output for one sensor, but I believe "sensors" can display output for more than one, depending on the machine), it is almost certainly not a heating issue (though it might be if it's getting close (within 5 degrees or so) to some of the critical temperatures).
 
If it's bluescreening while Ubuntu's installing, that would mean you're using Wubi (Windows UBuntu Installer). This installs Windows on a file on your existing Windows partition, which is nice for trying Ubuntu out without committing to repartitioning your hard drive.

The problem with it (especially in your situation) is that because of the "installed in a file" thing, it's extra susceptible to data loss from hard reboots.



30-40 C shouldn't be any problem at all. For a desktop, I'd say it's likely to be a fairly typical idling temperature. My laptop is currently running a bit above idle at 50 C.

If you want to make sure it's not a heating issue, shut down and boot from your Ubuntu CD directly (instead of through your Wubi install, as you don't want to mess that up if the following stress test does cause the machine to crash). Then open up a terminal window for each CPU core you have, plus one more. For each CPU core, type "top -d0" into one of your terminal windows and hit enter (top is a process monitoring program, but we're using it here because the -d0 option makes it update its display as fast as it possibly can, making it take up as much CPU time as it can get ahold of. It's only single threaded, though, so each instance will only max out one core). In the remaining terminal window, type "sensors" and hit enter. This will give you a temperature reading (and should also give you the critical temperature for the components your sensors are monitoring).

The output of "sensors" should look something like this:

Code:
acpitz-virtual-0
Adapter: Virtual device
temp1:       +52.8°C  (crit = +95.0°C)
Every 10 seconds or so, type "sensors" again (or hit the up arrow key, then enter). If after 10 minutes the machine hasn't exceeded any of the critical temperatures listed (my machine only displays output for one sensor, but I believe "sensors" can display output for more than one, depending on the machine), it is almost certainly not a heating issue (though it might be if it's getting close (within 5 degrees or so) to some of the critical temperatures).
I got Ubuntu installed so that doesn't matter any more. I don't have a CD I've always used Wubi to install Ubuntu.

I'm now starting to again think that it isn't a heating issue as Ubuntu runs fine seemingly indefinitely. Is the info I posted earlier of any use?
 
you'd better have ntkrnlmp.exe on your system, its a part of the window Kernel, if you don't have it, your in deep, deep trouble!
Excuse me while I go google that stop error code you got...

---------- Post added at 12:05 PM ---------- Previous post was at 12:01 PM ----------

Right:
STOP error 0x7A means that the requested page of kernel data from the paging file could not be read into memory
There's the problem, what caused it I can't say. :shrug:
 
Back
Top