the slot power u saying is it the dram voltage?

memtest no errors, now what?

i dont know what kind of bios u are using, please find memory voltage, normally either the value is 'auto' or standard value is 1.5volt.
try to up 0.1 point at a time.
if u lucky some bios gave explanation on the right.

yeah, well i think it's the dram voltage, inside memory voltage setting and the only thing that spells volt

My laptop had this crash dump on the blue screen. What's wrong with it? I've had my OS fully restored, but problem still persists. Please help.


This post has been edited by JJTam: Apr 10 2012, 04:20 PM

post your minidump here,
My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

it seems like to comlicated to troubleshoot this problem...take my advice...just change the motherboard...

http://blogsyarih.com/non-system-disk-or-d...-your-computer/

Hi, sorry there's no Minidump folder. I have just changed the Write Debugging Information header to Small memory dump (256 kB) in the dropdown box and
it shows that the Small Dump Directory is listed as %systemroot%\Minidump. Waiting for it to crash again. Is there any other ways to get the minidump files?

This post has been edited by JJTam: Apr 11 2012, 11:29 AM

i help u google that error code

---

Added on April 11, 2012, 11:34 amchecked might be a malware infection, u night need to repair windows, or scan for malware

This post has been edited by noobandroid: Apr 11 2012, 11:34 AM

I use Malwarebytes anti malware and did a quick scan, turns out to be no malware.


This post has been edited by JJTam: Apr 13 2012, 02:55 PM

Hi, this is the minidump file. It crashed again after a full factory restore.


Attached File(s)
 041312_25381_01.zip ( 20.66k ) Number of downloads: 6

I have BSOD appeared display error disk.sys.

have this problem when:

1. when finish loading at the taskbar (icons)
2. when using utilities software advance system care to clean registry etc
3. i have to restart then back to normal

heres my minidump:

please help thanks....

This post has been edited by yanouchi: Apr 16 2012, 11:54 AM


Attached File(s)
 Minidump.zip ( 37.32k ) Number of downloads: 6

Chances are you will need to purchase new memory. For more information on faulty memory and memory diagnostics, see PCstats Guide to diagnosing bad memory

This post has been edited by Genevieve84: Apr 16 2012, 03:29 PM

Hmm guys... had multiple BSOD seems to be related to Bad pool header.. did some reading still can't figure it out...


Attached File(s)
 042912_11341_01.zip ( 40.89k ) Number of downloads: 8

thus xp only have automatic restart?

hi guys im having a little bit trouble with my pc at the moment,

im getting random BSOD's which says "Stop 0x00000101 A clock interrupt was not received on a secondary processor within the allocated time interval."

and i've checked on my event logs under windows, giving me the error of "Microsoft-Windows-Kernel-Power" , "event ID: 41"

the issue occurs after when i replace my motherboard,

story is that my motherboard was faulty, and i got it replaced to the exact same board, only that .. i did not clean installed a new windows 7.

Could that be the reason of the BSOD? before i changed my motherboard the system was stable.

specs are ;

shuttle xpc sh67h3
intel i5 2500
2 x 4gb ddr 1333 team elite
crucial m4 128mb ssd
western digital 160gb hdd
pioneer dvdr-w
nvidia 9600gt

i've tried flashing to the latest BIOS and reset BIOS to default, but problem still occur.

anyway, i can fix this problem without reinstalling windows?

Cheers

Ur BSOD states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.

Use check disk command for any errors on hard disk -

Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.

Use the check disk commands as follows:
1. Click Start.
2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.
4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.

NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.

---

Added on May 2, 2012, 4:22 pmUr error was due to requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). A faulty vga card can also cause such issue.

---

Added on May 2, 2012, 4:52 pmThese crashes were caused by memory corruption probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

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-7 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://memtest.org/#downiso

Driver Verifer
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.

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/Windows 7 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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).

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.
http://msdn.microsoft.com/en-us/library/ff...v=VS.85%29.aspx


This post has been edited by super macgyver: May 2 2012, 04:52 PM

I'll give them a try and revert. Thank you very much for the detailed information!

Hi i recently bought a new pc system bout few weeks actually i used it for few days and kept frequently having bsod with a few types of errors.
NTFS_FILE_SYSTEM
DRIVER_IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
MEMORY_MANAGEMENT
I have reformatted countless times but this still occurs.
I suspected hardware problem and i sent it to the guy i bought it from to diagnose it but he say he diagnose for two weeks d with his busy schedule so far he say no problem.
He says might be due to my power supply from the socket being not stable causing the errors.
I am enquiring if this could be it? Cause i never face this much bsod errors before

I face this problem before with a brand new PC as well... I suffer for about 1 year... keep getting bsod..... finally i change to a brand new hard disk.... perfect!! my machine work flawlessly!! I was wasting so much time before to keep formatting my pc!!!