Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD on Windows 7


  • Please log in to reply
4 replies to this topic

#1 Darkmemento

Darkmemento

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:22 PM

Posted 12 December 2013 - 04:29 PM

Hi,

 

I have been having intermittent blue screen problems for weeks now. It was usually - irql_not_less_or_equal caused-by-ntoskrnl exe.

 

I have just wiped the computer and done a full windows 7 re-install. In the first half an hour since doing so I've already gotten two blue screens. Slight different errors this time - KMODE_EXCEPTION_NOT_HANDLED caused by ntoskrnl.exe..

 

==================================================
Dump File         : 121213-18922-01.dmp
Crash Time        : 12/12/2013 20:58:40
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 00000000`001904fb
Parameter 2       : fffff880`09b1e338
Parameter 3       : fffff880`09b1db90
Parameter 4       : fffff880`012ad355
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+ad355
File Description  : NT File System Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Crash Address     : ntoskrnl.exe+7fd00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\windows\Minidump\121213-18922-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,880
Dump File Time    : 12/12/2013 20:59:58
==================================================
 
==================================================
Dump File         : 121213-29062-01.dmp
Crash Time        : 12/12/2013 20:53:17
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000096
Parameter 2       : fffff800`02d108bf
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7fd00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
Processor         : x64
Crash Address     : ntoskrnl.exe+7fd00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\windows\Minidump\121213-29062-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,824
Dump File Time    : 12/12/2013 20:54:21
==================================================
 
Thanks for any help

Edited by Darkmemento, 12 December 2013 - 04:30 PM.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,586 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:22 PM

Posted 12 December 2013 - 05:45 PM

If you are getting multiple and varied bsod's it's usually either malware or failure of a hardware component.

 

1) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

2) Look in device manager - any yellow or red symbols?

3) Please run full system scans with BOTH your anti virus app and with MalwareBytes

4) Please check the hd and the ram

 

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

 

Hard Drive Diagnostics:

http://www.tacktech.com/display.cfm?ttid=287 

 

Make sure you select the tool which is appropriate for the brand of your hard drive.

Depending on the program, it'll create bootable floppy, or bootable CD.

If downloaded file is of .iso type, use ImgBurnhttp://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), to make the CD bootable.

For Toshiba drives, see here: http://sdd.toshiba.com/main.aspx?Path=ServicesSupport/FujitsuDrivesUSandCanada/SoftwareUtilities#diagnostic



#3 Darkmemento

Darkmemento
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:22 PM

Posted 13 December 2013 - 02:14 PM

Thanks for the reply. I forgot to include in the OP that the computer seemed fine when it wasn't moving about. I only seemed to get BSOD errors when I changed the angle of the screen or when moving the laptop about. This gave rise to be believing it must be a hardware problem with a loose connection or something. I ran all the checks you suggested anyway to see if I could resolve the problem. I've no idea how some sort of corruption could be causing this problem but just in case it's of use to others as googling it seems to be something that is common enough but after having to shut the computer off manually it booted into chkdsk which deleted entries and did other stuff after which the problem seems to have disappeared. Seems incredibly strange but I haven't had a single blue screen since the chkdsk this morning. Thanks for your help and reply.



#4 Allan

Allan

  • BC Advisor
  • 8,586 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:22 PM

Posted 13 December 2013 - 03:09 PM

I'd still run a diagnostic on the hd as described above. And if moving the lid/screen continues to cause problems in the future it may will be a problem with the connecting cable.



#5 Darkmemento

Darkmemento
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:06:22 PM

Posted 13 December 2013 - 03:22 PM

I'd still run a diagnostic on the hd as described above. And if moving the lid/screen continues to cause problems in the future it may will be a problem with the connecting cable.

 

Thanks I will do that. It's very weird in that I have actively tried to cause the problem by moving the computer as much as I can today but no sign of the blue screen since the chkdsk. It's very strange to understand why the two could have been interconnected.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users