Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after seconds or few minutes of operation

08 Mar 2010   #1

Windows 7 Ultimate x64 / XP Professional x32
 
 
BSOD after seconds or few minutes of operation

Hi everyone. While searching the internet to find out why I get so many BSOD I found this thread and I'm in need of your help.
My operating system is Windows 7 Ultimate x64 (but I also have Win XP Pro in another hard drive). Right after a boot I get a BSOD or sometimes it may happen in the first few minutes of operation (it always happens after loading the desktop, not before). But this doesn't happen always. After a few reboots, the OS can start-up and operate without any BSOD even for days. So I have to tolerate a few BSOD each time I turn on my computer (and select Win 7 to start-up).
I attach the files from the folder Minidump as I read in the instructions and I hope you can give me a clue for what is responsible for the BSOD as I have no clue how to use those files myself to find the cause of the problem.
Thanks in advance

P.S. I forgot to mention that lately the OS reboots so quickly that the blue screen doesn't show up, just a screen filled with a mixture of random pixels.


My System SpecsSystem Spec
.

11 Mar 2010   #2
Microsoft MVP

 
 

25 memory dumps - from 17 Jan to 8 Mar 2010
All are STOP 0xA (more info on this error here: BSOD Index )
And all blame core Windows files (which is unlikely).

please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
Quote:
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 manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
Code:
jraid.sys    Thu Apr 03 02:25:47 2008 - JMicron RAID Driver - http://www.carrona.org/dvrref.html#jraid.sys
RTKVHD64.sys Fri Jun 13 05:08:53 2008 - Realtek High Definition Audio Function Driver - http://www.carrona.org/dvrref.html#RTKVHD64.sys
WmBEnum.sys  Thu Jan 24 18:01:30 2008 - Logitech WingMan Virtual Bus Enumerator Driver - http://www.carrona.org/dvrref.html#WmBEnum.sys
WmFilter.sys Thu Jan 24 18:01:27 2008 - Logitech WingMan Hid Filter Driver - http://www.carrona.org/dvrref.html#WmFilter.sys                                                              
WmXlCore.sys Thu Jan 24 18:01:22 2008 - Logitech WingMan Translation Driver - http://www.carrona.org/dvrref.html#WmXlCore.sys
If that doesn't fix things, please run Driver Verifier according to these directions:
Quote:
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/Windows 7 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 "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 (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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Summary of the BSOD's:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 16 20:47:07.665 2010 (GMT-5)
System Uptime: 0 days 0:04:18.102
BugCheck A, {40000000000, 2, 1, fffff80002b19c22}
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 11 16:50:29.821 2010 (GMT-5)
System Uptime: 0 days 0:02:58.243
BugCheck A, {40000000000, 2, 1, fffff80002b0dc22}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 11 12:58:47.390 2010 (GMT-5)
System Uptime: 0 days 0:00:14.828
BugCheck A, {40000000000, 2, 1, fffff80002ac5c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 08:21:48.660 2010 (GMT-5)
System Uptime: 0 days 0:02:13.097
BugCheck A, {40000000000, 2, 1, fffff80002ac5c22}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+3e3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  FXExSS.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 01:28:23.384 2010 (GMT-5)
System Uptime: 0 days 0:01:25.822
BugCheck A, {40000000000, 2, 1, fffff80002abcc22}
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  FXExSS.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 04:37:46.944 2010 (GMT-5)
System Uptime: 0 days 0:01:10.397
BugCheck A, {40000000000, 2, 1, fffff80002ad1c22}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 01:26:26.365 2010 (GMT-5)
System Uptime: 0 days 0:02:17.818
BugCheck A, {40000000000, 2, 1, fffff80002ab4c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 04:40:20.257 2010 (GMT-5)
System Uptime: 0 days 0:00:15.679
BugCheck A, {40000000000, 2, 1, fffff80002ac5c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ATICustomerCar
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 04:38:41.779 2010 (GMT-5)
System Uptime: 0 days 0:00:19.216
BugCheck A, {40000000000, 2, 1, fffff80002abfc22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 04:42:44.974 2010 (GMT-5)
System Uptime: 0 days 0:01:23.412
BugCheck A, {40000000000, 2, 1, fffff80002afdc22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 04:39:33.202 2010 (GMT-5)
System Uptime: 0 days 0:00:15.655
BugCheck A, {40000000000, 2, 1, fffff80002b11c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MOM.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb 16 01:23:30.680 2010 (GMT-5)
System Uptime: 0 days 0:00:27.118
BugCheck A, {40000000000, 2, 1, fffff80002b19c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  sidebar.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 18 04:20:14.252 2010 (GMT-5)
System Uptime: 0 days 0:00:27.674
BugCheck A, {40000000000, 2, 1, fffff80002abac22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ekrn.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 18 04:23:00.259 2010 (GMT-5)
System Uptime: 0 days 0:00:52.697
BugCheck A, {40000000000, 2, 1, fffff80002b05c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ekrn.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Feb 18 04:21:32.484 2010 (GMT-5)
System Uptime: 0 days 0:00:09.937
BugCheck A, {40000000000, 2, 1, fffff80002b16c22}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Rotate+2d0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Feb 24 04:02:52.522 2010 (GMT-5)
System Uptime: 0 days 0:02:20.959
BugCheck A, {40000000000, 2, 1, fffff80002ac7c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 15:02:13.888 2010 (GMT-5)
System Uptime: 0 days 0:00:26.310
BugCheck A, {40000000000, 2, 1, fffff80002d0dc22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 15:01:31.612 2010 (GMT-5)
System Uptime: 0 days 0:00:16.034
BugCheck A, {40000000000, 2, 1, fffff80002d15c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 15:05:45.328 2010 (GMT-5)
System Uptime: 0 days 0:01:59.843
BugCheck A, {40000000000, 2, 1, fffff80001efcc22}
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Mar  2 15:03:22.450 2010 (GMT-5)
System Uptime: 0 days 0:00:50.872
BugCheck A, {40000000000, 2, 1, fffff80002d05c22}
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar  7 09:28:21.234 2010 (GMT-5)
System Uptime: 0 days 0:01:55.750
BugCheck A, {40000000000, 2, 1, fffff80001ec5c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar  7 09:24:10.446 2010 (GMT-5)
System Uptime: 0 days 0:00:26.868
BugCheck A, {40000000000, 2, 1, fffff80002ccbc22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ekrn.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Mar  7 09:25:36.493 2010 (GMT-5)
System Uptime: 0 days 0:00:52.946
BugCheck A, {40000000000, 2, 1, fffff80002cd1c22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ekrn.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar  8 15:38:25.750 2010 (GMT-5)
System Uptime: 0 days 0:00:37.187
BugCheck A, {40000000000, 2, 1, fffff80002cbdc22}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CCC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Mar  8 15:37:16.131 2010 (GMT-5)
System Uptime: 0 days 0:02:58.569
BugCheck A, {40000000000, 2, 1, fffff80002d0dc22}
Probably caused by : win32k.sys ( win32k!FreeObject+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
My System SpecsSystem Spec
11 Mar 2010   #3

Windows 7 Ultimate x64 / XP Professional x32
 
 

I noticed that the BSOD happen only when I turn on the computer after hours of non-use, and they always happen seconds or a minute or two after the OS boots-up. I have to tolerate a few repeated (2 to 7 until now) BSOD after OS boot till they stop. After that the OS operates just fine.

It is so strange. I can't figure out what is the problem. If someone is willing to help I attached the 8 latest minidump files. For the record, I've run the default tests (# 1-8) of Memtestx86 v4.00* for 10 hours, no errors,, test #9 for 12 hours (4 passes) no errors. I've also run sfc.exe /scannow , chkdsk /r , windows memory diagnostic tool and again, no errors/problems. Win XP Pro SP3 also work just fine.

*I did so because I noticed that it is frequently recommended to other users that are dealing with BSOD.

EDIT: The reply came while I was writing this post.
My System SpecsSystem Spec
.


17 Mar 2010   #4

Windows 7 Ultimate x64 / XP Professional x32
 
 

Usasma thank you very much for your time and your help. Thanks to you and this forum I finally got rid of those annoying blue screens.
It took me long to respond because I wanted to be sure that the problem is fixed, and what was causing it.

For the record: I did everything that you suggested but I still had blue screens. At that point I could be sure that the problem was not bad OS files or drivers or disk related. After some more searching I found this thread and this post and I realized that it was a RAM related problem. I reduced the RAM voltage by one step and after that I had no blue screens till this moment.
My System SpecsSystem Spec
18 Mar 2010   #5
Microsoft MVP

 
 

I'm glad that you were able to fix it! Thanks for letting us know!
My System SpecsSystem Spec
Reply

 BSOD after seconds or few minutes of operation




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:26 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33